DomainKeys Identified Mail (DKIM) Authorized Third-Party Signatures
Draft of message to be sent after approval:
From: The IESG <firstname.lastname@example.org> To: IETF-Announce <email@example.com> Cc: RFC Editor <firstname.lastname@example.org> Subject: Document Action: 'DKIM Authorized Third-Party Signers' to Experimental RFC (draft-kucherawy-dkim-atps-16.txt) The IESG has approved the following document: - 'DKIM Authorized Third-Party Signers' (draft-kucherawy-dkim-atps-16.txt) as an Experimental RFC This document has been reviewed in the IETF but is not the product of an IETF Working Group. The IESG contact person is Sean Turner. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-kucherawy-dkim-atps/
Technical Summary DKIM deliberately makes no binding between the DNS domain of the signer of a message and any other identity found in the message. Despite this, there is an automatic human perception that an author domain signature (one for which the RFC5322.From domain matches the DNS domain of the signer) is more valuable or trustworthy than any other. There is currently no protocol by which an ADMD can announce that DKIM signatures on its mail added by other ADMDs should also be considered trustworthy by verifiers. This presents an experimental mechanism for doing so. Working Group Summary This is an individual submission, but was discussed with the former DKIM participants, on the DKIM mailing list. Note that there is NOT general agreement that this protocol is important, or even useful. There is good consensus that experimentation is needed to determine utility, and this document sets up that experiment by proposing a protocol for it. Document Quality ATPS has been prototyped, in preparation for this experiment, and is available in an open-source implementation. Other implementations are expected as the experiment proceeds. Personnel Barry Leiba is the Document Shepherd. Sean Turner is the responsible Area Director. IANA Note The new registry should be nested under DKIM Parameters.