< draft-housley-number-registries-00.txt		draft-housley-number-registries-01.txt >
	Internet-Draft R. Housley		Internet-Draft R. Housley
	Intended Status: Informational Vigil Security		Intended Status: Informational Vigil Security
	Expires: 2 June 2014 2 December 2013		Expires: 12 June 2014 12 December 2013
	Internet Numbers Registries		Internet Numbers Registries
	<draft-housley-number-registries-00.txt>		<draft-housley-number-registries-01.txt>
	Abstract		Abstract
	RFC 7020 provides information about the Internet Numbers Registry		RFC 7020 provides information about the Internet Numbers Registry
	System and how it is used in the distribution of autonomous system		System and how it is used in the distribution of autonomous system
	(AS) numbers and globally unique unicast Internet Protocol (IP)		(AS) numbers and globally unique unicast Internet Protocol (IP)
	address space.		address space.
	This companion document identifies the IANA registries that are part		This companion document identifies the IANA registries that are part
	of the Internet Numbers Registry System at this time.		of the Internet Numbers Registry System at this time.
	skipping to change at page 2, line 47 ¶		skipping to change at page 3, line 5 ¶
	65535 of the 32-bit AS number space.		65535 of the 32-bit AS number space.
	The allocation and registration functions for all non-reserved AS		The allocation and registration functions for all non-reserved AS
	numbers are handled by the Internet Numbers Registry System in		numbers are handled by the Internet Numbers Registry System in
	accordance with policies developed by the Regional Internet		accordance with policies developed by the Regional Internet
	Registries (RIRs).		Registries (RIRs).
	Reservations of special-purpose AS Numbers are made through Internet		Reservations of special-purpose AS Numbers are made through Internet
	Standards actions.		Standards actions.
	At this time, the special-purpose AS numbers are:
	Internet Numbers Registries December 2013		Internet Numbers Registries December 2013
			At this time, the special-purpose AS numbers are:
	AS Numbers Reason for Reservation		AS Numbers Reason for Reservation
	--------------------- -------------------------------------------		--------------------- -------------------------------------------
	0 Reserved by [draft-ietf-idr-as0]		0 Reserved by [draft-ietf-idr-as0]
	23456 AS_TRANS; reserved by [RFC6793]		23456 AS_TRANS; reserved by [RFC6793]
	64496-64511 For documentation and sample code; reserved		64496-64511 For documentation and sample code; reserved
	by [RFC5398]		by [RFC5398]
	64512-65534 For private use; reserved by [RFC6996]		64512-65534 For private use; reserved by [RFC6996]
	65535 Reserved by [RFC1930]		65535 Reserved by [RFC1930]
	65536-65551 For documentation and sample code; reserved		65536-65551 For documentation and sample code; reserved
	by [RFC5398]		by [RFC5398]
	skipping to change at page 4, line 32 ¶		skipping to change at page 4, line 32 ¶
	At this time, the special-purpose IPv6 addresses are:		At this time, the special-purpose IPv6 addresses are:
	IPv6 Addresses Reason for Reservation		IPv6 Addresses Reason for Reservation
	-------------- ----------------------------------------------------		-------------- ----------------------------------------------------
	0::/8 For unspecified, loopback, IPv4-compatible, IPv4-		0::/8 For unspecified, loopback, IPv4-compatible, IPv4-
	mapped, link-local, site-local, and addresses		mapped, link-local, site-local, and addresses
	assigned by the IETF; reserved by [RFC4291]		assigned by the IETF; reserved by [RFC4291]
	100::/64 For discard-only addresses; reserved by [RFC6666]		100::/64 For discard-only addresses; reserved by [RFC6666]
	2001:0::/23 For IETF protocol assignments; reserved by [RFC2928]		2001:0::/23 For IETF protocol assignments; reserved by [RFC2928]
	2001:0::/32 For TEREDO; reserved by [RFC4380]
	2001:2::/48 For benchmarking; reserved by [RFC5180]
	2001:db8::/32 For documentation; reserved by [RFC3849]		2001:db8::/32 For documentation; reserved by [RFC3849]
	2001:10::/28 For ORCHID; reserved by [RFC4843]
	2002::/16 For 6to4; reserved by [RFC3056]		2002::/16 For 6to4; reserved by [RFC3056]
	3. IANA Considerations		3. IANA Considerations
	An Internet Standards action that reserves special-purpose AS numbers		"IETF Review" as defined in [RFC5226] is required to reserve special-
	or IPv4 addresses or IPv6 addresses is recorded in the relevant IANA		purpose AS numbers or IPv4 addresses or IPv6 addresses. These
	registry as a Special Purpose designation, referencing the IESG-		reservations are recorded in the relevant IANA registry with a
	approved RFC that documents the reservation.		Special Purpose designation, referencing the IESG-approved RFC that
			documents the reservation.
	IANA may designate special-purpose AS numbers or IPv4 addresses or		IANA may designate special-purpose AS numbers or IPv4 addresses or
	IPv6 addresses to support testing, IETF experimental activities, or		IPv6 addresses to support testing, IETF experimental activities, or
	other special uses (e.g., anycast) associated with a standards-track		other special uses (e.g., anycast) associated with a standards-track
	protocol.		protocol.
	4. Security Considerations		4. Security Considerations
	This document identifies the IANA registries that are part of the		This document identifies the IANA registries that are part of the
	Internet Numbers Registry System at this time. It does not change		Internet Numbers Registry System at this time. It does not change
	the security posture of the Internet in any way.		the security posture of the Internet in any way.
	Internet Numbers Registries December 2013		Internet Numbers Registries December 2013
	5. Informative References		5. References
	[draft-ietf-idr-as0] W. Kumari, W., R. Bush, H. Schiller, and K.		5.1. Normative References
	Patel, "Codification of AS 0 processing", work-in-progress,
	August 2012.		[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
			IANA Considerations Section in RFCs", BCP 26, RFC 5226, May
			2008.
			5.2. Informative References
			[draft-ietf-idr-as0] Kumari, W., R. Bush, H. Schiller, and K. Patel,
			"Codification of AS 0 processing", work-in-progress, August
			2012.
	[RFC1122] Braden, R., Ed., "Requirements for Internet Hosts -		[RFC1122] Braden, R., Ed., "Requirements for Internet Hosts -
	Communication Layers", STD 3, RFC 1122, October 1989.		Communication Layers", STD 3, RFC 1122, October 1989.
	[RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G.,		[RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G.,
	and E. Lear, "Address Allocation for Private Internets",		and E. Lear, "Address Allocation for Private Internets",
	BCP 5, RFC 1918, February 1996.		BCP 5, RFC 1918, February 1996.
	[RFC1930] Hawkinson, J. and T. Bates, "Guidelines for creation,		[RFC1930] Hawkinson, J. and T. Bates, "Guidelines for creation,
	selection, and registration of an Autonomous System (AS)",		selection, and registration of an Autonomous System (AS)",
	skipping to change at page 5, line 46 ¶		skipping to change at page 5, line 54 ¶
	[RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix		[RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix
	Reserved for Documentation", RFC 3849, July 2004.		Reserved for Documentation", RFC 3849, July 2004.
	[RFC3927] Cheshire, S., Aboba, B., and E. Guttman, "Dynamic		[RFC3927] Cheshire, S., Aboba, B., and E. Guttman, "Dynamic
	Configuration of IPv4 Link-Local Addresses", RFC 3927, May		Configuration of IPv4 Link-Local Addresses", RFC 3927, May
	2005.		2005.
	[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing		[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
	Architecture", RFC 4291, February 2006.		Architecture", RFC 4291, February 2006.
	[RFC4380] Huitema, C., "Teredo: Tunneling IPv6 over UDP through		[RFC5398] Huston, G., "Autonomous System (AS) Number Reservation for
	Network Address Translations (NATs)", RFC 4380, February
	2006.
	[RFC4843] Nikander, P., Laganier, J., and F. Dupont, "An IPv6 Prefix
	for Overlay Routable Cryptographic Hash Identifiers
	(ORCHID)", RFC 4843, April 2007.
	Internet Numbers Registries December 2013		Internet Numbers Registries December 2013
	[RFC5180] Popoviciu, C., Hamza, A., Van de Velde, G., and D.
	Dugatkin, "IPv6 Benchmarking Methodology for Network
	Interconnect Devices", RFC 5180, May 2008.
	[RFC5398] Huston, G., "Autonomous System (AS) Number Reservation for
	Documentation Use", RFC 5398, December 2008.		Documentation Use", RFC 5398, December 2008.
	[RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks		[RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks
	Reserved for Documentation", RFC 5737, January 2010.		Reserved for Documentation", RFC 5737, January 2010.
	[RFC6598] Weil, J., Kuarsingh, V., Donley, C., Liljenstolpe, C., and		[RFC6598] Weil, J., Kuarsingh, V., Donley, C., Liljenstolpe, C., and
	M. Azinger, "IANA-Reserved IPv4 Prefix for Shared Address		M. Azinger, "IANA-Reserved IPv4 Prefix for Shared Address
	Space", BCP 153, RFC 6598, April 2012.		Space", BCP 153, RFC 6598, April 2012.
	[RFC6666] Hilliard, N. and D. Freedman, "A Discard Prefix for IPv6",		[RFC6666] Hilliard, N. and D. Freedman, "A Discard Prefix for IPv6",
	skipping to change at page 6, line 37 ¶		skipping to change at page 6, line 32 ¶
	[RFC6890] Cotton, M., Vegoda, L., Bonica, R., Ed., and B. Haberman,		[RFC6890] Cotton, M., Vegoda, L., Bonica, R., Ed., and B. Haberman,
	"Special-Purpose IP Address Registries", BCP 153, RFC 6890,		"Special-Purpose IP Address Registries", BCP 153, RFC 6890,
	April 2013.		April 2013.
	[RFC6996] Mitchell, J., "Autonomous System (AS) Reservation for		[RFC6996] Mitchell, J., "Autonomous System (AS) Reservation for
	Private Use", BCP 6, RFC 6996, July 2013.		Private Use", BCP 6, RFC 6996, July 2013.
	Acknowledgements		Acknowledgements
	Many thanks to John Curran and Geoff Huston for their review and		Many thanks to Jari Arkko, John Curran and Geoff Huston for their
	comment.		insightful review and comment.
	Author's Addresses		Author's Addresses
	Russell Housley		Russell Housley
	Vigil Security, LLC		Vigil Security, LLC
	918 Spring Knoll Drive		918 Spring Knoll Drive
	Herndon, VA 20170		Herndon, VA 20170
	USA		USA
	EMail: housley@vigilsec.com		EMail: housley@vigilsec.com
End of changes. 12 change blocks.
	29 lines changed or deleted		24 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/