-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday 13 July 2004 07:26 am, Michel Bouissou wrote:
Does SPF really belong to Microsoft from now on ? Is the implementation
of SPF in software now governed by a MS License ? If yes, I would of
course immediately quit using it.
Or did I completely misunderstand the whole thing ?
Since that announcement, a lot has happened. If you follow the IETF mailing
list, you will get the most accurate information on what is being debated
and what is already decided.
Caller ID and SPF did merge into Sender ID. However, SPF kept going due to
community support, while Caller ID was basically abandoned. You are still
encouraged to publish and check SPF records because SPF is a subset of
Sender ID.
The IETF MARID working group has decided to not adopt XML anywhere in the
standard. They are currently working out the last few details, but what I
see, it looks like SPF will be adopted and published as an IETF standard
virtually unchanged. Therefore, a large chunk of Sender ID has been
abandoned, and Sender ID is virtually no longer relevant. Only SPF and a
few other similar protocols and procedures are being discussed.
Because Microsoft has virtually bound themselves to whatever the IETF
decides, it was SPF that took over Caller ID, not the other way around.
- --
Jonathan M. Gardner
Mass Mail Systems Developer, Amazon.com
jonagard(_at_)amazon(_dot_)com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFA9BYRBFeYcclU5Q0RAmS7AJ0WVoMzC/mI4tB6L+48IMIwSrmMPgCfcJmI
qVtF3WG0wnEy9EHA0qyDMlo=
=JdIH
-----END PGP SIGNATURE-----