In
<2A1D4C86842EE14CA9BC80474919782E011133B3(_at_)mou1wnexm02(_dot_)vcorp(_dot_)ad(_dot_)vrsn(_dot_)com>
"Hallam-Baker, Phillip" <pbaker(_at_)verisign(_dot_)com> writes:
The reason for this is that we are likely to define new features for spf at
some time that mean it makes sense to talk about a 2.0 or 3.0 version with a
whole lotta extra features. We want to have the option of doing that without
loosing backwards compatibility.
New features must be understood by new parsers. Old parsers must be
able to understand that they can't parse new records. If new features
are added, the version number *must* change. Domain owners are free
to publish both newer and older versions of SPF records so that both
newer and older parsers can understand them.
-wayne
-------
Sender Permitted From: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
Latest draft at http://spf.pobox.com/draft-mengwong-spf-02.9.4.txt
Wiki:
http://spfwiki.infinitepenguins.net/pmwiki.php/SenderPermittedFrom/HomePage
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname(_at_)©#«Mo\¯HÝÜîU;±¤Ö¤Íµø?¡