As before, any enterprise that needs globally unique address space isrequired to

obtain such addresses from an Internet registry. Indirect references to such add
resses should be contained within theenterprise. Such hosts will use the privat
e address spacedefined above. The address space can thus be usedby many enterpr
ises. However, they cannothave IP connectivity to any host outside of the enter
prise. Anenterprise that requests IP addresses for its external connectivitywil
l never be assigned addresses from the blocks defined above. As before, any ente
rprise that needs globally unique address space isrequired to obtain such addres
ses from an Internet registry. Public hosts do not have connectivity to private
hosts of otherenterprises. While nothaving external (outside of the enterprise)
IP connectivity privatehosts can still have access to external services via med
iatinggateways. In order to use private address space, an enterprise needs todet
ermine which hosts do not need to have network layer connectivityoutside the ent
erprise in the foreseeable future and thus could beclassified as private. Promi
nent examples of such references are DNS ResourceRecords and other information r
eferring to internal privateaddresses. While nothaving external (outside of the
enterprise) IP connectivity privatehosts can still have access to external serv
ices via mediatinggateways. Because private addresses have no global meaning, ro
uting informationabout private networks shall not be propagated on inter-enterpr
iselinks, and packets with private source or destination addressesshould not be
forwarded across such links. Private hosts can communicate with all other hostsi
nside the enterprise, both public and private. . We will refer to the first bloc
k as "24-bit block", the second as"20-bit block", and to the third as "16-bit" b
lock. An enterprise that decides to use IP addresses out of the addressspace def
ined in this document can do so without any coordinationwith IANA or an Internet
registry. Because private addresses have no global meaning, routing information
about private networks shall not be propagated on inter-enterpriselinks, and pac
kets with private source or destination addressesshould not be forwarded across
such links. The address space can thus be usedby many enterprises. Note that (
inpre-CIDR notation) the first block is nothing but a single class Anetwork numb
er, while the second block is a set of 16 contiguousclass B network numbers, and
third block is a set of 256 contiguousclass C network numbers. Moving a host fr
om private to public or vice versa involves a changeof IP address, changes to th
e appropriate DNS entries, and changes toconfiguration files on other hosts that
reference the host by IPaddress. In order to use private address space, an ente
rprise needs todetermine which hosts do not need to have network layer connectiv
ityoutside the enterprise in the foreseeable future and thus could beclassified
as private. While nothaving external (outside of the enterprise) IP connectivit
y privatehosts can still have access to external services via mediatinggateways.
Addresses within this private address space willonly be unique within the ente
rprise, or the set of enterprises whichchoose to cooperate over this space so th
ey may communicate with eachother in their own private internet. Public hosts do
not have connectivity to private hosts of otherenterprises. . Routers in netwo
rks notusing private address space, especially those of Internet serviceprovider
s, are expected to be configured to reject (filter out)routing information about
private networks. Public hosts can communicatewith other hosts inside the ente
rprise both public and private andcan have IP connectivity to public hosts outsi
de the enterprise. As before, any enterprise that needs globally unique address
space isrequired to obtain such addresses from an Internet registry. Prominent
examples of such references are DNS ResourceRecords and other information referr
ing to internal privateaddresses. Routers in networks notusing private address
space, especially those of Internet serviceproviders, are expected to be configu
red to reject (filter out)routing information about private networks. While not
having external (outside of the enterprise) IP connectivity privatehosts can sti
ll have access to external services via mediatinggateways. Because private addre
sses have no global meaning, routing informationabout private networks shall not
be propagated on inter-enterpriselinks, and packets with private source or dest
ination addressesshould not be forwarded across such links. The address space c
an thus be usedby many enterprises. Public hosts do not have connectivity to pri
vate hosts of otherenterprises. Addresses within this private address space wil

lonly be unique within the enterprise, or the set of enterprises whichchoose to

