[Docs] [txt|pdf|xml|html] [Tracker] [Email] [Diff1] [Diff2] [Nits]

Versions: (RFC 3330) 00 01 02 03 04 05 06 07 08 09 10 11 RFC 5735

Network Working Group                                          M. Cotton
Internet-Draft                                                     ICANN
Obsoletes: 3330 (if approved)                           January 21, 2009
Intended status: Informational
Expires: July 25, 2009


                       Special Use IPv4 Addresses
                        draft-iana-rfc3330bis-05

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on July 25, 2009.

Copyright Notice

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

Abstract

   This document obsoletes RFC 3330.  It describes the global and other



Cotton                    Expires July 25, 2009                 [Page 1]


Internet-Draft         Special Use IPv4 Addresses           January 2009


   specialized IPv4 address blocks that have been assigned by the
   Internet Assigned Numbers Authority (IANA).  It does not address IPv4
   address space assigned to operators and users through the Regional
   Internet Registries.  It also does not address allocations or
   assignments of IPv6 addresses or autonomous system numbers.  Special
   IPv6 addresses are described in RFC 5156.


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   3.  Differences between this document and RFC 3330  . . . . . . . . 3
   4.  Global and Other Specialized Address Blocks . . . . . . . . . . 4
   5.  Summary Table . . . . . . . . . . . . . . . . . . . . . . . . . 6
   6.  Assignments of IPv4 Blocks for New Specialized Uses . . . . . . 6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
   8.  Security Considerations . . . . . . . . . . . . . . . . . . . . 7
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . . . 7
     10.1.  Normative References . . . . . . . . . . . . . . . . . . . 7
     10.2.  Informative References . . . . . . . . . . . . . . . . . . 7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 8




























Cotton                    Expires July 25, 2009                 [Page 2]


Internet-Draft         Special Use IPv4 Addresses           January 2009


1.  Introduction

   Throughout its history, the Internet has employed a central Internet
   Assigned Numbers Authority (IANA) responsible for the allocation and
   assignment of various identifiers needed for the operation of the
   Internet [RFC1174].  In the case of the IPv4 address space, the IANA
   allocates parts of the address space to Regional Internet Registries
   (RIRs) according to their established needs.  These Regional Internet
   Registries are responsible for the registration of IPv4 addresses to
   operators and users of the Internet within their regions.

   On an ongoing basis, the IANA has been designated by the IETF to make
   assignments in support of the Internet Standards Process [RFC2860].
   Section 5 of this document describes that assignment process.

   Small portions of the IPv4 address space have been allocated or
   assigned directly by the IANA for global or other specialized
   purposes.  These allocations and assignments have been documented in
   a variety of RFCs and other documents.  This document is intended to
   collect these scattered references and provide a current list of
   special use IPv4 addresses.

   This document is a revision of RFC 3330 [RFC3330], which it
   obsoletes; its primary purpose is to re-publish the technical content
   of RFC 3330 mostly unchanged as a Best Current Practice RFC.

   The terms "Specification Required", "Expert Review", "IESG Approval",
   "IETF Consensus", and "Standards Action", are used in this memo to
   refer to the processes described in [RFC5226].  The keywords MUST,
   MUST NOT, MAY, OPTIONAL, REQUIRED, RECOMMENDED, SHALL, SHALL NOT,
   SHOULD, SHOULD NOT are to be interpreted as defined in [RFC2119].


2.  Terminology

   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.  Differences between this document and RFC 3330

   Address blocks that were reserved for a special purpose in RFC 3330
   but are no longer reserved for any special purpose and are available
   for allocation are no longer listed in Sections 4 or 5.  The
   following blocks have become available:

   - 14.0.0.0/8 is no longer set aside for assignments to the



Cotton                    Expires July 25, 2009                 [Page 3]


Internet-Draft         Special Use IPv4 Addresses           January 2009


   international system of Public Data Networks [RFC1700], page 181].
   It is now available for allocation to RIRs in the normal way;

   - 24.0.0.0/8 is no longer listed as the addresses in that block have
   been managed by the American Registry for Internet Numbers (ARIN) in
   the normal way since 2001.

   - 39.0.0.0/8 is no longer listed as it has been subject to allocation
   to an RIR for assignment in the normal manner since 2001;

   - 128.0.0.0/16 is not reserved and is subject to future allocation by
   a Regional Internet Registry for assignment in the normal manner;

   - 191.255.0.0/16 is not reserved and is subject to future allocation
   by a RIR for assignment in the normal manner;

   - 223.255.255.0/24 is not reserved and is subject to future
   allocation by an RIR for assignment in the normal manner.


4.  Global and Other Specialized Address Blocks

   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
   host on this network; other addresses within 0.0.0.0/8 may be used to
   refer to specified hosts on this network [RFC1122], page 30.

   10.0.0.0/8 - This block is set aside for use in private networks.
   Its intended use is documented in [RFC1918].  Addresses within this
   block should not appear on the public Internet and can be used
   without any coordination with IANA or an Internet registry.

   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
   address anywhere within this block should loop back inside the host.
   This is ordinarily implemented using only 127.0.0.1/32 for loopback,
   but no addresses within this block should ever appear on any network
   anywhere [RFC1122], page 31.

   169.254.0.0/16 - This is the "link local" block.  As described in
   [RFC3927], it is allocated for communication between hosts on a
   single link.  Hosts obtain these addresses by auto-configuration,
   such as when a DHCP server cannot be found.

   172.16.0.0/12 - This block is set aside for use in private networks.
   Its intended use is documented in [RFC1918].  Addresses within this
   block should not appear on the public Internet and can be used
   without any coordination with IANA or an Internet registry.



