Status Change for RFCs 4405, 4406, 4407 to Historic
draft-andersen-historic-4406-etal-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual in art area)
Last updated 2018-03-23
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state AD is watching
Consensus Boilerplate Unknown
Telechat date
Responsible AD Alexey Melnikov
Send notices to (None)
Network Working Group                                        K. Andersen
Internet-Draft                                                  LinkedIn
Updates: 4405, 4406, 4407 (if approved)                   March 22, 2018
Intended status: Informational
Expires: September 23, 2018

          Status Change for RFCs 4405, 4406, 4407 to Historic
                  draft-andersen-historic-4406-etal-00

Abstract

   In 2006, two experiments were started for email authentication:
   Sender Policy Framework (SPF, RFC 4408 [RFC4408]) and Sender ID (RFC
   4406 [RFC4406], supported by RFCs 4405 [RFC4405] and 4407 [RFC4407]).
   After eight years of experimental data (RFC 6686 [RFC6686]), it was
   clear that SPF remained in widespread use while Sender ID did not.
   RFC 7208 [RFC7208] moved SPF from Experimental status to Proposed
   Standard.  This document acknowledges that Sender ID did not pass its
   experiment, and changes the status of RFCs 4405 [RFC4405], 4406
   [RFC4406], and 4407 [RFC4407] to Historic.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 23, 2018.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Andersen               Expires September 23, 2018               [Page 1]
Internet-Draft                                                March 2018

   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Reasoning . . . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Normative References  . . . . . . . . . . . . . . . . . . . .   2
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   3

1.  Reasoning

   In 2006, two experiments were started for email authentication:
   Sender Policy Framework (SPF, RFC 4408 [RFC4408]) and Sender ID (RFC
   4406 [RFC4406], supported by RFCs 4405 [RFC4405] and 4407 [RFC4407]).
   After eight years of experimental data (RFC 6686 [RFC6686]), it was
   clear that SPF remained in widespread use while Sender ID did not.
   RFC 7208 [RFC7208] moved SPF from Experimental status to Proposed
   Standard.  This document acknowledges that Sender ID did not pass its
   experiment, and changes the status of RFCs 4405 [RFC4405], 4406
   [RFC4406], and 4407 [RFC4407] to Historic.

2.  Normative References

   [RFC4405]  Allman, E. and H. Katz, "SMTP Service Extension for
              Indicating the Responsible Submitter of an E-Mail
              Message", RFC 4405, DOI 10.17487/RFC4405, April 2006,
              <https://www.rfc-editor.org/info/rfc4405>.

   [RFC4406]  Lyon, J. and M. Wong, "Sender ID: Authenticating E-Mail",
              RFC 4406, DOI 10.17487/RFC4406, April 2006,
              <https://www.rfc-editor.org/info/rfc4406>.

   [RFC4407]  Lyon, J., "Purported Responsible Address in E-Mail
              Messages", RFC 4407, DOI 10.17487/RFC4407, April 2006,
              <https://www.rfc-editor.org/info/rfc4407>.

   [RFC4408]  Wong, M. and W. Schlitt, "Sender Policy Framework (SPF)
              for Authorizing Use of Domains in E-Mail, Version 1",
              RFC 4408, DOI 10.17487/RFC4408, April 2006,
              <https://www.rfc-editor.org/info/rfc4408>.

   [RFC6686]  Kucherawy, M., "Resolution of the Sender Policy Framework
              (SPF) and Sender ID Experiments", RFC 6686,
              DOI 10.17487/RFC6686, July 2012,
              <https://www.rfc-editor.org/info/rfc6686>.

Andersen               Expires September 23, 2018               [Page 2]
Internet-Draft                                                March 2018

   [RFC7208]  Kitterman, S., "Sender Policy Framework (SPF) for
              Authorizing Use of Domains in Email, Version 1", RFC 7208,
              DOI 10.17487/RFC7208, April 2014,
              <https://www.rfc-editor.org/info/rfc7208>.
Show full document text