cooperate over this space so they may communicate with eachother in their own pr
ivate internet. Private hosts can communicate with all other hostsinside the ent
erprise, both public and private. Prominent examples of such references are DNS
ResourceRecords and other information referring to internal privateaddresses. I
ndirect references to such addresses should be contained within theenterprise.
In particular, Internet service providers should takemeasures to prevent such le
akage. As before, any enterprise that needs globally unique address space isrequ
ired to obtain such addresses from an Internet registry. Because private address
es have no global meaning, routing informationabout private networks shall not b
e propagated on inter-enterpriselinks, and packets with private source or destin
ation addressesshould not be forwarded across such links. However, they cannoth
ave IP connectivity to any host outside of the enterprise. In particular, Inter
net service providers should takemeasures to prevent such leakage. An enterprise
that decides to use IP addresses out of the addressspace defined in this docume
nt can do so without any coordinationwith IANA or an Internet registry. Private
hosts can communicate with all other hostsinside the enterprise, both public and
private. . As before, any enterprise that needs globally unique address space i
srequired to obtain such addresses from an Internet registry. The address space
can thus be usedby many enterprises. The address space can thus be usedby many
enterprises. Anenterprise that requests IP addresses for its external connecti
vitywill never be assigned addresses from the blocks defined above. If such a r
outer receivessuch information the rejection shall not be treated as a routingpr
otocol error. However, they cannothave IP connectivity to any host outside of t
he enterprise. Routers in networks notusing private address space, especially t
hose of Internet serviceproviders, are expected to be configured to reject (filt
er out)routing information about private networks. We will refer to the first bl
ock as "24-bit block", the second as"20-bit block", and to the third as "16-bit"
block. An enterprise that decides to use IP addresses out of the addressspace d
efined in this document can do so without any coordinationwith IANA or an Intern
et registry. Routers in networks notusing private address space, especially tho
se of Internet serviceproviders, are expected to be configured to reject (filter
out)routing information about private networks. Routers in networks notusing p
rivate address space, especially those of Internet serviceproviders, are expecte
d to be configured to reject (filter out)routing information about private netwo
rks. Moving a host from private to public or vice versa involves a changeof IP a
ddress, changes to the appropriate DNS entries, and changes toconfiguration file
s on other hosts that reference the host by IPaddress. . Moving a host from priv
ate to public or vice versa involves a changeof IP address, changes to the appro
priate DNS entries, and changes toconfiguration files on other hosts that refere
nce the host by IPaddress. However, they cannothave IP connectivity to any host
outside of the enterprise. While nothaving external (outside of the enterprise
) IP connectivity privatehosts can still have access to external services via me
diatinggateways. Such hosts will use the private address spacedefined above. P
ublic hosts can communicatewith other hosts inside the enterprise both public an
d private andcan have IP connectivity to public hosts outside the enterprise. T
he address space can thus be usedby many enterprises. Public hosts can communic
atewith other hosts inside the enterprise both public and private andcan have IP
connectivity to public hosts outside the enterprise. We will refer to the first
block as "24-bit block", the second as"20-bit block", and to the third as "16-b
it" block. Note that (inpre-CIDR notation) the first block is nothing but a sin
gle class Anetwork number, while the second block is a set of 16 contiguousclass
B network numbers, and third block is a set of 256 contiguousclass C network nu
mbers. Private hosts can communicate with all other hostsinside the enterprise,
both public and private. In particular, Internet service providers should takem
easures to prevent such leakage. Anenterprise that requests IP addresses for it
s external connectivitywill never be assigned addresses from the blocks defined
above. The address space can thus be usedby many enterprises. Private hosts can
communicate with all other hostsinside the enterprise, both public and private.
As before, any enterprise that needs globally unique address space isrequired t

o obtain such addresses from an Internet registry. Anenterprise that requests I

P addresses for its external connectivitywill never be assigned addresses from t
he blocks defined above. Indirect references to such addresses should be contain
ed within theenterprise. Addresses within this private address space willonly b
e unique within the enterprise, or the set of enterprises whichchoose to coopera
te over this space so they may communicate with eachother in their own private i
nternet. While nothaving external (outside of the enterprise) IP connectivity p
rivatehosts can still have access to external services via mediatinggateways. .
In order to use private address space, an enterprise needs todetermine which hos
ts do not need to have network layer connectivityoutside the enterprise in the f
oreseeable future and thus could beclassified as private. Routers in networks n
otusing private address space, especially those of Internet serviceproviders, ar
e expected to be configured to reject (filter out)routing information about priv
ate networks. Routers in networks notusing private address space, especially th
ose of Internet serviceproviders, are expected to be configured to reject (filte
r out)routing information about private networks. If such a router receivessuch
information the rejection shall not be treated as a routingprotocol error. All
other hosts will be public and will use globally unique addressspace assigned by
an Internet Registry. Routers in networks notusing private address space, espe
cially those of Internet serviceproviders, are expected to be configured to reje
ct (filter out)routing information about private networks. Prominent examples o
f such references are DNS ResourceRecords and other information referring to int
ernal privateaddresses. Anenterprise that requests IP addresses for its externa
l connectivitywill never be assigned addresses from the blocks defined above. Al
l other hosts will be public and will use globally unique addressspace assigned
by an Internet Registry. Public hosts can communicatewith other hosts inside th
e enterprise both public and private andcan have IP connectivity to public hosts
outside the enterprise. Anenterprise that requests IP addresses for its extern
al connectivitywill never be assigned addresses from the blocks defined above.
Addresses within this private address space willonly be unique within the enterp
rise, or the set of enterprises whichchoose to cooperate over this space so they
may communicate with eachother in their own private internet. 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. If such a router receivessuch information the rejection sha
ll not be treated as a routingprotocol error. Public hosts can communicatewith
other hosts inside the enterprise both public and private andcan have IP connect
ivity to public hosts outside the enterprise. Public hosts can communicatewith
other hosts inside the enterprise both public and private andcan have IP connect
ivity to public hosts outside the enterprise. . Addresses within this private a
ddress space willonly be unique within the enterprise, or the set of enterprises
whichchoose to cooperate over this space so they may communicate with eachother
in their own private internet. Public hosts can communicatewith other hosts in
side the enterprise both public and private andcan have IP connectivity to publi
c hosts outside the enterprise. We will refer to the first block as "24-bit bloc
k", the second as"20-bit block", and to the third as "16-bit" block.