< draft-leiba-cotton-iana-5226bis-07.txt		draft-leiba-cotton-iana-5226bis-08.txt >
	Network Working Group M. Cotton		Network Working Group M. Cotton
	Internet-Draft ICANN		Internet-Draft ICANN
	BCP: 26 B. Leiba		BCP: 26 B. Leiba
	Obsoletes: 5226 (if approved) Huawei Technologies		Obsoletes: 5226 (if approved) Huawei Technologies
	Intended status: Best Current Practice T. Narten		Intended status: Best Current Practice T. Narten
	Expires: February 28, 2015 IBM Corporation		Expires: April 02, 2015 IBM Corporation
	August 29, 2014		October 01, 2014
	Guidelines for Writing an IANA Considerations Section in RFCs		Guidelines for Writing an IANA Considerations Section in RFCs
	draft-leiba-cotton-iana-5226bis-07		draft-leiba-cotton-iana-5226bis-08
	Abstract		Abstract
	Many protocols make use of points of extensibility that use constants		Many protocols make use of points of extensibility that use constants
	to identify various protocol parameters. To ensure that the values		to identify various protocol parameters. To ensure that the values
	used in these fields do not have conflicting uses, and to promote		used in these fields do not have conflicting uses, and to promote
	interoperability, their allocation is often coordinated by a central		interoperability, their allocation is often coordinated by a central
	authority. For IETF protocols, that role is filled by the Internet		authority. For IETF protocols, that role is filled by the Internet
	Assigned Numbers Authority (IANA).		Assigned Numbers Authority (IANA).
	skipping to change at page 1, line 48 ¶		skipping to change at page 1, line 48 ¶
	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 28, 2015.		This Internet-Draft will expire on April 02, 2015.
	Copyright Notice		Copyright Notice
	Copyright (c) 2014 IETF Trust and the persons identified as the		Copyright (c) 2014 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 6, line 53 ¶		skipping to change at page 6, line 53 ¶
	In particular, such instructions MUST include:		In particular, such instructions MUST include:
	The name of the registry (or sub-registry)		The name of the registry (or sub-registry)
	This name will appear on the IANA web page and will be referred to		This name will appear on the IANA web page and will be referred to
	in future documents that need to allocate a value from the new		in future documents that need to allocate a value from the new
	space. The full name (and abbreviation, if appropriate) should be		space. The full name (and abbreviation, if appropriate) should be
	provided. It is highly desirable that the chosen name not be		provided. It is highly desirable that the chosen name not be
	easily confused with the name of another registry.		easily confused with the name of another registry.
	When creating a sub-registry, the registry that it is a part of		When creating a sub-registry, the registry that it is a part of
	must be identified using its full name, exactly as it appears in		MUST be identified using its full name, exactly as it appears in
	the IANA registry list.		the IANA registry list.
	Providing a URL to precisely identify the registry helps IANA		Providing a URL to precisely identify the registry helps IANA
	understand the request. Such URLs can be removed from the RFC		understand the request. Such URLs can be removed from the RFC
	prior to final publication. If they are to be left in, it is		prior to final publication. If they are to be left in, it is
	important that they be permanent links -- IANA intends to include		important that they be permanent links. IANA intends to include
	the permalink for each registry in the registry header. [[*****		the permalink for each registry in the registry header. Until
	This is not yet done, but is planned. *****]]		that is done, IANA can answer questions about the correct URLs to
			use.
	For example, a document could contain something like this:		For example, a document could contain something like this:
	This registration should be made in the Foobar Operational		This registration should be made in the Foobar Operational
	Parameters registry, located at <http://www.iana.org/		Parameters registry, located at <http://www.iana.org/
	assignments/foobar-registry>.		assignments/foobar-registry>.
	It might be tempting to use the URL that appears in your web		It might be tempting to use the URL that appears in your web
	browser's address bar, which might look something like this for		browser's address bar, which might look something like this for
	the example above:		the example above:
	skipping to change at page 7, line 51 ¶		skipping to change at page 7, line 53 ¶
	on strings, and such), and the exact format in which registry		on strings, and such), and the exact format in which registry
	values should be displayed. For numeric assignments, one should		values should be displayed. For numeric assignments, one should
	specify whether values are to be recorded in decimal, in		specify whether values are to be recorded in decimal, in
	hexadecimal, or in some other format. For strings, the encoding		hexadecimal, or in some other format. For strings, the encoding
	format should be specified (ASCII, UTF8, etc.).		format should be specified (ASCII, UTF8, etc.).
	Initial assignments and reservations		Initial assignments and reservations
	Any initial assignments or registrations to be included. In		Any initial assignments or registrations to be included. In
	addition, any ranges that are to be reserved for "Private Use",		addition, any ranges that are to be reserved for "Private Use",
	"Reserved", "Unassigned", etc. should be indicated.		"Reserved", "Unassigned", etc. (see Section 6) should be
			indicated.
	For example, a document might specify a new registry by including:		For example, a document might specify a new registry by including:
	---------------------------------------------------------------		---------------------------------------------------------------
	X. IANA Considerations		X. IANA Considerations
	This document defines a new DHCP option, entitled "FooBar" (see		This document defines a new DHCP option, entitled "FooBar" (see
	Section y), assigned a value of TBD1 from the DHCP Option space		Section y), assigned a value of TBD1 from the DHCP Option space
	[to be removed upon publication:		[to be removed upon publication:
End of changes. 6 change blocks.
	9 lines changed or deleted		11 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/