Network Working Group M. Cotton
Internet-Draft L. Vegoda
Updates: 4773,5736 (if approved) Internet Corporation for Assigned Names and Numbers
Obsoletes: 5156, 5735 (if approved) R. Bonica, Ed.
Intended status: Best Current Practice Juniper Networks
Expires: March 28, 2013 B. Haberman
Johns Hopkins University Applied Physics Lab
September 26, 2012

Special-Purpose Address Registries
draft-bonica-special-purpose-00

Abstract

This memo instructs IANA to restructure its IPv4 and IPv6 Special-Purpose Address Registries. Upon restructuring, the aforementioned registries will record all special-purpose address blocks, maintaining a common set of information regarding each address block.

This memo updates RFC 5736 and RFC 4773, which define the current structure of the IPv4 and IPv6 Special-Purpose Address Registries . It also obsoletes RFC 5735 and RFC 5156 which document special-purpose address blocks that are not currently, but will in the future, be recorded in the IPv4 and IPv6 Special-Purpose Address Registries.

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 March 28, 2013.

Copyright Notice

Copyright (c) 2012 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.


Table of Contents

1. Introduction

In order to support new protocols and practices, the IETF occasionally reserves an address block a for special purpose. For example, [RFC1122] reserves an IPv4 address block (0.0.0.0/8) to represent the local (i.e., "this") network. Likewise, [RFC4291] reserves an IPv6 address block (fe80::/10) to represent link-scoped unicast addresses.

Periodically, the IETF publishes an RFC that catalogs special-purpose address blocks. Currently, [RFC5735] catalogs all IPv4 special-purpose address blocks and [RFC5156] catalogs all IPv6 special-purpose address blocks.

[RFC5736] assigns an IPv4 address block (192.0.0.0/24) to IANA and instructs IANA to allocate special-purpose address blocks from this space. [RFC5736] also instructs IANA to create an IPv4 Special-Purpose Address Registry that records allocations from this address space. However, [RFC5736] does not instruct IANA to record special-purpose address block reservations from outside of the aforementioned space in the IPv4 Special-Purpose Address Registry.

Likewise, [RFC2928] assigns an IPv6 address block (2001:0000::/23) to IANA and instructs IANA to allocate special-purpose address blocks from this space. [RFC4773] instructs IANA to create an IPv6 Special-Purpose Address Registry that records allocations from this address space. However, [RFC4773] does not instruct IANA to record special-purpose address block reservations from outside of the aforementioned space in the IPv6 Special-Purpose Address Registry.

This memo instructs IANA to restructure its IPv4 and IPv6 Special-Purpose Address Registries. Therefore, this document updates [RFC5736] and [RFC4773] which define the current structure of the aforementioned registries.

Specifically, this memo instructs IANA to record all special-purpose address blocks in the aforementioned registries. These include, but are not limited to, IPv4 allocations from 192.0.0.0/24 and IPv6 allocations from 2001:0000::/23. When the aforementioned registries include all special-purpose address blocks, [RFC5735] and [RFC5156] will become redundant with the registries. Therefore, this memo obsoletes [RFC5735] and [RFC5156].

Furthermore, this memo defines:

2. IANA Considerations

IANA will restructure the following registries:

The IPv4 Special-Purpose Address Registry will record all IPv4 special-purpose address blocks. These reservations will include, but not be limited to, allocations from the 192.0.0.0/24 address block. Likewise, the IPv6 Special-Purpose Address Registry will record all IPv6 special-purpose address blocks. These reservations will include, but not be limited to, allocations from the 2001:0000::/23 address block.

Section 2.1 of this document describes information that both registries will maintain for each entry. Initially, IANA will populate the IPv4 Special-Purpose Address Registry with information taken from Section 2.2 of this document. Likewise, IANA will populate the IPv6 Special-Purpose Address Registry with information taken from Section 2.3 of this document.

IANA will update the aforementioned registries as requested in the "IANA Considerations" section of an IESG-reviewed document. The " IANA Considerations" section must include all of the information specified in Section 2.1 of this document.

2.1. Information Requirements

