< draft-kolkman-proposed-standards-clarified-00.txt		draft-kolkman-proposed-standards-clarified-01.txt >
	Network Working Group O. Kolkman		Network Working Group O. Kolkman
	Internet-Draft NLnet Labs		Internet-Draft NLnet Labs
	Intended status: Informational S. Bradner		Updates: 2026 (if approved) S. Bradner
	Expires: February 01, 2014 Harvard University		Intended status: Informational Harvard University
	Turner		Expires: March 15, 2014 S. Turner
	IECA, Inc.		IECA, Inc.
	August 02, 2013		September 13, 2013
	Characterization of Proposed Standards		Characterization of Proposed Standards
	draft-kolkman-proposed-standards-clarified-00		draft-kolkman-proposed-standards-clarified-01
	Abstract		Abstract
	This document clarifies the description of the review performed on		This document clarifies the description of the review performed on
	and the maturity level of IETF Proposed Standard RFCs.		and the maturity level of IETF Proposed Standard RFCs and updates RFC
			2026
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on February 01, 2014.		This Internet-Draft will expire on March 15, 2014.
	Copyright Notice		Copyright Notice
	Copyright (c) 2013 IETF Trust and the persons identified as the		Copyright (c) 2013 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents (http://trustee.ietf.org/		Provisions Relating to IETF Documents (http://trustee.ietf.org/
	license-info) in effect on the date of publication of this document.		license-info) in effect on the date of publication of this document.
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	and restrictions with respect to this document. Code Components		and restrictions with respect to this document. Code Components
	extracted from this document must include Simplified BSD License text		extracted from this document must include Simplified BSD License text
	as described in Section 4.e of the Trust Legal Provisions and are		as described in Section 4.e of the Trust Legal Provisions and are
	provided without warranty as described in the Simplified BSD License.		provided without warranty as described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. IESG Reveiew of Proposed Standards . . . . . . . . . . . . . . 2		2. IESG Reveiew of Proposed Standards . . . . . . . . . . . . . . 2
	3. Characterization of Specification . . . . . . . . . . . . . . 2		3. Characterization of Specification . . . . . . . . . . . . . . 2
	3.1. Characterization of IETF Proposed Standard Specifications 2		3.1. Characterization of IETF Proposed Standard Specifications 3
	3.2. Characteristics of Internet Standards . . . . . . . . . . 3		3.2. Characteristics of Internet Standards . . . . . . . . . . 3
	4. Security Considerations . . . . . . . . . . . . . . . . . . . 3		4. Further Considerations . . . . . . . . . . . . . . . . . . . . 3
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3		5. Security Considerations . . . . . . . . . . . . . . . . . . . 4
	6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 3		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
			7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4
	Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . . 4		Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . . 4
	Appendix B. Internet Draft Editing History . . . . . . . . . . . . 4		Appendix B. Internet Draft Editing History . . . . . . . . . . . . 4
	Appendix B.1. Version 00 . . . . . . . . . . . . . . . . . . . 4		Appendix B.1. Version 00 . . . . . . . . . . . . . . . . . . . 4
	Appendix B.2. Editors versioning info . . . . . . . . . . . . . 5		Appendix B.2. Version 00->01 . . . . . . . . . . . . . . . . . 5
			Appendix B.3. Editors versioning info . . . . . . . . . . . . . 5
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5
	1. Introduction		1. Introduction
	[Editor Note: ietf@ietf.org is the mailing-list for discussing this		[Editor Note: ietf@ietf.org is the mailing-list for discussing this
	draft.]		draft.]
	In the two decades after publication of RFC 2026 [RFC2026] the IESG		In the two decades after publication of RFC 2026 [RFC2026] the IESG
	has evolved its review processes of Proposed Standard RFCs and thus		has evolved its review processes of Proposed Standard RFCs and thus
	RFC 2026 section 4.1.1 no longer accurately describes IETF Proposed		RFC 2026 section 4.1.1 no longer accurately describes IETF Proposed
	Standards.		Standards.
	This document updates the characterization of Proposed Standards but		This document updates the characterization of Proposed Standards from
	does not speak to or alter the standard maintenance procedures from		RFC2026 but does not speak to or alter the standard maintenance
	RFC 2026 and RFC 6410 [RFC6410].		procedures from RFC 2026 and RFC 6410 [RFC6410].
	2. IESG Reveiew of Proposed Standards		2. IESG Reveiew of Proposed Standards
	The entry-level maturity for the standards track is "Proposed		The entry-level maturity for the standards track is "Proposed
	Standard". A specific action by the IESG is required to move a		Standard". A specific action by the IESG is required to move a
	specification onto the standards track at the "Proposed Standard"		specification onto the standards track at the "Proposed Standard"
	level.		level.
	Initially it was assumed that most IETF technical specifications		Initially it was assumed that most IETF technical specifications
	would progress through a series of maturity stages starting with		would progress through a series of maturity stages starting with
	skipping to change at page 3, line 38 ¶		skipping to change at page 3, line 42 ¶
	A Proposed Standard will have no known technical omissions with		A Proposed Standard will have no known technical omissions with
	respect to the requirements placed upon it. Proposed Standards are		respect to the requirements placed upon it. Proposed Standards are
	of such quality that implementations can be deployed in the Internet.		of such quality that implementations can be deployed in the Internet.
	However, as with all technical specifications, Proposed Standards may		However, as with all technical specifications, Proposed Standards may
	be revised if problems are found or better solutions are identified,		be revised if problems are found or better solutions are identified,
	when experiences with deploying implementations of such technologies		when experiences with deploying implementations of such technologies
	at scale is gathered.		at scale is gathered.
	3.2. Characteristics of Internet Standards		3.2. Characteristics of Internet Standards
	An Internet Standard is characterized by a high degree of technical		A specification for which significant implementation and successful
	maturity and by a generally held belief that the specified protocol		operational experience has been obtained may be elevated to the
	or service provides significant benefit to the Internet community.		Internet Standard level. An Internet Standard (which may simply be
			referred to as a Standard) is characterized by a high degree of
			technical maturity and by a generally held belief that the specified
			protocol or service provides significant benefit to the Internet
			community.
	4. Security Considerations		4. Further Considerations
			While commonly less mature specifications will be published as
			Informational or Experimental RFCs, the IETF may, in exceptional
			cases, publish a specification that does not match the
			characterizations above as a Proposed Standard. In those cases that
			fact will be clearly communicated on the front page of the RFC e.g.
			means of an IESG statement.
			5. Security Considerations
	This document does not directly affect the security of the Internet.		This document does not directly affect the security of the Internet.
	5. IANA Considerations		6. IANA Considerations
	There are no actions for IANA.		There are no actions for IANA.
	6. References		7. References
	[RFC2026] Bradner, S., "The Internet Standards Process -- Revision		[RFC2026] Bradner, S., "The Internet Standards Process -- Revision
	3", BCP 9, RFC 2026, October 1996.		3", BCP 9, RFC 2026, October 1996.
	[RFC6410] Housley, R., Crocker, D. and E. Burger, "Reducing the		[RFC6410] Housley, R., Crocker, D. and E. Burger, "Reducing the
	Standards Track to Two Maturity Levels", BCP 9, RFC 6410,		Standards Track to Two Maturity Levels", BCP 9, RFC 6410,
	October 2011.		October 2011.
	Appendix A. Acknowledgements		Appendix A. Acknowledgements
	This document is inspired by a discussion at the open microphone		This document is inspired by a discussion at the open microphone
	session during the technical plenary at IETF 87. Thanks for [to be		session during the technical plenary at IETF 87. Thanks for John
	added] for motivation, input and review.		Klensin [to be added] for motivation, input and review.
	Appendix B. Internet Draft Editing History		Appendix B. Internet Draft Editing History
	This section is to assist reviewers of this document. It will be		This section is to assist reviewers of this document. It will be
	removed at publication as RFC.		removed at publication as RFC.
	Appendix B.1. Version 00		Appendix B.1. Version 00
	Introduction and motivation		Introduction and motivation
	skipping to change at page 5, line 23 ¶		skipping to change at page 5, line 40 ¶
	NEW:		NEW:
	A Proposed Standard will have no known technical omissions with		A Proposed Standard will have no known technical omissions with
	respect to the requirements placed upon it. Proposed Standards are		respect to the requirements placed upon it. Proposed Standards are
	of such quality that implementations can be deployed in the Internet.		of such quality that implementations can be deployed in the Internet.
	However, as with all technical specifications, Proposed Standards may		However, as with all technical specifications, Proposed Standards may
	be revised if problems are found or better solutions are identified,		be revised if problems are found or better solutions are identified,
	when experiences with deploying implementations of such technologies		when experiences with deploying implementations of such technologies
	at scale is gathered.		at scale is gathered.
	Appendix B.2. Editors versioning info		Appendix B.2. Version 00->01
	$Id: draft-kolkman-proposed-standards-clarified.xml 4 2013-08-02		Added "Updates 2026" and added Sean's initial"
	04:42:37Z olaf $
	Authors' Addresses		Copied the whole characterization pararaph for Internet Standards
			from 2026, instead of only the line that is the actual
			characterization itself.
			Added the Further Consideration section based on discussion on the
			mailinglist.
			Appendix B.3. Editors versioning info
			$Id: draft-kolkman-proposed-standards-clarified.xml 6 2013-09-13
			12:48:48Z olaf $
			Authors' Addresses
	Olaf Kolkman		Olaf Kolkman
	Stichting NLnet Labs		Stichting NLnet Labs
	Science Park 400		Science Park 400
	Amsterdam, 1098 XH		Amsterdam, 1098 XH
	The Netherlands		The Netherlands
	Email: olaf@nlnetlabs.nl		Email: olaf@nlnetlabs.nl
	URI: http://www.nlnetlabs.nl/		URI: http://www.nlnetlabs.nl/
	Scott O. Bradner		Scott O. Bradner
End of changes. 18 change blocks.
	27 lines changed or deleted		52 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/