Re: [spf-discuss] SPFv2.1: whether, why, and what?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alex van den Bogaerdt wrote:
> Scott Kitterman wrote:
> > But I agree, TYPE99 only for the new version would be the goal.  I'd
> > still allow for dual publication in TYPE99 and TXT because non-BIND
> > resolvers are not all going to support TYPE99 for some time, but I
> > don't think we should require it.
> Allow dual publication again and we have the same s**t as we have now.
> Either allow it and live with it forever, or do not allow it.  You can't
> allow it but aim for the opposite.
> Worst case is to allow but not require dual publication:
>
> a) publishes using TXT records only
> b) publishes using SPF records only
> c) publishes both
>
> A) only looks for TXT records
> B) only looks for SPF records
> C) looks for both types
>
> (A) has such an old, disfunctional, resolver.  (A) cannot look for (b)'s
> records. Thus, (b) cannot exist.  Most people will be (a), not (c). 
> Much software will be of type (C).  Result: lots of wasted resources.
>
> IMO we should make the SPF record type mandatory or we should
> abandon it entirely (both for version>1 of course).
I agree with your analysis, but it perfectly applies only to SPFv1.  The 
difference between v1 and v2.1 in this regard would be that SPF support 
would be mandatory for v2.1, i.e. v2.1 implementations would be _required_ 
to look up SPF records, so (A) would generally not exist (except where 
poor-quality resolver software would fail on the unknown RR type).

But I agree that (C) is undesirable -- still I would not decide just yet 
that the benefits of dual SPF/TXT support are not worth the hassle.  We 
should first wait for the SPFv1 RFC to be published and then contact the 
BIND people and ask them to implement support for the SPF RR type.  Then 
we need to find out what other obstacles to SPF-type-only support can be 
overcome.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFEEsW8wL7PKlBZWjsRAkAGAKDmzB6pBvUPHfIXfFmH9ZNb6DUNtACgvEAG
WEXJL0MbOg9me19df9+XcYg=
=/wlS
-----END PGP SIGNATURE-----

-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your 
subscription, 
please go to 
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com