STD Numbers and the IETF Standards Track
draft-klensin-std-numbers-02

Document Type Active Internet-Draft (individual)
Last updated 2018-07-01
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         J. Klensin
Internet-Draft                                              July 1, 2018
Updates: 1311, 2026 (if approved)
Intended status: Best Current Practice
Expires: January 2, 2019

                STD Numbers and the IETF Standards Track
                      draft-klensin-std-numbers-02

Abstract

   STD numbers are assigned to IETF Standards Track specifications in
   order to provide a stable reference even when RFCs are revised and
   the underlying documents change.  However, the numbers are only
   assigned when the specifications reach Full Standard maturity level,
   significantly reducing their utility in the contemporary world in
   which few specifications advance beyond the first standardization
   maturity level.  For that reason, one recent proposal suggested
   eliminating the numbers entirely.  This document argues that stable
   references for Standards Track specifications are actually useful and
   that the solution is not to abolish the numbers but to change the
   point at which they are assigned.

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 January 2, 2019.

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

Klensin                  Expires January 2, 2019                [Page 1]
Internet-Draft                 STD Numbers                     July 2018

   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   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.  Introduction and Rationale  . . . . . . . . . . . . . . . . .   2
   2.  Proposal  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Changes to RFC 2026 . . . . . . . . . . . . . . . . . . .   3
     2.2.  RFC 1311 Changes  . . . . . . . . . . . . . . . . . . . .   4
   3.  Transition  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction and Rationale

   Note in Draft: With the exception of date, file name info, updated
   references, and this paragraph, this version of this I-D is identical
   to the one posted on 14 February 2011.  In particular, to discussion
   of XML2RFC capabilities has not been updated to reflect new XML2RFC
   definitions and tools and terms like "recent" may need to be
   interpreted in the 2011 context.  It is provided for the convenience
   of the "RFCplusplus" BOF at IETF 102 in support of the hypothesis
   that, if a set of new numbering series are a solution to the
   perceived problem, then overlaying those numbers on the archival RFC
   numbers is likely to be a more realistic experiment than the one
   outlined in the bOF proposal.

   STD numbers [1] are assigned to IETF Standards Track specifications
   in order to provide a stable reference even when RFCs are revised and
   the underlying documents change.  However, as specified in BCP 9 [1],
   the numbers are only assigned when the specifications reach Full
   Standard maturity level, significantly reducing their utility in the
   contemporary world in which few specifications advance beyond the
   first ("Proposed") standardization level.  For that reason, an early
   version of one recent proposal suggested eliminating the numbers
Show full document text