This might be the right thing to do, but it seems like the more appropriate time might be to do this when DMARC becomes standards-track.
I will note that vanilla, uncustomized SpamAssassin does implement ADSP, so there might be more checking of ADSP records than some realize. See, for example: http://wiki.apache.org/spamassassin/Rules/DKIM_ADSP_CUSTOM_MED -Jim P.S. I owe the DMARC folks a review of the DMARC spec, which I have begun and already have quite a few questions. I expect to complete this within a week. On 9/11/13 4:52 PM, Dave Crocker wrote: > Folks, > > Barry has agreed to sponsor the enclosed status change. > > He would like to see discussion formal request. > > (If you've already responded to my /in/formal query earlier today on the > dmarc@ietf list, please now lodge any formal comments you wish to make > on either of the two lists here. > > d/ > > > -------- Original Message -------- > Subject: Request to move RFC 5617 (ADSP) to Historic > Date: Wed, 11 Sep 2013 16:09:14 -0700 > From: Dave Crocker <dcroc...@bbiw.net> > Organization: Brandenburg InternetWorking > To: Barry Leiba <barryle...@computer.org>, Pete Resnick > <resn...@episteme-software.com> > > Folks, > > This is a formal request, to have DomainKeys Identified Mail (DKIM) > Author Domain Signing Practices (ADSP) (RFC 5617) moved to Historic status. > > It has garnered almost no deployment and use, in the 4 years since its > advancement to IETF Proposed Standard. > > In addition, newer work, DMARC, covers the same general email functional > area and already has garnered quite a bit of deployment and use. Hence > it will clarify things for the marketplace to remove standards status > from the apparently-competing, but actually-useless ADSP specification. > > Today I sent a query to the MAAWG Technical committee and the IETF DMARC > mailing lists, to assess support for the status change. Within only a > few hours, I've already seen quite a few +1s, and no -1s. > > Thanks. > > > d/ > _______________________________________________ NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html
