On Mon, 7 Jun 2004, Michel Py wrote:
This is exactly why I supported the following suggestion that Tim made
some time ago:
Tim Meadowcroft wrote:
v=spf2 xml=http://www.schmerg.com/spf.xml mx -all
This way you get the best of both worlds - let the 'market(s)'
decide how much they want XML...
Your implementation can choose to ignore the xml string, the only extra
code required in the parser would be to understand that it's there and
jump to the old-style syntax.
This makes SPF1 a prerequisite to using SPF2. By sticking with the
current _ep subdomain scheme for SPF2, the layers are more independent.
I do agree, however, that the XML data is too large for DNS and
ought to be fetched via TCP. However, the existing _ep format
can contain the link.
--
Stuart D. Gathman <stuart(_at_)bmsi(_dot_)com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flamis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.