< draft-leiba-netmod-regpolicy-update-00.txt		draft-leiba-netmod-regpolicy-update-01.txt >
	Network Working Group B. Leiba		Network Working Group B. Leiba
	Internet-Draft Huawei Technologies		Internet-Draft Huawei Technologies
	Intended status: Best Current Practice October 12, 2015		Updates: 6241 (if approved) October 16, 2015
	Expires: April 12, 2016		Intended status: Best Current Practice
			Expires: April 16, 2016
	Changing the Registration Policy for the NETCONF Capability URNs		Changing the Registration Policy for the NETCONF Capability URNs
	Registry		Registry
	draft-leiba-netmod-regpolicy-update-00		draft-leiba-netmod-regpolicy-update-01
	Abstract		Abstract
	The registration policy for the Network Configuration Protocol		The registration policy for the Network Configuration Protocol
	(NETCONF) Capability URNs registry, set up by RFC 6241, has turned		(NETCONF) Capability URNs registry, set up by RFC 6241, has turned
	out to be unnecessarily strict. This document changes that		out to be unnecessarily strict. This document changes that
	registration policy to "IETF Review", allowing registrations from		registration policy to "IETF Review", allowing registrations from
	certain well reviewed Experimental RFCs, in addition to Standards		certain well reviewed Experimental RFCs, in addition to Standards
	Track RFCs.		Track RFCs.
	skipping to change at page 1, line 36 ¶		skipping to change at page 1, line 37 ¶
	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 April 12, 2016.		This Internet-Draft will expire on April 16, 2016.
	Copyright Notice		Copyright Notice
	Copyright (c) 2015 IETF Trust and the persons identified as the		Copyright (c) 2015 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
	skipping to change at page 2, line 33 ¶		skipping to change at page 2, line 33 ¶
	to be carefully reviewed through IETF Last Call and consultation with		to be carefully reviewed through IETF Last Call and consultation with
	relevant working groups, such as NETCONF. The Operations and		relevant working groups, such as NETCONF. The Operations and
	Management Area Directors should confirm the appropriate level of		Management Area Directors should confirm the appropriate level of
	review during IESG Evaluation.		review during IESG Evaluation.
	3. Security Considerations		3. Security Considerations
	This document is purely procedural, and there are no related security		This document is purely procedural, and there are no related security
	considerations.		considerations.
	4. References		4. NOTE
			[RFC Editor: Please remove this section and make sure the title of
			the references section is "Normative References". The version of
			xml2rfc that I'm using ignores my section title and just calls it
			"References".]
			5. References
	[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an		[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
	IANA Considerations Section in RFCs", BCP 26, RFC 5226,		IANA Considerations Section in RFCs", BCP 26, RFC 5226,
	May 2008.		May 2008.
	[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J.Ed.,		[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J.Ed.,
	and A. Bierman, Ed., "Network Configuration Protocol		and A. Bierman, Ed., "Network Configuration Protocol
	(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,		(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
	<http://www.rfc-editor.org/info/rfc6241>.		<http://www.rfc-editor.org/info/rfc6241>.
End of changes. 4 change blocks.
	5 lines changed or deleted		13 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/