tag:blog.tmcnet.com,2011:/hybrid-news2//155/tag:blog.tmcnet.com,2011:/hybrid-news2//155.46569- description of blog Movable Type 4.36 tag:blog.tmcnet.com,2011:/hybrid-news2//155.46569 2011-04-19T02:57:01Z 2011-04-20T03:41:06Z

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 (inpre-CIDR notation) the first dog block is nothing but a single class Anetwork number, while the second...

Tom Keating http://blog.tmcnet.com/blog/tom-keating/ "20-bit block", and to the third as "16-bit" block. Note that (in
pre-CIDR notation) the first dog 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 256 contiguous
class C network numbers.

An enterprise that decides to use IP addresses out of the address
space defined in this document can do so without any coordination
with IANA or an Internet registry. The address space can thus be used
by many enterprises. Addresses within this private address space will
only be unique within the enterprise, or the set of enterprises which
choose to cooperate over this space so they may communicate with each
other in their own private internet.

As before, any enterprise that needs globally unique address space is
required to obtain such addresses from an Internet registry. An
enterprise that requests IP addresses for its external connectivity
will never be assigned addresses from the blocks defined above.

In order to use private address space, an enterprise needs to
determine which hosts do not need to have network layer connectivity
outside the enterprise in the foreseeable future and thus could be
classified as private. Such hosts will use the private address space
defined above.  Private hosts can communicate with all other hosts
inside the enterprise, both public and private. However, they cannot
have IP connectivity to any host outside of the enterprise. While not
having external (outside of the enterprise) IP connectivity private
hosts can still have access to external services via mediating
gateways.

All other hosts will be public and will use globally unique address
space assigned by an Internet Registry. Public hosts can communicate
with other hosts inside the enterprise both public and private and
can have IP connectivity to public hosts outside the enterprise.
Public hosts do not have connectivity to private hosts of other
enterprises.

Moving a host from private to public or vice versa involves a change
of IP address, changes to the appropriate DNS entries, and changes to
configuration files on other hosts that reference the host by IP
address.

Because private addresses have no global meaning, routing information
about private networks shall not be propagated on inter-enterprise
links, and packets with private source or destination addresses
should not be forwarded across such links. Routers in networks not
using private address space, especially those of Internet service
providers, are expected to be configured to reject (filter out)
routing information about private networks. If such a router receives
such information the rejection shall not be treated as a routing
protocol error.

Indirect references to such addresses should be contained within the
enterprise. Prominent examples of such references are DNS Resource
Records and other information referring to internal private
addresses. In particular, Internet service providers should take
measures to prevent such leakage.]]>