The IPv4 and IPv6 Special-Purpose Address Registries will maintain the following information regarding each entry:

If the value of "Destination" is FALSE, the values of "Routable" and "Global" must also be false.

2.2. IPv4 Special-Purpose Address Registry Entries

Table 1 though Table 17, below, represent entries with which the IANA will initially populate the IPv4 Special-Purpose Address Registry.

"This" Network
Attribute Value
Prefix 0.0.0.0/8
Name "This" Network
RFC [RFC1122] Section 3.2.1.3
Allocation Date September, 1981
Termination Date N/A
Source True
Destination True
Routable False
Global False
Private-Use Networks
Attribute Value
Prefix 10.0.0.0/8
Name Private-Use
RFC [RFC1918]
Allocation Date February 1996
Termination Date N/A
Source True
Destination True
Routable True
Global False
Shared Address Space
Attribute Value
Prefix 100.64.0.0/10
Name Shared Address Space
RFC [RFC6598]
Allocation Date April 2012
Termination Date N/A
Source True
Destination True
Routable True
Global False
Loopback
Attribute Value
Prefix 127.0.0.0/8
Name Loopback
RFC [RFC1122] Section 3.2.1.3
Allocation Date September 1981
Termination Date N/A
Source False
Destination False
Routable False
Global False
Link Local
Attribute Value
Prefix 169.254.0.0/16
Name Link Local
RFC [RFC3927]
Allocation Date May 2005
Termination Date N/A
Source True
Destination True
Routable False
Global False
Private-Use Networks
Attribute Value
Prefix 172.16.0.0/12
Name Private-Use
RFC [RFC1122]
Allocation Date February 1996
Termination Date N/A
Source True
Destination True
Routable True
Global False
IETF Protocol Assignments
Attribute Value
Prefix 192.0.0.0/24
Name IETF Protocol Assignments
RFC [RFC5736]
Allocation Date January 2010
Termination Date N/A
Source False[1]
Destination False[1]
Routable False[1]
Global False[1]

[1] Unless permitted by a more specific allocation.

DS-Lite
Attribute Value
Prefix 192.0.0.0/29
Name DS-Lite
RFC [RFC6333]
Allocation Date June 2011
Termination Date N/A
Source True
Destination True
Routable True
Global False
TEST-NET-1
Attribute Value
Prefix 192.0.2.0/24
Name TEST-NET-1
RFC [RFC5737]
Allocation Date January 2010
Termination Date N/A
Source False
Destination False
Routable False
Global False
6to4 Relay Anycast
Attribute Value
Prefix 192.88.99.0/24
Name 6to4 Relay Anycast
RFC [RFC3068]
Allocation Date June 2001
Termination Date N.A
Source True
Destination True
Routable True
Global True
Private-Use Networks
Attribute Value
Prefix 192.168.0.0/16
Name Private-Use
RFC [RFC1918]
Allocation Date February 196
Termination Date N/A
Source True
Destination True
Routable True
Global Flase
Network Interconnect Device Benchmark Testing
Attribute Value
Prefix 198.18.0.0/15
Name Benchmarking
RFC [RFC2544]
Allocation Date March 1999
Termination Date N.A
Source True
Destination True
Routable True
Global False
TEST-NET-2
Attribute Value
Prefix 198.51.100.0/24
Name TEST-NET-2
RFC [RFC5737]
Allocation Date January 2010
Termination Date N/A
Source False
Destination False
Routable False
Global False
TEST-NET-3
Attribute Value
Prefix 203.0.113.0/24
Name TEST-NET-3
RFC [RFC5737]
Allocation Date January 2010
Termination Date N/A
Source False
Destination False
Routable False
Global False
Multicast
Attribute Value
Prefix 224.0.0.0/4
Name Multicast
RFC [RFC5771]
Allocation Date March 2010
Termination Date N/A
Source False
Destination True
Routable True
Global N/A [2]

