RFC 1814 INFORMATIONAL ADDRESSING · POLICY · GUIDANCE

Unique Addresses are Good

Why enterprises should apply for globally unique IP addresses.

On rfc-editor.org ↗
PUBLISHED
June 1995
AUTHORS
E. Gerich
STREAM
Legacy
RFC FOR PRIVATE ADDRESSES
RFC 1597
RFC FOR ALLOCATION CRITERIA
RFC 1466
DOI
10.17487/RFC1814

RFC text

Contents
Original text · RFC Editor View on rfc-editor.org ↗
Network Working Group                                          E. Gerich
Request for Comments: 1814                            Merit Network Inc.
Category: Informational                                        June 1995


                       Unique Addresses are Good

Status of this Memo

   This memo provides information for the Internet community.  This memo
   does not specify an Internet standard of any kind.  Distribution of
   this memo is unlimited.

Abstract

   The IAB suggests that while RFC 1597 establishes reserved IP address
   space for the use of private networks which are isolated and will
   remain isolated from the Internet, any enterprise which anticipates
   external connectivity to the Internet should apply for a globally
   unique address from an Internet registry or service provider.

Introduction

   With the advent of RFC 1466 and RFC 1597 the criteria for the
   allocation of unique IP numbers and the reservation of unique IP
   numbers have been defined. The IAB and the IANA wish to offer
   guidance to the Internet registries as to the application of these
   two documents.  The author submits this document as an informational
   RFC on behalf of the Internet Architecture Board and the IANA.

Guidance to Internet Registries

   RFC 1466 lists the criteria to which Internet registries should
   conform.  One of the criteria is that the Internet registry is
   committed to allocate IP numbers according to the guidelines
   established by the IANA and the IR. Those guidelines (for Classes A,
   B, and C addresses) are documented in RFC 1466.

   Internet Registries have agreed to comply with the guidelines
   established by RFC 1466 and therefore, if an organization meets the
   size requirement for the requested address(es) and submits an
   engineering plan, the organization has fulfilled the necessary
   requirements.  The Internet Registry will make the allocation based
   on the established criteria.

   The preconditions defined in RFC 1466 are limited to number of hosts
   and subnets as well as an engineering plan.  The existence of private
   address space (RFC 1597) shall not prevent an enterprise from
   obtaining public address space according to the allocation criteria
   (currently, RFC 1466).

   An enterprise may be required by a Internet registry to submit an
   engineering plan documenting a realistic deployment schedule and
   reasonable attention to conservation of address space to support the
   size of the enterprise's request for globally unique IP addresses.

   It is perfectly appropriate for an Internet registry to inform an
   organization of the provisions of RFC 1597.  Any organization
   considering the use of private network numbers should carefully
   consider the potential advantages and possible problems as discussed
   in RFCs 1597 and 1627.

   RFC 1597 establishes reserved IP address space for the use of private
   networks which are isolated and will remain isolated from the
   Internet. Thus RFC 1597 documents a way that private enterprises may
   assure that their networks will remain segregated from the Internet.
   The addresses designated in RFC 1597 should not be routed by the
   Internet.

   Any enterprise with a significantly large number of hosts which might
   require external connectivity to the Internet at the IP layer should
   apply for a block of globally unique addresses from an Internet
   registry.  Enterprises with a small to medium number of hosts that
   require external connectivity to the Internet at the IP layer should
   expect to use globally unique addresses for these hosts, assigned to
   them by their current Internet service provider from its own assigned
   addresses, if it has such addresses to distribute.

   If an enterprise with a small to medium number of hosts desires
   unique IP addresses, and is unable to obtain them under reasonable
   conditions from a service provider, or has no service provider, the
   Internet registries are recommended to assign such addresses without
   conditions with respect to service provider selection.  The
   registries should make clear to the enterprise that when the
   enterprise decides to connect to the Internet, the assigned addresses
   are no guarantee of Internet-wide IP connectivity. In fact, some
   service providers may require renumbering as a condition of
   connectivity.

   Any organization which anticipates having external connectivity is
   encouraged to apply for a globally unique IP address.  Globally
   unique addresses are necessary to differentiate between destinations
   on the Internet.  One must understand, however, that the globally
   unique address by itself does not necessarily guarantee global
   connectivity.  Individual network service providers may place
   restrictions on what addresses they will or will not route based on
   operational limitations.

