Characterization of Proposed Standards
draft-kolkman-proposed-standards-clarified-05
The information below is for an old version of the document | |||
---|---|---|---|
Document | Type | Active Internet-Draft (individual in gen area) | |
Last updated | 2013-10-31 | ||
Stream | IETF | ||
Intended RFC status | Best Current Practice | ||
Formats | pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Jari Arkko | ||
IESG | IESG state | IESG Evaluation::AD Followup | |
Consensus Boilerplate | Unknown | ||
Telechat date |
Needs 9 more YES or NO OBJECTION positions to pass. |
||
Responsible AD | Jari Arkko | ||
Send notices to | olaf@nlnetlabs.nl, sob@harvard.edu, turners@ieca.com, draft-kolkman-proposed-standards-clarified@tools.ietf.org | ||
IANA | IANA review state | IANA OK - No Actions Needed |
Network Working Group O. Kolkman Internet-Draft NLnet Labs Updates: 2026 (if approved) S. Bradner Intended status: Best Current Practice Harvard University Expires: May 02, 2014 S. Turner IECA, Inc. October 31, 2013 Characterization of Proposed Standards draft-kolkman-proposed-standards-clarified-05 Abstract RFC 2026 describes the review performed by the IESG on IETF Proposed Standard RFCs and characterizes the maturity level of those documents. This document updates RFC 2026 by providing a current and more accurate characterization of Proposed Standards. 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 May 02, 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 Kolkman, Bradner & Turner Expires May 02, 2014 [Page 1] Internet-Draft Proposed Standard October 2013 2. IETF Review of Proposed Standards . . . . . . . . . . . . . . 2 3. Characterization of Specifications . . . . . . . . . . . . . . 3 3.1. Characterization of IETF Proposed Standard Specifications 3 3.2. Characteristics of Internet Standards . . . . . . . . . . 3 4. Further Considerations . . . . . . . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . . 4 Appendix B. Internet Draft Notes and RFC Editor Instructions . . . 4 Appendix B.1. Version 00 . . . . . . . . . . . . . . . . . . . 5 Appendix B.2. Version 00->01 . . . . . . . . . . . . . . . . . 6 Appendix B.3. Version 01->02 . . . . . . . . . . . . . . . . . 6 Appendix B.4. Version 02->03 . . . . . . . . . . . . . . . . . 6 Appendix B.5. Version 03->04 . . . . . . . . . . . . . . . . . 6 Appendix B.6. Version 04->05 . . . . . . . . . . . . . . . . . 6 Appendix B.7. Editors versioning info . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 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 IETF 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 only updates the characterization of Proposed Standards from RFC2026 Section 4.1.1 and does not speak to or alter the procedures for the maintenance of Standards Track documents from RFC 2026 and RFC 6410 [RFC6410]. For complete understanding of the requirements for standardization those documents should be read in conjunction with this document. 2. IETF Review 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 intended that most IETF technical specificationsShow full document text