| See RFC 1597.
http://info.internet.isi.edu:80/in-notes/rfc/files/rfc1597.txt
"3. Private Address Space
The Internet Assigned Numbers Authority (IANA) has reserved the
following three blocks of the IP address space for private networks:
10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255
We will refer to the first block as "24-bit block", the second as
"20-bit block, and to the third as "16-bit" block. Note that the
first block is nothing but a single class A network number, while the
second block is a set of 16 contiguous class B network numbers, and
third block is a set of 255 contiguous class C network numbers."
|
| While it seems like it might be useful to have non-global IP addresses,
actually using them will probably result in significant pain in the future.
If its not going to result in future pain, then you don't need to limit
yourself to those addresses.
One of the suggested uses is for managing network toasters. However, that
is reasonable only if the current and future scope of your network managament
is, and will always be, a single (extended) LAN. If you can't be assured
of this, and using DEC as an example, this would be foolhardy, you end up
having to route this private net resulting in net 10.0 overlaying net 16.0.
It gets really complicated of there are multiple places within an organization
that is assigning these addresses.
Now is not the time to avoid using global addresses. I would recommend
assigning at least a half dozen addresses to your major servers so that
you can eventually turn them into clusters. Once you have a cluster, you
need an address for every interface plus an address for every application.
BTW, I don't even agree with the use of private addresses for memory channel.
It totally confuses any network management tool that does any automatic
discovery.
|