Re: Re: More about the SPF RRTYPE

alan <[email protected]>
Newsgroups gmane.mail.spam.spf.discuss
Message-ID <[email protected]>
At 19:37 18/08/2011  Thursday, Scott Kitterman wrote:
>I'm against any gratuitous incompatibilities.  I'm not aware of any actual 
>problems caused by the current TXT usage in SPF.  The _spf approach would make 
>wild carding impossible (_spf.*.exmple.com), but I'm not sure I really care.  
>Someone may.
>
>I think for 4408bis saying SHOULD NOT Type SPF (99), SHOULD TXT, MAY _spf TXT 
>is reasonable.  Then in the next update Type SPF could be retired and if there 
>is deployment, _spf could be preferred.
>
>Scott K

can i humbly suggest instead of _spf
we suggest to use
_spf1

to leave room for later potentially incompatible
_spf3

thus people querying can be told to MUST look for _spf1.domain.tld/TXT and MAY if nonexistant look for domain.tld/txt

thus implementers can publish

_spf1.domain.tld     IN TXT "v=spf1 whatever -all"
_senderid.domain.tld IN TXT "v=spf1 whatever -all"
domain.tld           IN TXT "v=spf1 redirect:_spf1.domain.tld -all"
domain.tld           IN TXT "spf2.0/mfrom redirect:_senderid.domain.tld ?all"   <any other junk thrown into txt
domain.tld           IN TXT "spf2.0/pra ?all"   <any other junk thrown into txt
(yes i publish sender-id to stop them mis-using my spf as such)

or whatever they want

and have their record work with new libspf(1 lookup) and old libspf(2 lookups) and all those horrid senderid implementors (2 lookups)

when spf3 comes round we just add

_spf3.domain.tld IN TXT "whatever"

and let implementors leave the old spf1 stuff in place for those recievers not doing spf3 yet
but spf3 requesters will only query _spf3
so once adopted by all (ie the libspf is common) then extra crap in the txt for the domain can be weeded



>-------------------------------------------
>Sender Policy Framework: http://www.openspf.org [http://www.openspf.org]
>Modify Your Subscription: http://www.listbox.com/member/ [http://www.listbox.com/member/]
>
>Archives: https://www.listbox.com/member/archive/735/=now
>RSS Feed: https://www.listbox.com/member/archive/rss/735/13124949-0b42f103
>Modify Your Subscription: https://www.listbox.com/member/?&
>Unsubscribe Now: https://www.listbox.com/unsubscribe/?&&post_id=20110818143728:1EEEF82A-C9C9-11E0-906B-FB4D5F1CDC4B
>Powered by Listbox: http://www.listbox.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.