Internet DRAFT - draft-manderson-routing-intent
draft-manderson-routing-intent
Network Working Group T. Manderson
Internet-Draft ICANN
Intended status: Standards Track August 17, 2011
Expires: February 18, 2012
Signaling Public Routing Intent (PRI) for Internet Protocol Addresses in
IANA Registries
draft-manderson-routing-intent-02.txt
Abstract
This document provides direction to IANA to mark existing and future
IANA IPv4 and IPv6 allocations with generic terms pertaining to the
Public (global) Routing Intent (PRI).
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 18, 2012.
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Manderson Expires February 18, 2012 [Page 1]
Internet-Draft Routing Intent in IANA Address Registries August 2011
Table of Contents
1. Requirements Notation . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Wording for future IETF Documents . . . . . . . . . . . . . . 6
5. Special Address Registries . . . . . . . . . . . . . . . . . . 7
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
7. Security Considerations . . . . . . . . . . . . . . . . . . . 9
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
9.1. Normative References . . . . . . . . . . . . . . . . . . . 11
9.2. Informative References . . . . . . . . . . . . . . . . . . 11
Appendix A. Example IPv4 Address Registry . . . . . . . . . . . . 12
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 13
Manderson Expires February 18, 2012 [Page 2]
Internet-Draft Routing Intent in IANA Address Registries August 2011
1. Requirements Notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
Manderson Expires February 18, 2012 [Page 3]
Internet-Draft Routing Intent in IANA Address Registries August 2011
2. Introduction
The IANA address registries currently do not have a uniform and
consistent nomenclature to signal if an allocation is intended to be
publicly routed. While some registries, such as the IANA IPv4
Special Purpose Address Registry [RFC5736], include a column
describing routing scope it is the exception. The consequence of
this is that at present the intended routing posture of many
allocations is, at best, implied.
Work is underway in the IETF to design and document a number of
systems or architectures to facilitate the desire to secure the
Internet routing system. [I-D.ietf-sidr-arch] describes one such
architecture. Such work will require an explicit statement as to the
intended public routability of an allocation. Over time several
architectures may come to exist, and in support of the idea of
routing security, this document provides direction to IANA to mark
existing and future IANA IPv4 [RFC0791] and IPv6 [RFC2460]
allocations with generic terms pertaining to the Public (global)
Routing Intent (PRI) and with a granularity that removes any possible
ambiguity in interpreting the address registry.
These well defined generic terms can then be applied in technology
solutions that address routing security, or other routing concerns.
Manderson Expires February 18, 2012 [Page 4]
Internet-Draft Routing Intent in IANA Address Registries August 2011
3. Definitions
Publically Routed: Where the announcement of a prefix contained
within, or representing, an allocation is exchanged between 2 or more
Autonomous Systems that do not share a common and unified routing
policy except for the announcement and acceptance of routes
containing a prefix directly allocated to themselves.
Routable: An IPv4 [RFC0791] or IPv6 [RFC2460] prefix that is intended
to be (publicly) routed.
Not Routable: An IPv4 [RFC0791] or IPv6 [RFC2460] prefix that is NOT
intended to be (publicly) routed.
Manderson Expires February 18, 2012 [Page 5]
Internet-Draft Routing Intent in IANA Address Registries August 2011
4. Wording for future IETF Documents
All future IETF documents that request IANA [RFC5226] to allocate,
assign, or reserve an IPv4 [RFC0791] or IPv6 [RFC2460] address block
MUST include a statement for each and every unique prefix it requests
that describes the routing intent for the prefix. Suitable examples
are:
1) This prefix, 2001:DB8::/32, is to be considered Routable.
2) 2001:DB8::/32 is for private use and intended to be Not Routable.
3) The assignment of 2001:DB8::/32 is intended to be Routable.
Manderson Expires February 18, 2012 [Page 6]
Internet-Draft Routing Intent in IANA Address Registries August 2011
5. Special Address Registries
The IANA IPv4 Special Purpose Address Registry [RFC5736] already
contains a routing scope definition. While this registry is the
exception for address registries, the PRI column MUST be added to the
IANA IPv4 Special Purpose Address Registry leaving the existing
Routing Scope in place for additional information to the reader.
Manderson Expires February 18, 2012 [Page 7]
Internet-Draft Routing Intent in IANA Address Registries August 2011
6. IANA Considerations
This document directs IANA to extend all the IPv4 and IPv6 address
registries to record Public Routing Intent (PRI) as either "Routable"
or "Not Routable". This intent should be initially taken from the
appendices in [I-D.ietf-sidr-iana-objects] for reserved, special use,
and unallocated address space. Address space already allocated to
the Regional Internet Registries or other entities for use on the
public internet MUST be marked as "Routable". Future standards
action IETF documents that request action in all IANA IPv4 or IPv6
addresses registries MUST include a statement pertaining to the
routing intent of the resulting action as described in this document.
Implementation of this document further requires IANA to update the
IPv4 and IPv6 address registries to use a granularity commensurate
with the most specific entry in the address registry. An example
registry can be found in Appendix A (Appendix A).
Manderson Expires February 18, 2012 [Page 8]
Internet-Draft Routing Intent in IANA Address Registries August 2011
7. Security Considerations
This document does not alter the security profile for IANA IPv4
[RFC0791] or IPv6 [RFC2460] address registries.
Manderson Expires February 18, 2012 [Page 9]
Internet-Draft Routing Intent in IANA Address Registries August 2011
8. Acknowledgments
The Author appreciates the review, consideration, and helpful
feedback from Leo Vegoda, Michelle Cotton, Benson Schliesser, Arturo
Servin, and Geoff Huston.
Manderson Expires February 18, 2012 [Page 10]
Internet-Draft Routing Intent in IANA Address Registries August 2011
9. References
9.1. Normative References
[I-D.ietf-sidr-iana-objects]
Manderson, T., Vegoda, L., and S. Kent, "RPKI Objects
issued by IANA", draft-ietf-sidr-iana-objects-03 (work in
progress), May 2011.
9.2. Informative References
[I-D.ietf-sidr-arch]
Lepinski, M. and S. Kent, "An Infrastructure to Support
Secure Internet Routing", draft-ietf-sidr-arch-13 (work in
progress), May 2011.
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,
September 1981.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
[RFC5736] Huston, G., Cotton, M., and L. Vegoda, "IANA IPv4 Special
Purpose Address Registry", RFC 5736, January 2010.
Manderson Expires February 18, 2012 [Page 11]
Internet-Draft Routing Intent in IANA Address Registries August 2011
Appendix A. Example IPv4 Address Registry
This is a truncated example of how the resulting IANA IPv4 address
registry might appear. The existing IANA IPv4 address registry
columns of Designation, Date, and Whois have been removed from this
example for brevity reasons only.
| Prefix | ... | Status | PRI | Note |
| ...
| 198.0/12 | | ALLOCATED | Routable | |
| 198.16/15 | | ALLOCATED | Routable | |
| 198.18/15 | | RESERVED | Not Routable | [ref] |
| 198.20/14 | | ALLOCATED | Routable | |
| 198.24/13 | | ALLOCATED | Routable | |
| 198.32/12 | | ALLOCATED | Routable | |
| 198.48/15 | | ALLOCATED | Routable | |
| 198.50/16 | | ALLOCATED | Routable | |
| 198.51.0/18 | | ALLOCATED | Routable | |
| 198.51.64/19 | | ALLOCATED | Routable | |
| 198.51.96/22 | | ALLOCATED | Routable | |
| 198.51.100.0/24 | | RESERVED | Not Routable | [ref] |
| 198.51.101/24 | | ALLOCATED | Routable | |
| 198.51.102/23 | | ALLOCATED | Routable | |
| 198.51.104/21 | | ALLOCATED | Routable | |
| 198.51.112/20 | | ALLOCATED | Routable | |
| 198.51.128/17 | | ALLOCATED | Routable | |
| 198.52/14 | | ALLOCATED | Routable | |
| 198.56/13 | | ALLOCATED | Routable | |
| 198.64/10 | | ALLOCATED | Routable | |
| 198.128/9 | | ALLOCATED | Routable | |
| ...
Manderson Expires February 18, 2012 [Page 12]
Internet-Draft Routing Intent in IANA Address Registries August 2011
Author's Address
Terry Manderson
ICANN
Email: terry.manderson@icann.org
Manderson Expires February 18, 2012 [Page 13]
