It is hard to overstate the value and consequent inertia of the SPF
records already "in the field". This is not going to change quickly,
and the standard _must_ reinforce, not diminish, the value of the
existing "base of records".
Anything in the standard that seeks to "force" changes in this base
will do damage to SPF adoption.
We have almost zero leverage with the admins and software vendors
that would have to make changes.
I agree with what is below. Get on the standards track. Fix what is
broken. Change only what must be changed - no more. I would go
one step further, and remove things that are controversial or where
utility is not clearly demonstrated. Smaller, simpler standards are
easier to get adopted.
-dgl-
Dropping the previous text to try a different approach ....
To update RFC 4408 we have to do two things:
1. Resolve the conflict with Sender ID. My proposal for this is to say
DKIM already covers the problem SenderID was meant to solve and is
standards track. Make the Sender ID specs historic and declare it dead.
2. Bugfix the current protocol. I think this can be limited to moving
some DNS Rcodes to permerror and adjusting the type SPF/TXT discussion.
Anything else, IMO, is compatible with the installed base and can be done
in a separate draft or breaks the installed based and I'm against it.
For SPF/TXT, how about something like:
SPF records of type TXT will be deprecated in the future. Senders SHOULD
publish records of type SPF. Receivers SHOULD check for type SPF. Use of
type TXT records MAY continue, but will be deprecated and are not
futureproof.
Keep in mind the IETF has a three step process to full standards, so there
are two more shots at this. We put the deprecation warning in now,
deprecate them the next time, and then drop them for full standard.
Scott K
-------------------------------------------
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
-------------------------------------------
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