< draft-ietf-sidr-iana-objects-01.txt		draft-ietf-sidr-iana-objects-02.txt >
	Network Working Group T. Manderson		Network Working Group T. Manderson
	Internet-Draft L. Vegoda		Internet-Draft L. Vegoda
	Intended status: Standards Track ICANN		Intended status: Standards Track ICANN
	Expires: August 20, 2011 S. Kent		Expires: October 10, 2011 S. Kent
	BBN		BBN
	February 16, 2011		April 8, 2011
	RPKI Objects issued by IANA		RPKI Objects issued by IANA
	draft-ietf-sidr-iana-objects-01.txt		draft-ietf-sidr-iana-objects-02.txt
	Abstract		Abstract
	This document provides specific direction to IANA as to the Resource		This document provides specific direction to IANA as to the Resource
	Public Key Infrastructure (RPKI) objects it should issue.		Public Key Infrastructure (RPKI) objects it should issue.
	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.
	skipping to change at page 1, line 33 ¶		skipping to change at page 1, line 33 ¶
	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 August 20, 2011.		This Internet-Draft will expire on October 10, 2011.
	Copyright Notice		Copyright Notice
	Copyright (c) 2011 IETF Trust and the persons identified as the		Copyright (c) 2011 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		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 2, line 22 ¶		skipping to change at page 2, line 22 ¶
	6. Unallocated Resources . . . . . . . . . . . . . . . . . . . . 8		6. Unallocated Resources . . . . . . . . . . . . . . . . . . . . 8
	7. Special Purpose Registry Resources . . . . . . . . . . . . . . 9		7. Special Purpose Registry Resources . . . . . . . . . . . . . . 9
	8. Multicast . . . . . . . . . . . . . . . . . . . . . . . . . . 10		8. Multicast . . . . . . . . . . . . . . . . . . . . . . . . . . 10
	9. Informational Objects . . . . . . . . . . . . . . . . . . . . 11		9. Informational Objects . . . . . . . . . . . . . . . . . . . . 11
	10. Certificates and CRLs . . . . . . . . . . . . . . . . . . . . 12		10. Certificates and CRLs . . . . . . . . . . . . . . . . . . . . 12
	11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13		11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
	12. Security Considerations . . . . . . . . . . . . . . . . . . . 14		12. Security Considerations . . . . . . . . . . . . . . . . . . . 14
	13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15		13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
	14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16		14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
	14.1. Normative References . . . . . . . . . . . . . . . . . . 16		14.1. Normative References . . . . . . . . . . . . . . . . . . 16
	14.2. Informative References . . . . . . . . . . . . . . . . . 17		14.2. Informative References . . . . . . . . . . . . . . . . . 16
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19		Appendix A. IANA Reserved IPv4 Address Blocks . . . . . . . . . . 19
			Appendix B. IANA Reserved IPv6 Address Blocks . . . . . . . . . . 20
			Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22
	1. Requirements Notation		1. Requirements Notation
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in [RFC2119].		document are to be interpreted as described in [RFC2119].
	2. Introduction		2. Introduction
	An Infrastructure to Support Secure Internet Routing		An Infrastructure to Support Secure Internet Routing
	skipping to change at page 7, line 10 ¶		skipping to change at page 7, line 10 ¶
	"Not intended to be (publicly) routed": This phrase refers to		"Not intended to be (publicly) routed": This phrase refers to
	prefixes that are not meant to be represented in the global Internet		prefixes that are not meant to be represented in the global Internet
	routing table (for example 192.168/16, [RFC1918]).		routing table (for example 192.168/16, [RFC1918]).
	5. Reserved Resources		5. Reserved Resources
	Reserved IPv4 and IPv6 resources are held back for various reasons by		Reserved IPv4 and IPv6 resources are held back for various reasons by
	IETF action. Generally such resources are not intended to be		IETF action. Generally such resources are not intended to be
	globally routed. An example of such a reservation is 127.0.0.0/8		globally routed. An example of such a reservation is 127.0.0.0/8
	[RFC5735].		[RFC5735]. See Appendix A (Appendix A) and B (Appendix B) for IANA
			reserved resources.
	IANA SHOULD issue an AS0 ROA for all reserved IPv4 and IPv6 resources		IANA SHOULD issue an AS0 ROA for all reserved IPv4 and IPv6 resources
	not intended to be routed.		not intended to be routed.
	There are a small number of reserved resources which are intended to		There are a small number of reserved resources which are intended to
	be routed, for example 192.88.99.0/24 [RFC3068].		be routed, for example 192.88.99.0/24 [RFC3068]. See Appendix A
			(Appendix A) and B (Appendix B) for IANA reserved resources.
	IANA MUST NOT issue any ROAs (AS0 or otherwise) for reserved		IANA MUST NOT issue any ROAs (AS0 or otherwise) for reserved
	resources that are expected to be globally routed.		resources that are expected to be globally routed.
	6. Unallocated Resources		6. Unallocated Resources
	Internet Number Resources that have not yet been allocated for		Internet Number Resources that have not yet been allocated for
	special purposes [RFC5736], to Regional Internet Registries (RIRs),		special purposes [RFC5736], to Regional Internet Registries (RIRs),
	or to others are considered as not intended to be globally routed.		or to others are considered as not intended to be globally routed.
	skipping to change at page 10, line 28 ¶		skipping to change at page 10, line 28 ¶
	224.1.0.0-224.1.255.255 (224.1/16)		224.1.0.0-224.1.255.255 (224.1/16)
	- RESERVED		- RESERVED
	224.5.0.0-224.251.255.255 (251 /16s)		224.5.0.0-224.251.255.255 (251 /16s)
	225.0.0.0-231.255.255.255 (7 /8s)		225.0.0.0-231.255.255.255 (7 /8s)
	IPv6:		IPv6:
	- Node-Local Scope Multicast Addresses		- Node-Local Scope Multicast Addresses
	- Link-Local Scope Multicast Addresses		- Link-Local Scope Multicast Addresses
	IANA MUST NOT issue any ROAs (AS0 or otherwise) for any other		IANA MUST NOT issue any ROAs (AS0 or otherwise) for any other
	multicast addresses unless directed.		multicast addresses unless directed by an IESG approved standards
			track document with an appropriate IANA Considerations section.
	9. Informational Objects		9. Informational Objects
	One informational object that can exist at a publication point of an		One informational object that can exist at a publication point of an
	RPKI repository is the Ghostbusters Record		RPKI repository is the Ghostbusters Record
	[I-D.ietf-sidr-ghostbusters].		[I-D.ietf-sidr-ghostbusters].
	IANA MUST issue a ghostbusters object appropriate in content for the		IANA MUST issue a ghostbusters object appropriate in content for the
	resources IANA maintains.		resources IANA maintains.
	skipping to change at page 16, line 11 ¶		skipping to change at page 16, line 11 ¶
	The authors acknowledge Dave Meyer for helpful direction with regard		The authors acknowledge Dave Meyer for helpful direction with regard
	to multicast assignments.		to multicast assignments.
	14. References		14. References
	14.1. Normative References		14.1. Normative References
	[I-D.ietf-sidr-arch]		[I-D.ietf-sidr-arch]
	Lepinski, M. and S. Kent, "An Infrastructure to Support		Lepinski, M. and S. Kent, "An Infrastructure to Support
	Secure Internet Routing", draft-ietf-sidr-arch-11 (work in		Secure Internet Routing", draft-ietf-sidr-arch-12 (work in
	progress), September 2010.		progress), February 2011.
	[I-D.ietf-sidr-cp]		[I-D.ietf-sidr-cp]
	Kent, S., Kong, D., Seo, K., and R. Watro, "Certificate		Kent, S., Kong, D., Seo, K., and R. Watro, "Certificate
	Policy (CP) for the Resource PKI (RPKI",		Policy (CP) for the Resource PKI (RPKI",
	draft-ietf-sidr-cp-16 (work in progress), December 2010.		draft-ietf-sidr-cp-16 (work in progress), December 2010.
	[I-D.ietf-sidr-ghostbusters]		[I-D.ietf-sidr-ghostbusters]
	Bush, R., "The RPKI Ghostbusters Record",		Bush, R., "The RPKI Ghostbusters Record",
	draft-ietf-sidr-ghostbusters-00 (work in progress),		draft-ietf-sidr-ghostbusters-03 (work in progress),
	December 2010.		March 2011.
	[I-D.ietf-sidr-res-certs]		[I-D.ietf-sidr-res-certs]
	Huston, G., Michaelson, G., and R. Loomans, "A Profile for		Huston, G., Michaelson, G., and R. Loomans, "A Profile for
	X.509 PKIX Resource Certificates",		X.509 PKIX Resource Certificates",
	draft-ietf-sidr-res-certs-21 (work in progress),		draft-ietf-sidr-res-certs-21 (work in progress),
	December 2010.		December 2010.
	[I-D.ietf-sidr-roa-format]		[I-D.ietf-sidr-roa-format]
	Lepinski, M., Kent, S., and D. Kong, "A Profile for Route		Lepinski, M., Kent, S., and D. Kong, "A Profile for Route
	Origin Authorizations (ROAs)",		Origin Authorizations (ROAs)",
	draft-ietf-sidr-roa-format-09 (work in progress),		draft-ietf-sidr-roa-format-10 (work in progress),
	November 2010.		February 2011.
	[I-D.ietf-sidr-roa-validation]		[I-D.ietf-sidr-roa-validation]
	Huston, G. and G. Michaelson, "Validation of Route		Huston, G. and G. Michaelson, "Validation of Route
	Origination using the Resource Certificate PKI and ROAs",		Origination using the Resource Certificate PKI and ROAs",
	draft-ietf-sidr-roa-validation-10 (work in progress),		draft-ietf-sidr-roa-validation-10 (work in progress),
	November 2010.		November 2010.
	[I-D.ietf-sidr-rpki-manifests]		[I-D.ietf-sidr-rpki-manifests]
	Austein, R., Huston, G., Kent, S., and M. Lepinski,		Austein, R., Huston, G., Kent, S., and M. Lepinski,
	"Manifests for the Resource Public Key Infrastructure",		"Manifests for the Resource Public Key Infrastructure",
	draft-ietf-sidr-rpki-manifests-09 (work in progress),		draft-ietf-sidr-rpki-manifests-09 (work in progress),
	November 2010.		November 2010.
			14.2. Informative References
			[I-D.ietf-sidr-ltamgmt]
			Kent, S. and M. Reynolds, "Local Trust Anchor Management
			for the Resource Public Key Infrastructure",
			draft-ietf-sidr-ltamgmt-00 (work in progress),
			November 2010.
			[I-D.ietf-sidr-usecases]
			Manderson, T., Sriram, K., and R. White, "Use Cases and
			interpretation of RPKI objects for issuers and relying
			parties", draft-ietf-sidr-usecases-01 (work in progress),
			December 2010.
			[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,
			September 1981.
			[RFC0919] Mogul, J., "Broadcasting Internet Datagrams", STD 5,
			RFC 919, October 1984.
			[RFC0922] Mogul, J., "Broadcasting Internet datagrams in the
			presence of subnets", STD 5, RFC 922, October 1984.
			[RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5,
			RFC 1112, August 1989.
			[RFC1122] Braden, R., "Requirements for Internet Hosts -
			Communication Layers", STD 3, RFC 1122, October 1989.
	[RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and		[RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and
	E. Lear, "Address Allocation for Private Internets",		E. Lear, "Address Allocation for Private Internets",
	BCP 5, RFC 1918, February 1996.		BCP 5, RFC 1918, February 1996.
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
			[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
			(IPv6) Specification", RFC 2460, December 1998.
			[RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for
			Network Interconnect Devices", RFC 2544, March 1999.
	[RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of		[RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of
	Understanding Concerning the Technical Work of the		Understanding Concerning the Technical Work of the
	Internet Assigned Numbers Authority", RFC 2860, June 2000.		Internet Assigned Numbers Authority", RFC 2860, June 2000.
	[RFC3068] Huitema, C., "An Anycast Prefix for 6to4 Relay Routers",		[RFC3068] Huitema, C., "An Anycast Prefix for 6to4 Relay Routers",
	RFC 3068, June 2001.		RFC 3068, June 2001.
	[RFC3779] Lynn, C., Kent, S., and K. Seo, "X.509 Extensions for IP		[RFC3779] Lynn, C., Kent, S., and K. Seo, "X.509 Extensions for IP
	Addresses and AS Identifiers", RFC 3779, June 2004.		Addresses and AS Identifiers", RFC 3779, June 2004.
	[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.
			[RFC3879] Huitema, C. and B. Carpenter, "Deprecating Site Local
			Addresses", RFC 3879, September 2004.
			[RFC3927] Cheshire, S., Aboba, B., and E. Guttman, "Dynamic
			Configuration of IPv4 Link-Local Addresses", RFC 3927,
			May 2005.
	[RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway		[RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
	Protocol 4 (BGP-4)", RFC 4271, January 2006.		Protocol 4 (BGP-4)", RFC 4271, January 2006.
	[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		[RFC4380] Huitema, C., "Teredo: Tunneling IPv6 over UDP through
	Network Address Translations (NATs)", RFC 4380,		Network Address Translations (NATs)", RFC 4380,
	February 2006.		February 2006.
			[RFC4843] Nikander, P., Laganier, J., and F. Dupont, "An IPv6 Prefix
			for Overlay Routable Cryptographic Hash Identifiers
			(ORCHID)", RFC 4843, April 2007.
	[RFC5180] Popoviciu, C., Hamza, A., Van de Velde, G., and D.		[RFC5180] Popoviciu, C., Hamza, A., Van de Velde, G., and D.
	Dugatkin, "IPv6 Benchmarking Methodology for Network		Dugatkin, "IPv6 Benchmarking Methodology for Network
	Interconnect Devices", RFC 5180, May 2008.		Interconnect Devices", RFC 5180, May 2008.
	[RFC5735] Cotton, M. and L. Vegoda, "Special Use IPv4 Addresses",		[RFC5735] Cotton, M. and L. Vegoda, "Special Use IPv4 Addresses",
	BCP 153, RFC 5735, January 2010.		BCP 153, RFC 5735, January 2010.
	[RFC5736] Huston, G., Cotton, M., and L. Vegoda, "IANA IPv4 Special		[RFC5736] Huston, G., Cotton, M., and L. Vegoda, "IANA IPv4 Special
	Purpose Address Registry", RFC 5736, January 2010.		Purpose Address Registry", RFC 5736, January 2010.
			[RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks
			Reserved for Documentation", RFC 5737, January 2010.
	[RFC5771] Cotton, M., Vegoda, L., and D. Meyer, "IANA Guidelines for		[RFC5771] Cotton, M., Vegoda, L., and D. Meyer, "IANA Guidelines for
	IPv4 Multicast Address Assignments", BCP 51, RFC 5771,		IPv4 Multicast Address Assignments", BCP 51, RFC 5771,
	March 2010.		March 2010.
	14.2. Informative References		Appendix A. IANA Reserved IPv4 Address Blocks
	[I-D.ietf-sidr-ltamgmt]		This list of Address Space and RFCs was correct at the time of
	Kent, S. and M. Reynolds, "Local Trust Anchor Management		writing
	for the Resource Public Key Infrastructure",
	draft-ietf-sidr-ltamgmt-00 (work in progress),
	November 2010.
	[I-D.ietf-sidr-usecases]		IPv4 Address Blocks and the RFCs which direct IANA to Reserve them
	Manderson, T., Sriram, K., and R. White, "Use Cases and
	interpretation of RPKI objects for issuers and relying
	parties", draft-ietf-sidr-usecases-01 (work in progress),
	December 2010.
	[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,		+--------------------+------------------------------------+---------+
	September 1981.		| Prefix | RFC | TBR |
			+--------------------+------------------------------------+---------+
			| 0.0.0.0/8 | RFC1122, Section 3.2.1.3 | No |
			| | | |
			| 10.0.0.0/8 | RFC1918 | No |
			| | | |
			| 127.0.0.0/8 | RFC1122, Section 3.2.1.3 | No |
			| | | |
			| 169.254.0.0/16 | RFC3927 | No |
			| | | |
			| 172.16.0.0/12 | RFC1918 | No |
			| | | |
			| 192.0.0.0/24 | RFC5736 | Various |
			| | | |
			| 192.0.2.0/24 | RFC5737 | No |
			| | | |
			| 192.88.99.0/24 | RFC3068 | Yes |
			| | | |
			| 192.168.0.0/16 | RFC1918 | No |
			| | | |
			| 198.18.0.0/15 | RFC2544 | No |
			| | | |
			| 198.51.100.0/24 | RFC5737 | No |
			| | | |
			| 203.0.113.0/24 | RFC5737 | No |
			| | | |
			| 224.0.0.0/4 | RFC5771 | No |
			| | | |
			| 240.0.0.0/4 | RFC1112, Section 4 | No |
			| | | |
			| 255.255.255.255/32 | RFC919, Section 7 and RFC922, | No |
			| | Section 7 | |
			+--------------------+------------------------------------+---------+
	[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6		TBR: To Be Routed, the intention of the RFC pertaining to the address
	(IPv6) Specification", RFC 2460, December 1998.		block.
			Table 1
			Appendix B. IANA Reserved IPv6 Address Blocks
			This list of Address Space and RFCs was correct at the time of
			writing
			IPv6 Address Blocks and the RFCs which direct IANA to Reserve them
			+----------------+---------+-----+
			| Prefix | RFC | TBR |
			+----------------+---------+-----+
			| 0000::/8 | RFC4291 | No |
			| | | |
			| 0100::/8 | RFC4291 | No |
			| | | |
			| 0200::/7 | RFC4291 | No |
			| | | |
			| 0400::/6 | RFC4291 | No |
			| | | |
			| 0800::/5 | RFC4291 | No |
			| | | |
			| 1000::/4 | RFC4291 | No |
			| | | |
			| 4000::/3 | RFC4291 | No |
			| | | |
			| 6000::/3 | RFC4291 | No |
			| | | |
			| 8000::/3 | RFC4291 | No |
			| | | |
			| A000::/3 | RFC4291 | No |
			| | | |
			| C000::/3 | RFC4291 | No |
			| | | |
			| E000::/4 | RFC4291 | No |
			| | | |
			| F000::/5 | RFC4291 | No |
			| | | |
			| F800::/6 | RFC4291 | No |
			| | | |
			| FC00::/7 | RFC4193 | No |
			| | | |
			| FE00::/9 | RFC4291 | No |
			| | | |
			| FE80::/10 | RFC4291 | No |
			| | | |
			| FEC0::/10 | RFC3879 | No |
			| | | |
			| FF00::/8 | RFC4291 | No |
			| | | |
			| 2001:0002::/48 | RFC5180 | No |
			| | | |
			| 2001:10::/28 | RFC4843 | No |
			+----------------+---------+-----+
			TBR: To Be Routed, the intention of the RFC pertaining to the address
			block.
			Table 2
	Authors' Addresses		Authors' Addresses
	Terry Manderson		Terry Manderson
	ICANN		ICANN
	Email: terry.manderson@icann.org		Email: terry.manderson@icann.org
	Leo Vegoda		Leo Vegoda
	ICANN		ICANN
End of changes. 21 change blocks.
	30 lines changed or deleted		169 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/