At 12:16 PM 1/24/2009, you wrote:
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.
Agreed. Although anecdotal, I have been using a mixed DKIM and SPF
environment here and in my experience this works just fine.
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
I would modify slightly, "Receivers MUST first check for type SPF and
failing a response Receivers SHOULD then check for type TXT."
I think that this serves to make clear that SPF has not abandoned TXT
records, but that they are a secondary priority for the current
protocol specification. It becomes another flag to demonstrate that
the protocol has matured and is moving forward by considering the TXT
RR as specifically included to account for the earlier days when
99/SPF DNS RRs did not exist.
In doing this, I think the spec underscores an objective to announce
that SPF TXT RR records are subject to becoming fully depreciated
through an organic process. That process being driven by the
adopters who publish SPF entries in their host files, dropping those
records in favor of the native 99/SPF RR, over however much time
required for that happening.
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.
Sender Policy Framework: http://www.openspf.org
Modify Your Subscription: http://www.listbox.com/member/
RSS Feed: https://www.listbox.com/member/archive/rss/735/
Powered by Listbox: http://www.listbox.com