RFC 1597 (rfc1597) - Page 1 of 8
Address Allocation for Private Internets
Alternative Format: Original Text Document
Network Working Group Y. Rekhter
Request for Comments: 1597 T.J. Watson Research Center, IBM Corp.
Category: Informational B. Moskowitz
Chrysler Corp.
D. Karrenberg
RIPE NCC
G. de Groot
RIPE NCC
March 1994
Address Allocation for Private Internets
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.
1. Introduction
This RFC describes methods to preserve IP address space by not
allocating globally unique IP addresses to hosts private to an
enterprise while still permitting full network layer connectivity
between all hosts inside an enterprise as well as between all public
hosts of different enterprises. The authors hope, that using these
methods, significant savings can be made on allocating IP address
space.
For the purposes of this memo, an enterprise is an entity
autonomously operating a network using TCP/IP and in particular
determining the addressing plan and address assignments within that
network.
2. Motivation
With the proliferation of TCP/IP technology worldwide, including
outside the Internet itself, an increasing number of non-connected
enterprises use this technology and its addressing capabilities for
sole intra-enterprise communications, without any intention to ever
directly connect to other enterprises or the Internet itself.
The current practice is to assign globally unique addresses to all
hosts that use TCP/IP. There is a growing concern that the finite IP
address space might become exhausted. Therefore, the guidelines for
assigning IP address space have been tightened in recent years [1].
These rules are often more conservative than enterprises would like,
in order to implement and operate their networks.
Rekhter, Moskowitz, Karrenberg & de Groot
