Skip to main content

Shepherd writeup
draft-ietf-appsawg-rfc5451bis

1. Summary

  The document shepherd is S. Moonesamy.  The Responsible Area Director is
   Barry Leiba.

   draft-ietf-appsawg-rfc5451bis specifies a header field (Authentication-Results)
   for use with electronic mail messages to indicate the results of message
   authentication efforts.  RFC 5451 was published as a Proposed Standard in
   April 2009.  draft-ietf-appsawg-rfc5451bis incorporates RFC 5451 and its
   errata and RFC 6577 (Authentication-Results Registration Update).  The
   intended status is Internet Standard as there are seven implementations
   of the specification and it has gained significant deployment.

   UPDATE (Barry Leiba): Because of the changes being made in the document,
   this will recycle at Proposed Standard now, and be presented for upgrade to
   Internet Standard in six months or so.

2. Review and Consensus

   The document was discussed by five participants within the Applications
   Area Working Group and it has the consensus of the working group.  The
   issues raised during the WGLC were resolved quickly.

3. Intellectual Property

   There isn't any IPR disclosure referencing this document.  The author has
   confirmed that the document is in full conformance with BCP 78 and BCP 79.

4. Other points

   The document obsoletes RFC 5451 and RFC 6577.

   The "CFWS" mentioned in idnits is not a missing reference.  The informational
   reference to RFC 4870 is intentional.

   Although RFC 2045 and RFC 5321 are downward references.  RFC 5322 is already
   listed in the DOWNREF registry.

   The registration procedures for the "Email Authentication Method Name" and
   "Email Authentication Result Name" registries are changed to Expert Review
   (from IETF Review).  This relaxes the registration requirements, but will require
   that the IESG appoint a designated expert for those registries.  The allocation
   procedures and polices are clearly specified in Sections 6.2 and 6.3.
Back