Characterization of Proposed Standards
draft-kolkman-proposed-standards-clarified-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual in gen area)
Last updated 2013-09-02 (latest revision 2013-08-01)
Stream IETF
Intended RFC status Best Current Practice
Formats pdf htmlized bibtex
Reviews
Stream WG state (None)
Document shepherd None
IESG IESG state AD is watching
Consensus Boilerplate Unknown
Telechat date
Responsible AD Jari Arkko
Send notices to olaf@nlnetlabs.nl, sob@harvard.edu, turners@ieca.com, draft-kolkman-proposed-standards-clarified@tools.ietf.org
Network Working Group                                         O. Kolkman
Internet-Draft                                                NLnet Labs
Intended status: Informational                                S. Bradner
Expires: February 01, 2014                            Harvard University
                                                                  Turner
                                                              IECA, Inc.
                                                         August 02, 2013

                 Characterization of Proposed Standards
             draft-kolkman-proposed-standards-clarified-00

Abstract

   This document clarifies the description of the review performed on
   and the maturity level of IETF Proposed Standard RFCs.

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 http://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 February 01, 2014.

Copyright Notice

   Copyright (c) 2013 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 (http://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 . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  IESG Reveiew of Proposed Standards . . . . . . . . . . . . . .  2
   3.  Characterization of Specification  . . . . . . . . . . . . . .  2

Kolkman, Bradner & TurnExpires February 01, 2014                [Page 1]
Internet-Draft             Proposed Standard                 August 2013

     3.1.  Characterization of IETF Proposed Standard Specifications   2
     3.2.  Characteristics of Internet Standards  . . . . . . . . . .  3
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . .  3
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  3
   6.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . .  4
   Appendix B. Internet Draft Editing History . . . . . . . . . . . .  4
     Appendix B.1.  Version 00  . . . . . . . . . . . . . . . . . . .  4
     Appendix B.2.  Editors versioning info . . . . . . . . . . . . .  5
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  5

1.  Introduction

   [Editor Note: ietf@ietf.org is the mailing-list for discussing this
   draft.]

   In the two decades after publication of RFC 2026 [RFC2026] the IESG
   has evolved its review processes of Proposed Standard RFCs and thus
   RFC 2026 section 4.1.1 no longer accurately describes IETF Proposed
   Standards.

   This document updates the characterization of Proposed Standards but
   does not speak to or alter the standard maintenance procedures from
   RFC 2026 and RFC 6410 [RFC6410].

2.  IESG Reveiew of Proposed Standards

   The entry-level maturity for the standards track is "Proposed
   Standard".  A specific action by the IESG is required to move a
   specification onto the standards track at the "Proposed Standard"
   level.

   Initially it was assumed that most IETF technical specifications
   would progress through a series of maturity stages starting with
   Proposed Standard, then progressing to Draft Standard then, finally,
   to Internet Standard (see RFC 2026 section 6).  Over time, for a
   number of reasons, this progression became less common.  In response,
   the IESG strengthened its review of Proposed Standards, basically
   operating as if the Proposed Standard was the last chance for the
   IESG to ensure the quality of the technology and the clarity of the
   standards document.  The result was that IETF Proposed Standards
   approved over the last decade or more have had extensive review.
   Because of this change in review assumptions, IETF Proposed Standards
   should be considered to be at least as mature as final standards from
Show full document text