spf-discuss
[Top] [All Lists]

Re: [spf-discuss] back to Reclassifying Sender ID and SPF as Historic - was: New SPF Council

2009-01-21 07:56:14
WebMaster(_at_)Commerco(_dot_)Net wrote:
At 01:25 PM 1/20/2009, Sandy wrote:
Anyway,  add  in  half  of  the  unclassified  BINDs, plus half of the
totally  unknown  servers,  and  even  at  this surely inflated level,
you're  talking  about  45%  SPF  RR support. That isn't "most all DNS
servers" (whatever that means). It's almost "most".
[...]
I  would  not argue with your wishful thinking, but that's not what we
should deal with here.

I really don't think it a case of wishful thinking to suggest that moving the spec to 99/SPF as the primary request type over TXT. It is the logical path where things will eventually go.

The new spec should move to 99/SPF as the _only_ request type. It may mention compatibility issues with the experimental rfc (to specify limiting dates would really be wishful thinking, though.)

I'm currently using the stock debian bind, without SPF RR support. So what? Switching to the new spec will not happen suddenly, and people will have plenty of time for upgrading. OTOH, to standardize that the same data should be repeated twice in two distinct RRs is grotesque.

DNS queries might also differ in the new spec. It has been noted that hostmasters usually don't define SPF records for each host. Although I agree that better doc/evangelism may help, we should ease SPF adoption rather than making it more complicated than it needs. I wish the new specs provide for one or more of

1) recommend using wildcard DNS records, see rfc4592 (nb: 4592>4408),
2) mandate the "zone cut" algorithm in clients, and
3) set a default _spf.<domain> name, where <domain> is the SOA MNAME of a failed query.


Below, some pointers to interesting old discussions:


26 Apr 2004, Wayne and Meng agree that _not_ having the zone cut algorithm "is very yucky" http://www.listbox.com/member/archive/735/2004/04/search/em9uZSBjdXQ/sort/subj/page/1/entry/0:1/4462669/

21 Jun 2004, "match_subdomains=yes" wording http://www.listbox.com/member/archive/735/2004/06/search/em9uZSBjdXQ/sort/subj/page/1/entry/0:1/5258624/

18 Oct 2004, "zone cut" in the list of requested changes http://www.listbox.com/member/archive/735/2004/10/search/em9uZSBjdXQ/sort/subj/page/1/entry/10:11/7043237/

07 Nov 2004, worries for the wizard not handling the zone cut http://www.listbox.com/member/archive/735/2004/11/search/em9uZSBjdXQ/sort/subj/page/1/entry/6:12/7310336/

26 Dec 2004, delegated SPF as redirect http://www.listbox.com/member/archive/735/2004/12/search/em9uZSBjdXQ/sort/subj/page/1/entry/1:16/7848208/

14 Jan 2005, pros and cons http://www.listbox.com/member/archive/735/2005/01/search/em9uZSBjdXQ/sort/subj/page/1/entry/9:22/8036442/

23 Feb 2005, zone cut default algorithm should not be used by SPFv1 http://www.listbox.com/member/archive/735/2005/02/search/em9uZSBjdXQ/sort/subj/page/1/entry/0:15/8458725/

24 Feb 2005, "left-to-right stuff" http://www.listbox.com/member/archive/735/2005/02/search/em9uZSBjdXQ/sort/subj/page/1/entry/4:15/8462290/



-------------------------------------------
Sender Policy Framework: http://www.openspf.org
Modify Your Subscription: http://www.listbox.com/member/
Archives: https://www.listbox.com/member/archive/735/=now
RSS Feed: https://www.listbox.com/member/archive/rss/735/
Powered by Listbox: http://www.listbox.com

<Prev in Thread] Current Thread [Next in Thread>