References

   [1] Gerich, E., "Guidelines for Management of IP Address Space", RFC
       1466, Merit Network Inc., May 1993.

   [2] Rekhter, Y., Moskowitz, B., Karrenberg, D., and G. de Groot,
       "Address Allocation for Private Internets", RFC 1597, T.J. Watson
       Research Center, IBM Corp., Chrysler Corp., RIPE NCC, RIPE NCC,
       March 1994.

Security Considerations

   Security issues are not discussed in this memo.

Author's Address

   Elise Gerich
   Merit Network Inc.
   4251 Plymouth Road
   Ann Arbor, MI 48105

   Phone: +1 313 764 9430
   Fax: +1 313 747 3745
   EMail: epg@merit.edu

AI ELI5

On this page
PROBLEMRFC 1597 reserved address space for private networks that would never connect to the Internet. Some enterprises thought they could use private addresses and avoid the registration process, but this creates problems when (or if) they later need external connectivity.
MECHANISMThe Internet Architecture Board (IAB) and IANA issue guidance to Internet registries: even though private addresses exist, any enterprise that anticipates external connectivity should apply for globally unique addresses if they meet the allocation criteria.
POLICY GUIDANCEThe IAB clarifies that globally unique addresses are necessary for Internet connectivity, and enterprises should plan accordingly. Registries are encouraged to allocate unique addresses without unreasonable conditions to enterprises that expect future connectivity.

§1The Problem

RFC 1597 established reserved IP address space for private networks that are isolated and will never connect to the Internet. These private addresses can be reused within many different organizations without conflict, since they never appear in Internet routing.

However, some enterprises saw this as a way to avoid registering for global addresses. Elise Gerich, on behalf of the IAB and IANA, clarifies the guidance: any enterprise that anticipates external connectivity should apply for globally unique addresses instead.

RFC 1597 said: use secret addresses if you are never connecting. But some companies used them anyway, thinking they could switch later. This RFC says: get real addresses from the start if you might connect.

§2Guidance to Registries

The IAB advises Internet registries to allocate globally unique addresses according to the established criteria in RFC 1466, without letting the existence of private address space discourage it. Registries should verify that an organization meets the size requirements and submits a reasonable engineering plan, then make the allocation.

Organizations should be informed of the provisions in RFC 1597 so they understand the trade-off. Large enterprises requiring external connectivity should apply for large blocks of unique addresses. Smaller enterprises with a few hosts needing external connectivity can receive addresses from their Internet service provider or, if necessary, directly from the registry.

The key point: globally unique addresses are necessary to differentiate between destinations on the Internet. A unique address by itself does not guarantee global connectivity—service providers may place restrictions on what they route—but it is a prerequisite.

Registries should give out real addresses generously to any company that might want to connect. You cannot meet the Internet later with a fake address.

§3Planning for Future Connectivity

Enterprises that use private addresses and later decide to connect to the Internet may face renumbering: converting all their addresses to globally unique ones across all their machines. This is expensive and disruptive.

The RFC recommends that any organization anticipating external connectivity apply for globally unique addresses early. The registry will ask for a realistic deployment schedule and evidence of attention to address conservation, but these criteria are reasonable and should not be obstacles.

Even if an enterprise is unsure whether it will connect, the prudent path is to obtain unique addresses and use them from the start. This avoids the pain of renumbering later.

It is cheaper to get real addresses now than to swap them out later on every computer when you do connect.

§4References