Cotton                    Expires July 25, 2009                 [Page 4]


Internet-Draft         Special Use IPv4 Addresses           January 2009


   192.0.0.0/24 - This block is reserved for IETF protocol assignments.

   192.0.2.0/24 - This block is assigned as "TEST-NET" for use in
   documentation and example code.  It is often used in conjunction with
   domain names example.com or example.net in vendor and protocol
   documentation.  Addresses within this block SHOULD NOT appear on the
   public Internet and can be used without any coordination with IANA or
   an Internet registry.

   192.88.99.0/24 - This block is allocated for use as 6to4 relay
   anycast addresses, according to [RFC3068].

   192.168.0.0/16 - This block is set aside for use in private networks.
   Its intended use is documented in [RFC1918].  Addresses within this
   block should not appear on the public Internet and can be used
   without any coordination with IANA or an Internet registry.

   198.18.0.0/15 - This block has been allocated for use in benchmark
   tests of network interconnect devices.  [RFC2544] explains that this
   range was assigned to minimize the chance of conflict in case a
   testing device were to be accidentally connected to part of the
   Internet.  Packets with source addresses from this range are not
   meant to be forwarded across the Internet.

   224.0.0.0/4 - This block, formerly known as the Class D address
   space, is allocated for use in IPv4 multicast address assignments.
   The IANA guidelines for assignments from this space are described in
   [RFC3171].

   240.0.0.0/4 - This block, formerly known as the Class E address
   space, is reserved.  The "limited broadcast" destination address
   255.255.255.255 should never be forwarded outside the local network
   of the source.  The remainder of this space is reserved for future
   use.  [RFC1112], page 2.

















Cotton                    Expires July 25, 2009                 [Page 5]


Internet-Draft         Special Use IPv4 Addresses           January 2009


5.  Summary Table


   Address Block       Present Use                Reference
   ------------------------------------------------------------------
   0.0.0.0/8           "This" Network             RFC 1122, page 30
   10.0.0.0/8          Private-Use Networks       RFC 1918
   127.0.0.0/8         Loopback                   RFC 1122, page 31
   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
   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
   224.0.0.0/4         Multicast                  RFC 3171
   240.0.0.0/4         Reserved for Future Use    RFC 1112, page 2




6.  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
   experimental assignments of IPv4 addresses, also in consultation with
   the Regional Internet Registries.



Cotton                    Expires July 25, 2009                 [Page 6]


Internet-Draft         Special Use IPv4 Addresses           January 2009


7.  IANA Considerations

   This document describes the IANA's past and current practices and
   does not create any new requirements for assignments or allocations
   by the IANA.


8.  Security Considerations

   The particular assigned values of special-use IPv4 addresses
   cataloged in this document do not directly raise security issues.
   However, the Internet does not inherently protect against abuse of
   these addresses; if you expect (for instance) that all packets from
   the 10.0.0.0/8 block originate within your subnet, all border routers
   should filter such packets that originate from elsewhere.  Attacks
   have been mounted that depend on the unexpected use of some of these
   addresses.


9.  Acknowledgments

   Many people have made comments on draft versions of this document.
   The IANA would especially like to thank Scott Bradner, Randy Bush,
   Leo Vegoda, Harald Alvestrand and the IESG for their constructive
   feedback and comments.


10.  References

10.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

10.2.  Informative References

   [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.

   [RFC1174]  Cerf, V., "IAB recommended policy on distributing internet
              identifier assignment and IAB recommended policy change to
              internet "connected" status", RFC 1174, August 1990.

   [RFC1700]  Reynolds, J. and J. Postel, "Assigned Numbers", RFC 1700,
              October 1994.



Cotton                    Expires July 25, 2009                 [Page 7]


Internet-Draft         Special Use IPv4 Addresses           January 2009


   [RFC1918]  Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and
              E. Lear, "Address Allocation for Private Internets",
              BCP 5, RFC 1918, February 1996.

   [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
              Understanding Concerning the Technical Work of the
              Internet Assigned Numbers Authority", RFC 2860, June 2000.

   [RFC3068]  Huitema, C., "An Anycast Prefix for 6to4 Relay Routers",
              RFC 3068, June 2001.

   [RFC3171]  Albanna, Z., Almeroth, K., Meyer, D., and M. Schipper,
              "IANA Guidelines for IPv4 Multicast Address Assignments",
              BCP 51, RFC 3171, August 2001.

   [RFC3330]  IANA, "Special-Use IPv4 Addresses", RFC 3330,
              September 2002.

   [RFC3927]  Cheshire, S., Aboba, B., and E. Guttman, "Dynamic
              Configuration of IPv4 Link-Local Addresses", RFC 3927,
              May 2005.

   [RFC5156]  Blanchet, M., "Special-Use IPv6 Addresses", RFC 5156,
              April 2008.

   [RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", BCP 26, RFC 5226,
              May 2008.


Author's Address

   Michelle Cotton
   Internet Corporation for Assigned Names and Numbers
   4676 Admiralty Way, Suite 330
   Marina del Rey  90292
   United States

   Phone: +310-823-9358
   Email: michelle.cotton@icann.org
   URI:   http://www.iana.org/







Cotton                    Expires July 25, 2009                 [Page 8]


Html markup produced by rfcmarkup 1.129b, available from https://tools.ietf.org/tools/rfcmarkup/