ietf-mxcomp
[Top] [All Lists]

RE: change of version string

2004-08-19 09:32:04

-----Original Message-----
From: owner-ietf-mxcomp(_at_)mail(_dot_)imc(_dot_)org
[mailto:owner-ietf-mxcomp(_at_)mail(_dot_)imc(_dot_)org]On Behalf Of 
william(at)elan.net
Sent: Wednesday, August 11, 2004 5:59 AM
To: IETF MARID WG
Subject: Re: change of version string

Perhaps it would be usefull if we allow one type of SPF record to
reference
(include, refer to) another type of SPF record, this would eliminate
duplication problems in case of long records and avoid issues with large
dns packet (because of multiple large txt records) as well.

Or perhaps we could say that mail receivers MAY use an v=spf1 records if no
SPF2 record is returned.  As I understand it, any query for a TXT record
will return all TXT records for the domain, so if the TXT version of SPF2 is
queried for, the v=spf1 record will be returned if it exists.

I understand that some are concerned with the difference between 2821
mail.from and 2822 PRA.  I've read all the drafts and as nearly as I can
tell, the mechanisms defined in my v=spf1 record will work perfectly well
for Sender-ID.

For those, like me, for whom the records would be the same, allowing for
backward use of the earler SPF records would simplify things considerably.
It would also allow for Sender-ID checks to be usefully evaluated much
sooner since a large body of v=spf1 records is already published.

For those who are concerned about the distinction, but want to use v=spf1,
if they publish an SPF2 record, then they can define that distinction.

The change I am proposing would be to Page 5 of The Sender-ID Record: Format
and Interpretation, draft-ietf-marid-protocol-02.

Change:

   A Sender-ID compliant MTA MUST look up SPF2 RR type, it MAY lookup
   TXT record at the same time, or wait for negative answer.  SPF2 type
   SHOULD be used if available.

To:

   A Sender-ID compliant MTA MUST look up SPF2 RR type, it MAY lookup
   TXT record at the same time, or wait for negative answer.  SPF2 type
   SHOULD be used if available.  If a v=spf1 record is returned from
   the TXT record lookup, it MAY be used if and only if no SPF2 (SPF2
   RR or SPF2 TXT) record is returned.

I believe that would make life simpler for many of us without undue
complication for others.

Scott Kitterman