< draft-vegoda-cotton-rfc5735bis-02.txt   draft-vegoda-cotton-rfc5735bis-03.txt >
Network Working Group M. Cotton Network Working Group M. Cotton
Internet-Draft L. Vegoda Internet-Draft L. Vegoda
Obsoletes: 5735 (if approved) ICANN Obsoletes: 5735 (if approved) ICANN
Updates: 6441 (if approved) May 22, 2012 Intended status: BCP August 14, 2012
Intended status: BCP Expires: February 15, 2013
Expires: November 23, 2012
Special Use IPv4 Addresses Special Use IPv4 Addresses
draft-vegoda-cotton-rfc5735bis-02 draft-vegoda-cotton-rfc5735bis-03
Abstract Abstract
This document obsoletes RFC 5735 and updates RFC 6441. It describes This document describes the global and other specialized IPv4 address
the global and other specialized IPv4 address blocks that have been blocks that have been assigned by the Internet Assigned Numbers
assigned by the Internet Assigned Numbers Authority (IANA). It does Authority (IANA). It does not address IPv4 address space assigned to
not address IPv4 address space assigned to operators and users operators and users through the Regional Internet Registries, nor
through the Regional Internet Registries, nor does it address IPv4 does it address IPv4 address space assigned directly by IANA prior to
address space assigned directly by IANA prior to the creation of the the creation of the Regional Internet Registries. It also does not
Regional Internet Registries. It also does not address allocations address allocations or assignments of IPv6 addresses or autonomous
or assignments of IPv6 addresses or autonomous system numbers. system numbers. This document obsoletes RFC 5735 and updates RFC
6441.
The substantive change between this document and RFC 5735 is that it
includes 100.64.0.0/10, which was assigned in RFC 6598.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 November 23, 2012. This Internet-Draft will expire on February 15, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Global and Other Specialized Address Blocks . . . . . . . . . . 3
3. Global and Other Specialized Address Blocks . . . . . . . . . . 3 3. Summary Table . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Summary Table . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
5. Assignments of IPv4 Blocks for New Specialized Uses . . . . . . 6 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7
7. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 7. Informative References . . . . . . . . . . . . . . . . . . . . 7
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
9.1. Normative References . . . . . . . . . . . . . . . . . . . 7
9.2. Informative References . . . . . . . . . . . . . . . . . . 8
Appendix A. Changes from RFC 5735 . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
Throughout its history, the Internet has employed a central Internet Throughout its history, the Internet has employed a central Internet
Assigned Numbers Authority (IANA) responsible for the allocation and Assigned Numbers Authority (IANA) responsible for the allocation and
assignment of various identifiers needed for the operation of the assignment of various identifiers needed for the operation of the
Internet [RFC1174]. In the case of the IPv4 address space, the IANA Internet [RFC1174]. In the case of the IPv4 address space, the IANA
allocates parts of the address space to Regional Internet Registries allocates parts of the address space to Regional Internet Registries
(RIRs) according to their established needs. These RIRs are (RIRs) according to their established needs. These RIRs are
responsible for the registration of IPv4 addresses to operators and responsible for the registration of IPv4 addresses to operators and
users of the Internet within their regions. users of the Internet within their regions.
On an ongoing basis, the IANA has been designated by the IETF to make On an ongoing basis, IANA assignmnets have been made using policies
assignments in support of the Internet Standards Process [RFC2860]. established by the IETF to support the Internet Standards Process
Section 4 of this document describes that assignment process. described in Section 4 of [RFC2860].
Small portions of the IPv4 address space have been allocated or Small portions of the IPv4 address space have been allocated or
assigned directly by the IANA for global or other specialized assigned directly by the IANA for global or other specialized
purposes. These allocations and assignments have been documented in purposes. These allocations and assignments have been documented in
a variety of RFCs and other documents. This document is intended to a variety of RFCs and other documents. This document is intended to
collect these scattered references and provide a current list of collect these scattered references and provide a current list of
special use IPv4 addresses. special use IPv4 addresses.
This document is a revision of RFC 5735 [RFC5735], which it This document is a revision of RFC 5735 [RFC5735], which it
obsoletes; its primary purpose is to reflect the changes to the list obsoletes; its primary purpose is to reflect the changes to the list
of special IPv4 assignments since the publication of RFC 5735. It is of special IPv4 assignments since the publication of RFC 5735. It is
a companion to [RFC5156] which describes special IPv6 addresses. a companion to [RFC5156] which describes special IPv6 addresses.
2. Terminology 2. Global and Other Specialized Address Blocks
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 BCP 14, [RFC2119].
3. Global and Other Specialized Address Blocks
0.0.0.0/8 - Addresses in this block refer to source hosts on "this" 0.0.0.0/8 - Addresses in this block refer to source hosts on "this"
network. Address 0.0.0.0/32 may be used as a source address for this network. Address 0.0.0.0/32 may be used as a source address for this
host on this network; other addresses within 0.0.0.0/8 may be used to host on this network; other addresses within 0.0.0.0/8 may be used to
refer to specified hosts on this network [RFC1122], section 3.2.1.3. refer to specified hosts on this network [RFC1122], section 3.2.1.3.
10.0.0.0/8 - This block is set aside for use in private networks. 10.0.0.0/8 - This block is set aside for use in private networks.
Its intended use is documented in [RFC1918]. As described in that Its intended use is documented in [RFC1918]. As described in that
RFC, addresses within this block do not legitimately appear on the RFC, addresses within this block do not legitimately appear on the
public Internet. These addresses can be used without any public Internet. These addresses can be used without any
skipping to change at page 4, line 15 skipping to change at page 4, line 8
127.0.0.0/8 - This block is assigned for use as the Internet host 127.0.0.0/8 - This block is assigned for use as the Internet host
loopback address. A datagram sent by a higher level protocol to an loopback address. A datagram sent by a higher level protocol to an
address anywhere within this block loops back inside the host. This address anywhere within this block loops back inside the host. This
is ordinarily implemented using only 127.0.0.1/32 for loopback. As is ordinarily implemented using only 127.0.0.1/32 for loopback. As
described in [RFC1122], Section 3.2.1.3, addresses within the entire described in [RFC1122], Section 3.2.1.3, addresses within the entire
127.0.0.0/8 block do not legitimately appear on any network anywhere. 127.0.0.0/8 block do not legitimately appear on any network anywhere.
100.64.0.0/10 - This block is used as Shared Address Space. 100.64.0.0/10 - This block is used as Shared Address Space.
[RFC6598] states that Shared Address Space can only be used in [RFC6598] states that Shared Address Space can only be used in
Service Provider networks or on routing equipment that is able to do Service Provider networks or on routing equipment that is able to do
address translation across router the interfaces when addresses are address translation across router interfaces when addresses are
identical on two different interfaces. identical on two different interfaces.
169.254.0.0/16 - This is the "link local" block. As described in 169.254.0.0/16 - This is the "link local" block. As described in
[RFC3927], it is allocated for communication between hosts on a [RFC3927], it is allocated for communication between hosts on a
single link. Hosts obtain these addresses by auto-configuration, single link. Hosts obtain these addresses by auto-configuration,
such as when a DHCP server cannot be found. such as when a DHCP server cannot be found.
172.16.0.0/12 - This block is set aside for use in private networks. 172.16.0.0/12 - This block is set aside for use in private networks.
Its intended use is documented in [RFC1918]. As described in that Its intended use is documented in [RFC1918]. As described in that
RFC, addresses within this block do not legitimately appear the RFC, addresses within this block do not legitimately appear the
skipping to change at page 6, line 5 skipping to change at page 6, line 5
The IANA guidelines for assignments from this space are described in The IANA guidelines for assignments from this space are described in
[RFC5771]. [RFC5771].
240.0.0.0/4 - This block, formerly known as the Class E address 240.0.0.0/4 - This block, formerly known as the Class E address
space, is reserved for future use, see [RFC1112], section 4. space, is reserved for future use, see [RFC1112], section 4.
The one exception to this is the "limited broadcast" destination The one exception to this is the "limited broadcast" destination
address 255.255.255.255. As described in [RFC0919] and [RFC0922], address 255.255.255.255. As described in [RFC0919] and [RFC0922],
packets with this destination address are not forwarded at IP layer. packets with this destination address are not forwarded at IP layer.
4. Summary Table 3. Summary Table
Address Block Present Use Reference
0.0.0.0/8 "This" Network RFC 1122, section 3.2.1.3
10.0.0.0/8 Private-Use Networks RFC 1918
100.64.0.0/10 Shared Address Space RFC 6598
127.0.0.0/8 Loopback RFC 1122, section 3.2.1.3
169.254.0.0/16 Link Local RFC 3927
172.16.0.0/12 Private-Use Networks RFC 1918
192.0.0.0/24 IETF Protocol Assignments
192.0.2.0/24 TEST-NET-1 RFC 5737
192.88.99.0/24 6to4 Relay Anycast RFC 3068
192.168.0.0/16 Private-Use Networks RFC 1918
198.18.0.0/15 Network Interconnect
Device Benchmark Testing RFC 2544
198.51.100.0/24 TEST-NET-2 RFC 5737
203.0.113.0/24 TEST-NET-3 RFC 5737
224.0.0.0/4 Multicast RFC 5771
240.0.0.0/4 Reserved for Future Use RFC 1112, section 4
255.255.255.255/32 Limited Broadcast RFC 919, section 7
5. Assignments of IPv4 Blocks for New Specialized Uses
The IANA has responsibility for making assignments of protocol
parameters used in the Internet according to the requirements of the
"Memorandum of Understanding Concerning the Technical Work of the
Internet Assigned Numbers Authority" [RFC2860]. Among other things,
[RFC2860] requires that protocol parameters be assigned according to
the criteria and procedures specified in RFCs, including Proposed,
Draft, and full Internet Standards and Best Current Practice
documents, and any other RFC that calls for IANA assignment.
The domain name and IP address spaces involve policy issues (in
addition to technical issues) so that the requirements of [RFC2860]
do not apply generally to those spaces. Nonetheless, the IANA is
responsible for ensuring assignments of IPv4 addresses as needed in
support of the Internet Standards Process. When a portion of the
IPv4 address space is specifically required by an RFC, the technical
requirements (e.g., size, prefix length) for the portion should be
described [RFC5226]. Immediately before the RFC is published, the
IANA will, in consultation with the Regional Internet Registries,
make the necessary assignment and notify the RFC Editor of the
particulars for inclusion in the RFC as published.
As required by [RFC2860], the IANA will also make necessary Address Block Present Use Reference
experimental assignments of IPv4 addresses, also in consultation with ------------------------------------------------------------------
the Regional Internet Registries. 0.0.0.0/8 "This" Network RFC 1122, sect 3.2.1.3
10.0.0.0/8 Private-Use Networks RFC 1918
100.64.0.0/10 Shared Address Space RFC 6598
127.0.0.0/8 Loopback RFC 1122, sect 3.2.1.3
169.254.0.0/16 Link Local RFC 3927
172.16.0.0/12 Private-Use Networks RFC 1918
192.0.0.0/24 IETF Protocol Assignments RFC 5736
192.0.2.0/24 TEST-NET-1 RFC 5737
192.88.99.0/24 6to4 Relay Anycast RFC 3068
192.168.0.0/16 Private-Use Networks RFC 1918
198.18.0.0/15 Network Interconnect
Device Benchmark Testing RFC 2544
198.51.100.0/24 TEST-NET-2 RFC 5737
203.0.113.0/24 TEST-NET-3 RFC 5737
224.0.0.0/4 Multicast RFC 5771
240.0.0.0/4 Reserved for Future Use RFC 1112, sect 4
255.255.255.255/32 Limited Broadcast RFC 919, sect 7
6. IANA Considerations 4. IANA Considerations
This document describes the IANA's past and current practices and This document describes the past and current practices, but does not
does not create any new requirements for assignments or allocations create any new requirements for assignments or allocations by the
by the IANA. IANA.
7. Security Considerations 5. Security Considerations
The particular assigned values of special use IPv4 addresses The particular assigned values of special use IPv4 addresses
cataloged in this document do not directly raise security issues. cataloged in this document do not directly raise security issues.
However, the Internet does not inherently protect against abuse of However, the Internet does not inherently protect against abuse of
these addresses; if you expect (for instance) that all packets from a these addresses; if you expect (for instance) that all packets from a
private address space such as the 10.0.0.0/8 block or the link local private address space such as the 10.0.0.0/8 block or the link local
block 169.254.0.0/16 originate within your subnet, all routers at the block 169.254.0.0/16 originate within your subnet, all routers at the
border of your network should filter such packets that originate from border of your network should filter such packets that originate from
outside your network. Attacks have been mounted that depend on the outside your network. Attacks have been mounted that depend on the
unexpected use of some of these addresses. unexpected use of some of these addresses.
It should also be noted that some of these address blocks may be used It should also be noted that some of these address blocks may be used
legitimately outside of a single administrative domain, and may legitimately outside of a single administrative domain, and may
appear on the global Internet. Security policy SHOULD NOT blindly appear on the global Internet. Security policy should not blindly
filter all of these address spaces without due consideration, and filter all of these address spaces without due consideration, and
network operators are encouraged to review this document, and network operators are encouraged to review this document, and
references contained therein, and determine what security policies references contained therein, and determine what security policies
should be associated with each of these address blocks within their should be associated with each of these address blocks within their
specific operating environments. specific operating environments.
8. Acknowledgments 6. Acknowledgments
Your name here?
9. References
9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Many people have made comments on draft versions of this document.
Requirement Levels", BCP 14, RFC 2119, March 1997. The authors would especially like to thank Scott Bradner, Randy Bush,
Harald Alvestrand, Peter Koch, Alfred Hoenes, and Jari Arkko for
their constructive feedback and comments. They would also like to
offer a special note of thanks to APNIC, which nominated
198.51.100.0/24 and 203.0.113.0/24.
9.2. Informative References 7. Informative References
[RFC0919] Mogul, J., "Broadcasting Internet Datagrams", STD 5, [RFC0919] Mogul, J., "Broadcasting Internet Datagrams", STD 5,
RFC 919, October 1984. RFC 919, October 1984.
[RFC0922] Mogul, J., "Broadcasting Internet datagrams in the [RFC0922] Mogul, J., "Broadcasting Internet datagrams in the
presence of subnets", STD 5, RFC 922, October 1984. presence of subnets", STD 5, RFC 922, October 1984.
[RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5, [RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5,
RFC 1112, August 1989. RFC 1112, August 1989.
skipping to change at page 8, line 47 skipping to change at page 8, line 15
[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.
[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, Configuration of IPv4 Link-Local Addresses", RFC 3927,
May 2005. May 2005.
[RFC5156] Blanchet, M., "Special-Use IPv6 Addresses", RFC 5156, [RFC5156] Blanchet, M., "Special-Use IPv6 Addresses", RFC 5156,
April 2008. April 2008.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
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 [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.
[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.
[RFC6441] Vegoda, L., "Time to Remove Filters for Previously
Unallocated IPv4 /8s", BCP 171, RFC 6441, November 2011.
[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.
Appendix A. Changes from RFC 5735
This document includes 100.64.0.0/10, which was assigned in
[RFC6598]. It is the only substantive change between this document
and [RFC5735].
Authors' Addresses Authors' Addresses
Michelle Cotton Michelle Cotton
Internet Corporation for Assigned Names and Numbers Internet Corporation for Assigned Names and Numbers
4676 Admiralty Way, Suite 330 12025 Waterfront Drive, Suite 300
Marina del Rey 90292 Los Angeles, CA 90094-2536
United States of America United States of America
Phone: +310-823-9358 Phone: +310-823-9358
Email: michelle.cotton@icann.org Email: michelle.cotton@icann.org
URI: http://www.icann.org/ URI: http://www.icann.org/
Leo Vegoda Leo Vegoda
Internet Corporation for Assigned Names and Numbers Internet Corporation for Assigned Names and Numbers
4676 Admiralty Way, Suite 330 12025 Waterfront Drive, Suite 300
Marina del Rey 90292 Los Angeles, CA 90094-2536
United States of America United States of America
Phone: +310-823-9358 Phone: +310-823-9358
Email: leo.vegoda@icann.org Email: leo.vegoda@icann.org
URI: http://www.icann.org/ URI: http://www.icann.org/
 End of changes. 23 change blocks. 
116 lines changed or deleted 66 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/