| 1 |
<pre>Network Working Group Y. Rekhter |
| 2 |
Request for Comments: 1597 T.J. Watson Research Center, IBM Corp. |
| 3 |
Category: Informational B. Moskowitz |
| 4 |
Chrysler Corp. |
| 5 |
D. Karrenberg |
| 6 |
RIPE NCC |
| 7 |
G. de Groot |
| 8 |
RIPE NCC |
| 9 |
March 1994 |
| 10 |
|
| 11 |
|
| 12 |
<span class="h1">Address Allocation for Private Internets</span> |
| 13 |
|
| 14 |
Status of this Memo |
| 15 |
|
| 16 |
This memo provides information for the Internet community. This memo |
| 17 |
does not specify an Internet standard of any kind. Distribution of |
| 18 |
this memo is unlimited. |
| 19 |
|
| 20 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 21 |
|
| 22 |
This RFC describes methods to preserve IP address space by not |
| 23 |
allocating globally unique IP addresses to hosts private to an |
| 24 |
enterprise while still permitting full network layer connectivity |
| 25 |
between all hosts inside an enterprise as well as between all public |
| 26 |
hosts of different enterprises. The authors hope, that using these |
| 27 |
methods, significant savings can be made on allocating IP address |
| 28 |
space. |
| 29 |
|
| 30 |
For the purposes of this memo, an enterprise is an entity |
| 31 |
autonomously operating a network using TCP/IP and in particular |
| 32 |
determining the addressing plan and address assignments within that |
| 33 |
network. |
| 34 |
|
| 35 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Motivation</span> |
| 36 |
|
| 37 |
With the proliferation of TCP/IP technology worldwide, including |
| 38 |
outside the Internet itself, an increasing number of non-connected |
| 39 |
enterprises use this technology and its addressing capabilities for |
| 40 |
sole intra-enterprise communications, without any intention to ever |
| 41 |
directly connect to other enterprises or the Internet itself. |
| 42 |
|
| 43 |
The current practice is to assign globally unique addresses to all |
| 44 |
hosts that use TCP/IP. There is a growing concern that the finite IP |
| 45 |
address space might become exhausted. Therefore, the guidelines for |
| 46 |
assigning IP address space have been tightened in recent years [<a href="#ref-1" title=""Guidelines for Management of IP Address Space"">1</a>]. |
| 47 |
These rules are often more conservative than enterprises would like, |
| 48 |
in order to implement and operate their networks. |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Rekhter, Moskowitz, Karrenberg & de Groot [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1597">RFC 1597</a> Address Allocation for Private Internets March 1994</span> |
| 55 |
|
| 56 |
|
| 57 |
Hosts within enterprises that use IP can be partitioned into three |
| 58 |
categories: |
| 59 |
|
| 60 |
- hosts that do not require access to hosts in other enterprises |
| 61 |
or the Internet at large; |
| 62 |
|
| 63 |
- hosts that need access to a limited set of outside services |
| 64 |
(e.g., E-mail, FTP, netnews, remote login) which can be handled |
| 65 |
by application layer gateways; |
| 66 |
|
| 67 |
- hosts that need network layer access outside the enterprise |
| 68 |
(provided via IP connectivity); |
| 69 |
|
| 70 |
- hosts within the first category may use IP addresses that are |
| 71 |
unambiguous within an enterprise, but may be ambiguous between |
| 72 |
enterprises. |
| 73 |
|
| 74 |
For many hosts in the second category an unrestricted external access |
| 75 |
(provided via IP connectivity) may be unnecessary and even |
| 76 |
undesirable for privacy/security reasons. Just like hosts within the |
| 77 |
first category, such hosts may use IP addresses that are unambiguous |
| 78 |
within an enterprise, but may be ambiguous between enterprises. |
| 79 |
|
| 80 |
Only hosts in the last category require IP addresses that are |
| 81 |
globally unambiguous. |
| 82 |
|
| 83 |
Many applications require connectivity only within one enterprise and |
| 84 |
do not even need external connectivity for the majority of internal |
| 85 |
hosts. In larger enterprises it is often easy to identify a |
| 86 |
substantial number of hosts using TCP/IP that do not need network |
| 87 |
layer connectivity outside the enterprise. |
| 88 |
|
| 89 |
Some examples, where external connectivity might not be required, |
| 90 |
are: |
| 91 |
|
| 92 |
- A large airport which has its arrival/departure displays |
| 93 |
individually addressable via TCP/IP. It is very unlikely that |
| 94 |
these displays need to be directly accessible from other |
| 95 |
networks. |
| 96 |
|
| 97 |
- Large organisations like banks and retail chains are switching |
| 98 |
to TCP/IP for their internal communication. Large numbers of |
| 99 |
local workstations like cash registers, money machines, and |
| 100 |
equipment at clerical positions rarely need to have such |
| 101 |
connectivity. |
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Rekhter, Moskowitz, Karrenberg & de Groot [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1597">RFC 1597</a> Address Allocation for Private Internets March 1994</span> |
| 111 |
|
| 112 |
|
| 113 |
- For security reasons, many enterprises use application layer |
| 114 |
gateways (e.g., firewalls) to connect their internal network to |
| 115 |
the Internet. The internal network usually does not have direct |
| 116 |
access to the Internet, thus only one or more firewall hosts are |
| 117 |
visible from the Internet. In this case, the internal network |
| 118 |
can use non-unique IP numbers. |
| 119 |
|
| 120 |
- If two enterprises communicate over their own private link, |
| 121 |
usually only a very limited set of hosts is mutually reachable |
| 122 |
from the other enterprise over this link. Only those hosts need |
| 123 |
globally unique IP numbers. |
| 124 |
|
| 125 |
- Interfaces of routers on an internal network usually do not |
| 126 |
need to be directly accessible from outside the enterprise. |
| 127 |
|
| 128 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Private Address Space</span> |
| 129 |
|
| 130 |
The Internet Assigned Numbers Authority (IANA) has reserved the |
| 131 |
following three blocks of the IP address space for private networks: |
| 132 |
|
| 133 |
10.0.0.0 - 10.255.255.255 |
| 134 |
172.16.0.0 - 172.31.255.255 |
| 135 |
192.168.0.0 - 192.168.255.255 |
| 136 |
|
| 137 |
We will refer to the first block as "24-bit block", the second as |
| 138 |
"20-bit block, and to the third as "16-bit" block. Note that the |
| 139 |
first block is nothing but a single class A network number, while the |
| 140 |
second block is a set of 16 contiguous class B network numbers, and |
| 141 |
third block is a set of 255 contiguous class C network numbers. |
| 142 |
|
| 143 |
An enterprise that decides to use IP addresses out of the address |
| 144 |
space defined in this document can do so without any coordination |
| 145 |
with IANA or an Internet registry. The address space can thus be |
| 146 |
used by many enterprises. Addresses within this private address |
| 147 |
space will only be unique within the enterprise. |
| 148 |
|
| 149 |
As before, any enterprise that needs globally unique address space is |
| 150 |
required to obtain such addresses from an Internet registry. An |
| 151 |
enterprise that requests IP addresses for its external connectivity |
| 152 |
will never be assigned addresses from the blocks defined above. |
| 153 |
|
| 154 |
In order to use private address space, an enterprise needs to |
| 155 |
determine which hosts do not need to have network layer connectivity |
| 156 |
outside the enterprise in the foreseeable future. Such hosts will be |
| 157 |
called private hosts, and will use the private address space defined |
| 158 |
above. Private hosts can communicate with all other hosts inside the |
| 159 |
enterprise, both public and private. However, they cannot have IP |
| 160 |
connectivity to any external host. While not having external network |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Rekhter, Moskowitz, Karrenberg & de Groot [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc1597">RFC 1597</a> Address Allocation for Private Internets March 1994</span> |
| 167 |
|
| 168 |
|
| 169 |
layer connectivity private hosts can still have access to external |
| 170 |
services via application layer relays. |
| 171 |
|
| 172 |
All other hosts will be called public and will use globally unique |
| 173 |
address space assigned by an Internet Registry. Public hosts can |
| 174 |
communicate with other hosts inside the enterprise both public and |
| 175 |
private and can have IP connectivity to external public hosts. |
| 176 |
Public hosts do not have connectivity to private hosts of other |
| 177 |
enterprises. |
| 178 |
|
| 179 |
Moving a host from private to public or vice versa involves a change |
| 180 |
of IP address. |
| 181 |
|
| 182 |
Because private addresses have no global meaning, routing information |
| 183 |
about private networks shall not be propagated on inter-enterprise |
| 184 |
links, and packets with private source or destination addresses |
| 185 |
should not be forwarded across such links. Routers in networks not |
| 186 |
using private address space, especially those of Internet service |
| 187 |
providers, are expected to be configured to reject (filter out) |
| 188 |
routing information about private networks. If such a router |
| 189 |
receives such information the rejection shall not be treated as a |
| 190 |
routing protocol error. |
| 191 |
|
| 192 |
Indirect references to such addresses should be contained within the |
| 193 |
enterprise. Prominent examples of such references are DNS Resource |
| 194 |
Records and other information referring to internal private |
| 195 |
addresses. In particular, Internet service providers should take |
| 196 |
measures to prevent such leakage. |
| 197 |
|
| 198 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Advantages and Disadvantages of Using Private Address Space</span> |
| 199 |
|
| 200 |
The obvious advantage of using private address space for the Internet |
| 201 |
at large is to conserve the globally unique address space by not |
| 202 |
using it where global uniqueness is not required. |
| 203 |
|
| 204 |
Enterprises themselves also enjoy a number of benefits from their |
| 205 |
usage of private address space: They gain a lot of flexibility in |
| 206 |
network design by having more address space at their disposal than |
| 207 |
they could obtain from the globally unique pool. This enables |
| 208 |
operationally and administratively convenient addressing schemes as |
| 209 |
well as easier growth paths. |
| 210 |
|
| 211 |
For a variety of reasons the Internet has already encountered |
| 212 |
situations where an enterprise that has not between connected to the |
| 213 |
Internet had used IP address space for its hosts without getting this |
| 214 |
space assigned from the IANA. In some cases this address space had |
| 215 |
been already assigned to other enterprises. When such an enterprise |
| 216 |
later connects to the Internet, it could potentially create very |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Rekhter, Moskowitz, Karrenberg & de Groot [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc1597">RFC 1597</a> Address Allocation for Private Internets March 1994</span> |
| 223 |
|
| 224 |
|
| 225 |
serious problems, as IP routing cannot provide correct operations in |
| 226 |
presence of ambiguous addressing. Using private address space |
| 227 |
provides a safe choice for such enterprises, avoiding clashes once |
| 228 |
outside connectivity is needed. |
| 229 |
|
| 230 |
One could argue that the potential need for renumbering represents a |
| 231 |
significant drawback of using the addresses out of the block |
| 232 |
allocated for private internets. However, we need to observe that |
| 233 |
the need is only "potential", since many hosts may never move into |
| 234 |
the third category, and an enterprise may never decide to |
| 235 |
interconnect (at IP level) with another enterprise. |
| 236 |
|
| 237 |
But even if renumbering has to happen, we have to observe that with |
| 238 |
Classless Inter-Domain Routing (CIDR) an enterprise that is connected |
| 239 |
to the Internet may be encouraged to renumber its public hosts, as it |
| 240 |
changes its Network Service Providers. Thus renumbering is likely to |
| 241 |
happen more often in the future, regardless of whether an enterprise |
| 242 |
does or does not use the addresses out of the block allocated for |
| 243 |
private networks. Tools to facilitate renumbering (e.g., DHCP) would |
| 244 |
certainly make it less of a concern. |
| 245 |
|
| 246 |
Also observe that the clear division of public and private hosts and |
| 247 |
the resulting need to renumber makes uncontrolled outside |
| 248 |
connectivity more difficult, so to some extend the need to renumber |
| 249 |
could be viewed as an advantage. |
| 250 |
|
| 251 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Operational Considerations</span> |
| 252 |
|
| 253 |
A recommended strategy is to design the private part of the network |
| 254 |
first and use private address space for all internal links. Then |
| 255 |
plan public subnets at the locations needed and design the external |
| 256 |
connectivity. |
| 257 |
|
| 258 |
This design is not fixed permanently. If a number of hosts require |
| 259 |
to change status later this can be accomplished by renumbering only |
| 260 |
the hosts involved and installing another physical subnet if |
| 261 |
required. |
| 262 |
|
| 263 |
If a suitable subnetting scheme can be designed and is supported by |
| 264 |
the equipment concerned, it is advisable to use the 24-bit block of |
| 265 |
private address space and make an addressing plan with a good growth |
| 266 |
path. If subnetting is a problem, the 16-bit class C block, which |
| 267 |
consists of 255 contiguous class C network numbers, can be used. |
| 268 |
|
| 269 |
Using multiple IP (sub)nets on the same physical medium has many |
| 270 |
pitfalls. We recommend to avoid it unless the operational problems |
| 271 |
are well understood and it is proven that all equipment supports this |
| 272 |
properly. |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Rekhter, Moskowitz, Karrenberg & de Groot [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc1597">RFC 1597</a> Address Allocation for Private Internets March 1994</span> |
| 279 |
|
| 280 |
|
| 281 |
Moving a single host between private and public status will involve a |
| 282 |
change of address and in most cases physical connectivity. In |
| 283 |
locations where such changes can be foreseen (machine rooms etc.) it |
| 284 |
may be advisable to configure separate physical media for public and |
| 285 |
private subnets to facilitate such changes. |
| 286 |
|
| 287 |
Changing the status of all hosts on a whole (sub)network can be done |
| 288 |
easily and without disruption for the enterprise network as a whole. |
| 289 |
Consequently it is advisable to group hosts whose connectivity needs |
| 290 |
might undergo similar changes in the future on their own subnets. |
| 291 |
|
| 292 |
It is strongly recommended that routers which connect enterprises to |
| 293 |
external networks are set up with appropriate packet and routing |
| 294 |
filters at both ends of the link in order to prevent packet and |
| 295 |
routing information leakage. An enterprise should also filter any |
| 296 |
private networks from inbound routing information in order to protect |
| 297 |
itself from ambiguous routing situations which can occur if routes to |
| 298 |
the private address space point outside the enterprise. |
| 299 |
|
| 300 |
Groups of organisations which foresee a big need for mutual |
| 301 |
communication can consider forming an enterprise by designing a |
| 302 |
common addressing plan supported by the necessary organisational |
| 303 |
arrangements like a registry. |
| 304 |
|
| 305 |
If two sites of the same enterprise need to be connected using an |
| 306 |
external service provider, they can consider using an IP tunnel to |
| 307 |
prevent packet leaks form the private network. |
| 308 |
|
| 309 |
A possible approach to avoid leaking of DNS RRs is to run two |
| 310 |
nameservers, one external server authoritative for all globally |
| 311 |
unique IP addresses of the enterprise and one internal nameserver |
| 312 |
authoritative for all IP addresses of the enterprise, both public and |
| 313 |
private. In order to ensure consistency both these servers should be |
| 314 |
configured from the same data of which the external nameserver only |
| 315 |
receives a filtered version. |
| 316 |
|
| 317 |
The resolvers on all internal hosts, both public and private, query |
| 318 |
only the internal nameserver. The external server resolves queries |
| 319 |
from resolvers outside the enterprise and is linked into the global |
| 320 |
DNS. The internal server forwards all queries for information |
| 321 |
outside the enterprise to the external nameserver, so all internal |
| 322 |
hosts can access the global DNS. This ensures that information about |
| 323 |
private hosts does not reach resolvers and nameservers outside the |
| 324 |
enterprise. |
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Rekhter, Moskowitz, Karrenberg & de Groot [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc1597">RFC 1597</a> Address Allocation for Private Internets March 1994</span> |
| 335 |
|
| 336 |
|
| 337 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span> |
| 338 |
|
| 339 |
[<a id="ref-1">1</a>] Gerich, E., "Guidelines for Management of IP Address Space", <a href="./rfc1466">RFC</a> |
| 340 |
<a href="./rfc1466">1466</a>, Merit Network, Inc., May 1993. |
| 341 |
|
| 342 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span> |
| 343 |
|
| 344 |
While using private address space can improve security, it is not a |
| 345 |
substitute for dedicated security measures. |
| 346 |
|
| 347 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Conclusion</span> |
| 348 |
|
| 349 |
With the described scheme many large enterprises will need only a |
| 350 |
relatively small block of addresses from the globally unique IP |
| 351 |
address space. The Internet at large benefits through conservation |
| 352 |
of globally unique address space which will effectively lengthen the |
| 353 |
lifetime of the IP address space. The enterprises benefit from the |
| 354 |
increased flexibility provided by a relatively large private address |
| 355 |
space. |
| 356 |
|
| 357 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Acknowledgments</span> |
| 358 |
|
| 359 |
We would like to thank Tony Bates (RIPE NCC), Jordan Becker (ANS), |
| 360 |
Hans-Werner Braun (SDSC), Ross Callon (Wellfleet), John Curran |
| 361 |
(NEARNET), Vince Fuller (Barrnet), Tony Li (cisco Systems), Anne Lord |
| 362 |
(RIPE NCC), Milo Medin (NSI), Marten Terpstra (RIPE NCC), and Geza |
| 363 |
Turchanyi (RIPE NCC) for their review and constructive comments. |
| 364 |
|
| 365 |
|
| 366 |
|
| 367 |
|
| 368 |
|
| 369 |
|
| 370 |
|
| 371 |
|
| 372 |
|
| 373 |
|
| 374 |
|
| 375 |
|
| 376 |
|
| 377 |
|
| 378 |
|
| 379 |
|
| 380 |
|
| 381 |
|
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Rekhter, Moskowitz, Karrenberg & de Groot [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc1597">RFC 1597</a> Address Allocation for Private Internets March 1994</span> |
| 391 |
|
| 392 |
|
| 393 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Authors' Addresses</span> |
| 394 |
|
| 395 |
Yakov Rekhter |
| 396 |
T.J. Watson Research Center, IBM Corp. |
| 397 |
P.O. Box 218 |
| 398 |
Yorktown Heights, NY, 10598 |
| 399 |
|
| 400 |
Phone: +1 914 945 3896 |
| 401 |
Fax: +1 914 945 2141 |
| 402 |
EMail: [email protected] |
| 403 |
|
| 404 |
|
| 405 |
Robert G Moskowitz |
| 406 |
Chrysler Corporation |
| 407 |
CIMS: 424-73-00 |
| 408 |
25999 Lawrence Ave |
| 409 |
Center Line, MI 48015 |
| 410 |
|
| 411 |
Phone: +1 810 758 8212 |
| 412 |
Fax: +1 810 758 8173 |
| 413 |
EMail: [email protected] |
| 414 |
|
| 415 |
|
| 416 |
Daniel Karrenberg |
| 417 |
RIPE Network Coordination Centre |
| 418 |
Kruislaan 409 |
| 419 |
1098 SJ Amsterdam, the Netherlands |
| 420 |
|
| 421 |
Phone: +31 20 592 5065 |
| 422 |
Fax: +31 20 592 5090 |
| 423 |
EMail: [email protected] |
| 424 |
|
| 425 |
|
| 426 |
Geert Jan de Groot |
| 427 |
RIPE Network Coordination Centre |
| 428 |
Kruislaan 409 |
| 429 |
1098 SJ Amsterdam, the Netherlands |
| 430 |
|
| 431 |
Phone: +31 20 592 5065 |
| 432 |
Fax: +31 20 592 5090 |
| 433 |
EMail: [email protected] |
| 434 |
|
| 435 |
|
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
Rekhter, Moskowitz, Karrenberg & de Groot [Page 8] |
| 445 |
</pre> |