[2[ See [RFC5771] for details.

Reserved for Future Use
Attribute Value
Prefix 240.0.0.0/4
Name Reserved
RFC [RFC1112] Section 4
Allocation Date August 1989
Termination Date N/A
Source False
Destination False
Routable False
Global False
Limited Broadcast
Attribute Value
Prefix 255.255.255.255/32
Name Limited Broadcast
RFC [RFC0919] Section 7
Allocation Date October 1984
Termination Date N/A
Source False
Destination True
Routable False
Global False

2.3. IPv6 Special-Purpose Address Registry Entries

Table 18 through Table 30, below, represent entries with which the IANA will initially populate the IPv6 Special-Purpose Address Registry.

Loopback Address
Attribute Value
Prefix ::1/128
Name Loopback Address
RFC [RFC4291]
Allocation Date February 2006
Termination Date N/A
Source False
Destination False
Routable False
Global False
Unspecified Address
Attribute Value
Prefix ::/128
Name Unspecified Address
RFC [RFC4291]
Allocation Date February 2006
Termination Date N/A
Source True
Destination False
Routable False
Global False
IPv4-mapped Address
Attribute Value
Prefix ::FFFF:0:0/96
Name IPv4-mapped Address
RFC [RFC4291]
Allocation Date February 2006
Termination Date N/A
Source True
Destination True
Routable True
Global True
Discard-Only Prefix
Attribute Value
Prefix 0100::/64
Name Discard-Only Prefix
RFC [RFC6666]
Allocation Date June 2012
Termination Date N/A
Source True
Destination True
Routable True
Global False
IETF Protocol Assignments
Attribute Value
Prefix 2001:0000::/23
Name IETF Protocol Assignments
RFC [RFC2928]
Allocation Date September 2000
Termination Date N/A
Source False[3]
Destination False[3]
Routable False[3]
Global False[3]

[3] Unless allowed by a more specific allocation

TEREDO
Attribute Value
Prefix 2001:0000::/32
Name TEREDO
RFC [RFC4380]
Allocation Date January 2006
Termination Date N/A
Source True
Destination True
Routable True
Global False
Benchmarking
Attribute Value
Prefix 2001:0002::/48
Name Benchmarking
RFC [RFC5180]
Allocation Date April 2008
Termination Date N/A
Source True
Destination True
Routable True
Global False
Documentation
Attribute Value
Prefix 2001:db8::/32
Name Documentation
RFC [RFC3849]
Allocation Date July 2004
Termination Date N/A
Source False
Destination False
Routable False
Global False
ORCHID
Attribute Value
Prefix 2001:10::/28
Name ORCHID
RFC [RFC4843]
Allocation Date March 2007
Termination Date March 2014
Source False
Destination False
Routable False
Global False
6to4
Attribute Value
Prefix 2002::/16
Name 6to4
RFC [RFC3056]
Allocation Date February 2001
Termination Date N/A
Source False
Destination True
Routable True
Global N/A[4]

See [RFC3056] for details.

Unique-Local
Attribute Value
Prefix FC00::/7
Name Unique-Local
RFC [RFC4193]
Allocation Date October 2005
Termination Date N/A
Source True
Destination True
Routable True
Global False
Linked-Scoped Unicast
Attribute Value
Prefix FE80::/10
Name Linked-Scoped Unicast
RFC [RFC4291]
Allocation Date February 2006
Termination Date N/A
Source True
Destination True
Routable False
Global False
Multicast
Attribute Value
Prefix FF00::/8
Name Multicast
RFC [RFC4291]
Allocation Date February 2006
Termination Date N/A
Source False
Destination True
Routable True
Global

3. Security Considerations

Security of the Internet's routing system relies on the ability to authenticate an assertion of unique control of an address block. Measures to authenticate such assertions rely on validation that the address block forms part of an existing allocated address block, and that there is a trustable and unique reference in the IANA address registries.

The proposed registry is intended to provide an authoritative source of information regarding the currency and intended purpose of special purpose address blocks that are designated from the IANA-administered Special Purpose registry. This is a small step towards the creation of a comprehensive registry framework that can be used as a trust point for commencing a chain of address validation. Consideration should be given to IANA registry publication formats that are machine parseable, and also the use of file signatures and associated certificate mechanisms to allow applications to confirm that the registry contents are current, and that they have been published by the IANA.

4. Acknowledgements

The authors would like to acknowledge an anonymous donor, without whom this document would not have been written.

5. References

5.1. Normative References

[RFC5156] Blanchet, M., "Special-Use IPv6 Addresses", RFC 5156, April 2008.
[RFC5735] Cotton, M. and L. Vegoda, "Special Use IPv4 Addresses", BCP 153, RFC 5735, January 2010.
[RFC5736] Huston, G., Cotton, M. and L. Vegoda, "IANA IPv4 Special Purpose Address Registry", RFC 5736, January 2010.
[RFC4773] Huston, G., "Administration of the IANA Special Purpose IPv6 Address Block", RFC 4773, December 2006.

5.2. Informative References

[RFC1122] Braden, R., "Requirements for Internet Hosts - Communication Layers", STD 3, RFC 1122, October 1989.
[RFC2928] Hinden, R., Deering, S., Fink, R. and T. Hain, "Initial IPv6 Sub-TLA ID Assignments", RFC 2928, September 2000.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 4291, February 2006.
[RFC6666] Hilliard, N. and D. Freedman, "A Discard Prefix for IPv6", RFC 6666, August 2012.
[RFC4380] Huitema, C., "Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)", RFC 4380, February 2006.
[RFC5180] Popoviciu, C., Hamza, A., Van de Velde, G. and D. Dugatkin, "IPv6 Benchmarking Methodology for Network Interconnect Devices", RFC 5180, May 2008.
[RFC3849] Huston, G., Lord, A. and P. Smith, "IPv6 Address Prefix Reserved for Documentation", RFC 3849, July 2004.
[RFC4843] Nikander, P., Laganier, J. and F. Dupont, "An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers (ORCHID)", RFC 4843, April 2007.
[RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6 Domains via IPv4 Clouds", RFC 3056, February 2001.
[RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast Addresses", RFC 4193, October 2005.
[RFC6598] Weil, J., Kuarsingh, V., Donley, C., Liljenstolpe, C. and M. Azinger, "IANA-Reserved IPv4 Prefix for Shared Address Space", BCP 153, RFC 6598, April 2012.
[RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G. and E. Lear, "Address Allocation for Private Internets", BCP 5, RFC 1918, February 1996.
[RFC3927] Cheshire, S., Aboba, B. and E. Guttman, "Dynamic Configuration of IPv4 Link-Local Addresses", RFC 3927, May 2005.
[RFC5737] Arkko, J., Cotton, M. and L. Vegoda, "IPv4 Address Blocks Reserved for Documentation", RFC 5737, January 2010.
[RFC6333] Durand, A., Droms, R., Woodyatt, J. and Y. Lee, "Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion", RFC 6333, August 2011.
[RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for Network Interconnect Devices", RFC 2544, March 1999.
[RFC5771] Cotton, M., Vegoda, L. and D. Meyer, "IANA Guidelines for IPv4 Multicast Address Assignments", BCP 51, RFC 5771, March 2010.
[RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5, RFC 1112, August 1989.
[RFC0919] Mogul, J., "Broadcasting Internet Datagrams", STD 5, RFC 919, October 1984.
[RFC3068] Huitema, C., "An Anycast Prefix for 6to4 Relay Routers", RFC 3068, June 2001.

Authors' Addresses

Michelle Cotton Internet Corporation for Assigned Names and Numbers 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 USA Phone: +310-823-9358 EMail: michelle.cotton@icann.org URI: http://www.icann.org/
Leo Vegoda Internet Corporation for Assigned Names and Numbers 12025 Waterfront Drive, Suite 300 LosAngeles, CA 90094-2536 USA Phone: +310-823-9358 EMail: leo.vegoda@icann.org URI: http://www.icann.org/
Ronald P Bonica (editor) Juniper Networks 2251 Corporate Park Drive Herndon, Virginia 20171 USA EMail: rbonica@juniper.net
Brian Haberman Johns Hopkins University Applied Physics Lab 11100 Johns Hopkins Road Laurel, Maryland 20723-6099 USA EMail: brian@innovationslab.net