ianaplanwg-beforeiesg.txt		ianaplanwg-afteriesg.txt
	Background		Background
	==========		==========
	Registries of parameter values for use in IETF protocols are stored		Registries of parameter values for use in IETF protocols are stored
	and maintainted for the IETF by the Internet Assigned Numbers		and maintainted for the IETF by the Internet Assigned Numbers
	Authority (IANA), and are the subject of the "IANA Considerations"		Authority (IANA), and are the subject of the "IANA Considerations"
	section in many RFCs.		section in many RFCs.
	For a number of years, maintenance of the IETF protocol parameters		For a number of years, this IANA function has been provided by the
	registries has been provided by the Internet Corporation for Assigned		Internet Corporation for Assigned Names and Numbers (ICANN). The
	Names and Numbers (ICANN). The IETF's relationship with IANA was		IETF's relationship with IANA was formalized through a Memorandum of
	formalized through a Memorandum of Understanding between the IETF and		Understanding between the IETF and ICANN codified in 2000 with the
	ICANN codified in 2000 with the publication of RFC 2860. Over time,		publication of RFC 2860. Over time, processes and role definitions
	processes and role definitions have evolved, and have been documented		have evolved, and have been documented in supplemental agreements.
	in supplemental agreements.
	ICANN has had a contract with the US Department of Commerce (DoC) to		ICANN has had a contract with the US Department of Commerce (DoC) to
	provide the IANA function, undertaken through the National		provide the IANA function, undertaken through the National
	Telecommunications and Information Administration (NTIA). In March of		Telecommunications and Information Administration (NTIA). In March of
	2014, NTIA announced its intention to transition out of its current		2014, NTIA announced its intention to transition out of its current
	role, meaning that NTIA would not need to renew its contract with		role, meaning that NTIA would not need to renew its contract with
	ICANN when that contract expires 30 September 2015. NTIA requested a		ICANN when that contract expires 30 September 2015. NTIA requested a
	transition proposal be prepared to outline the necessary		transition proposal be prepared to outline the necessary
	arrangements. In the case of the elements of the IANA function		arrangements. In the case of the elements of the IANA function
	concerning the IETF protocol registries, it is likely that the		concerning the IETF protocol registries, it is likely that the
	skipping to change at line 62		skipping to change at line 61
	- ICANN-IETF Supplemental Agreements		- ICANN-IETF Supplemental Agreements
	(updated yearly since 2007, the 2014 version is available at		(updated yearly since 2007, the 2014 version is available at
	http://iaoc.ietf.org/documents/		http://iaoc.ietf.org/documents/
	2014-ICANN-IETF-MoU-Supplemental-Agreement-Executed.pdf)		2014-ICANN-IETF-MoU-Supplemental-Agreement-Executed.pdf)
	This working group is chartered solely with respect to the planning		This working group is chartered solely with respect to the planning
	needed for the transition, and is not meant to cover other topics		needed for the transition, and is not meant to cover other topics
	related to IANA. Possible improvements outside that scope will be set		related to IANA. Possible improvements outside that scope will be set
	aside for future consideration. However, the mechanisms required to		aside for future consideration. However, the mechanisms required to
	address the removal of the overarching NTIA contract may require		address the removal of the overarching NTIA contract may require
	additional documentation or agreements.		additional documentation or agreements. The WG will identify, but
			not create, such required agreements.
	Should proposals made by other communities regarding the		Should proposals made by other communities regarding the
	transition of other IANA functions affect the IETF protocol parameter		transition of other IANA functions affect the IETF protocol parameter
	registries or the IETF, the WG may also review and comment on them.		registries or the IETF, the WG may also review and comment on them.
	Some parts of the transition proposal may need to document detailed		Fully documenting the interaction between the IETF and the operator
	terms of agreements or other details of procedures that are normally		of IETF protocol parameters registries may require detailed terms of
	delegated to and handled by the IAB or IAOC. The working group will		agreements or other details of procedures that are normally delegated
	not attempt to produce or discuss documentation for these details, but		to and handled by the IAB or IAOC. The working group will not attempt
	will request the IAB or IAOC to provide them ready for submission as		to produce or discuss documentation for these details, but will
	part of the final proposal.		request the IAB or IAOC to provide them separately.
	The WG shall seek the expertise of the IAB IANA Strategy Program to		The WG shall seek the expertise of the IAB IANA Evolution Program to
	formulate its output. It is expected that members of the IAB IANA		formulate its output. It is expected that members of the IAB IANA
	Strategy Program will actively participate in the WG.		Evolution Program will actively participate in the WG.
End of changes. 5 change blocks.
	15 lines changed or deleted		15 lines changed or added
This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/