The Wayback Machine - https://web.archive.org/web/20201022232755/https://tools.ietf.org/rfcdiff?url2=rfc2050
< draft-hubbard-registry-guidelines   rfc2050.txt 
K. Hubbard Network Working Group K. Hubbard
InterNIC Request for Comments: 2050 M. Kosters
M. Kosters Obsoletes: 1466 InterNIC
InterNIC BCP: 12 D. Conrad
D. Conrad Category: Best Current Practice APNIC
APNIC D. Karrenberg
D. Karrenberg RIPE
RIPE J. Postel
J.Postel ISI
IANA November 1996
July 1996
INTERNET REGISTRY IP ALLOCATION GUIDELINES INTERNET REGISTRY IP ALLOCATION GUIDELINES
draft-hubbard-registry-guidelines-04.txt
Status of this Memo Status of this Memo
This memo provides information for the Internet community. This document specifies an Internet Best Current Practices for the
This memo does not specify an Internet standard of any kind. Internet Community, and requests discussion and suggestions for
Distribution of this memo is unlimited. improvements. Distribution of this memo is unlimited.
This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its
areas, and its working groups. Note that other groups may also
distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six IESG Note:
months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as
``work in progress.''
To learn the current status of any Internet-Draft, please check By approving this document as a Best Current Practice,the IESG
the ``1id-abstracts.txt'' listing contained in the Internet- asserts its belief that this policy described herein is an accurate
Drafts Shadow Directories on ftp.is.co.za (Africa), representation of the current practice of the IP address registries
nic.nordu.net (Europe), munnari.oz.au (Pacific Rim), with respect to address assignment. This does not constitute
ds.internic.net (US East Coast), or ftp.isi.edu (US West Coast). endorsement or recommendation of this policy by the IESG. The IESG
will reevaluate its approval of this document in December 1997 taking
into consideration the results of the discussions that will be take
place in the IRE Working Group between now and then.
Abstract Abstract
This document describes the registry system for the distribution of This document describes the registry system for the distribution of
globally unique Internet address space and registry operations. globally unique Internet address space and registry operations.
Particularly this document describes the rules and guidelines Particularly this document describes the rules and guidelines
governing the distribution of this address space. governing the distribution of this address space.
This document replaces RFC 1466, with all the guidelines and This document describes the IP assignment policies currently used by
procedures updated and modified in the light of experience. the Regional Registries to implement the guidelines developed by the
IANA. The guidelines and these policies are subject to revision at
the direction of the IANA. The registry working group (IRE WG) will
be discussing these issues and may provide advice to the IANA about
possible revisions.
This document does not describe private Internet address space and This document replaces RFC 1466, with all the guidelines and
multicast address space. It also does not describe regional and local procedures updated and modified in the light of experience.
refinements of the global rules and guidelines.
This document can be considered the base set of operational guidelines This document does not describe private Internet address space and
in use by all registries. Additional guidelines may be imposed by a multicast address space. It also does not describe regional and
particular registry as appropriate. local refinements of the global rules and guidelines.
Expire in six months This document can be considered the base set of operational
guidelines in use by all registries. Additional guidelines may be
imposed by a particular registry as appropriate.
Table of Contents Table of Contents
1. Introduction.......................................3 1. Introduction.......................................2
2. Allocation Framework...............................4 2. Allocation Framework...............................4
2.1 Guidelines for Internet Service Providers.........4 2.1 Guidelines for Internet Service Providers.........4
2.2 Submission of Reassignment Information............7 2.2 Submission of Reassignment Information............6
3. Assignment Framework..............................7 3. Assignment Framework..............................7
3.1 Common Registry Requirements......................8 3.1 Common Registry Requirements......................7
3.2 Network Engineering Plans.........................9 3.2 Network Engineering Plans.........................8
3.3 Previous Assignment History.......................10 3.3 Previous Assignment History.......................9
3.4 Network Deployment Plans..........................10 3.4 Network Deployment Plans..........................9
3.5 Organization Information..........................10 3.5 Organization Information..........................9
3.6 Expected Utilization Rate.........................10 3.6 Expected Utilization Rate.........................10
4. Operational Guidelines for Registries.............10 4. Operational Guidelines for Registries.............10
5. In-Addr.Arpa Domain Maintenance...................11
5. In-Addr.Arpa Domain Maintenance...................12 6. Right to Appeal...................................11
6. Right to Appeal...................................12
7. References........................................12 7. References........................................12
8. Security Considerations...........................12
9. Authors' Addresses................................13
8. Authors' Addresses................................13 1. Introduction
1. Introduction
The addressing constraints described in this document are The addressing constraints described in this document are largely the
largely the result of the interaction of existing router result of the interaction of existing router technology, address
technology, address assignment, and architectural history. assignment, and architectural history. After extensive review and
After extensive review and discussion, the authors of this discussion, the authors of this document, the IETF working group that
document, the IETF working group that reviewed it and the IESG reviewed it and the IESG have concluded that there are no other
have concluded that there are no other currently deployable currently deployable technologies available to overcome these
technologies available to overcome these limitations. In the limitations. In the event that routing or router technology develops
event that routing or router technology develops to the point to the point that adequate routing aggregation can be achieved by
that adequate routing aggregation can be achieved by other other means or that routers can deal with larger routing and more
means or that routers can deal with larger routing and more dynamic tables, it may be appropriate to review these constraints.
dynamic tables, it may be appropriate to review these
constraints.
Internet address space is distributed according to the following Internet address space is distributed according to the following
three goals: three goals:
1) Conservation: Fair distribution of globally unique Internet address 1) Conservation: Fair distribution of globally unique Internet address
space according to the operational needs of the end-users and Internet space according to the operational needs of the end-users and Internet
Service Providers operating networks using this address space. Service Providers operating networks using this address space.
Prevention of stockpiling in order to maximize the lifetime of the Prevention of stockpiling in order to maximize the lifetime of the
Internet address space. Internet address space.
2) Routability: Distribution of globally unique Internet addresses 2) Routability: Distribution of globally unique Internet addresses
in a hierarchical manner, permitting the routing scalability of in a hierarchical manner, permitting the routing scalability of
the addresses. This scalability is necessary to ensure proper the addresses. This scalability is necessary to ensure proper
operation of Internet routing, although it must be stressed that operation of Internet routing, although it must be stressed that
routability is in no way guaranteed with the allocation or routability is in no way guaranteed with the allocation or
assignment of IPv4 addresses. assignment of IPv4 addresses.
3) Registration: Provision of a public registry documenting address 3) Registration: Provision of a public registry documenting address
space allocation and assignment. This is necessary to ensure space allocation and assignment. This is necessary to ensure
uniqueness and to provide information for Internet trouble shooting uniqueness and to provide information for Internet trouble shooting
at all levels. at all levels.
It is in the interest of the Internet community as a whole that the It is in the interest of the Internet community as a whole that the
above goals be pursued. However it should be noted that above goals be pursued. However it should be noted that
"Conservation" and "Routability" are often conflicting goals. All "Conservation" and "Routability" are often conflicting goals. All
the above goals may sometimes be in conflict with the interests of the above goals may sometimes be in conflict with the interests of
individual end-users or Internet service providers. Careful analysis individual end-users or Internet service providers. Careful analysis
and judgement is necessary in each individual case to find an and judgement is necessary in each individual case to find an
appropriate compromise. appropriate compromise.
The Internet Registry system The Internet Registry system
In order to achieve the above goals the Internet Registry (IR) hierarchy In order to achieve the above goals the Internet Registry (IR)
was established. hierarchy was established.
The Internet Registry hierarchy consists of the following levels of The Internet Registry hierarchy consists of the following levels
hierarchy as seen from the top down: IANA, Regional IRs, Local IRs. of hierarchy as seen from the top down: IANA, Regional IRs, Local
IRs.
IANA IANA
The Internet Assigned Numbers Authority has authority over all number The Internet Assigned Numbers Authority has authority over all
spaces used in the Internet. This includes Internet Address Space. IANA number spaces used in the Internet. This includes Internet
allocates parts of the Internet address space to regional IRs according Address Space. IANA allocates parts of the Internet address space
to its established needs. to regional IRs according to its established needs.
Regional IRs Regional IRs
Regional IRs operate in large geopolitical regions such as continents. Regional IRs operate in large geopolitical regions such as
Currently there are three regional IRs established; InterNIC serving continents. Currently there are three regional IRs established;
North America, RIPE NCC serving Europe, and AP-NIC serving the Asian InterNIC serving North America, RIPE NCC serving Europe, and AP-
Pacific region. Since this does not cover all areas, regional IRs also NIC serving the Asian Pacific region. Since this does not cover
serve areas around its core service areas. It is expected that the all areas, regional IRs also serve areas around its core service
number of regional IRs will remain relatively small. Service areas will areas. It is expected that the number of regional IRs will remain
be of continental dimensions. relatively small. Service areas will be of continental
dimensions.
Regional IRs are established under the authority of the IANA. This Regional IRs are established under the authority of the IANA.
requires consensus within the Internet community of the region. A con- This requires consensus within the Internet community of the
sensus of Internet Service Providers in that region may be necessary to region. A consensus of Internet Service Providers in that region
fulfill that role. may be necessary to fulfill that role.
The specific duties of the regional IRs include coordination and The specific duties of the regional IRs include coordination and
representation of all local IRs in its respective regions. representation of all local IRs in its respective regions.
Local IRs Local IRs
Local IRs are established under the authority of the regional IR and Local IRs are established under the authority of the regional IR
IANA. These local registries have the same role and responsibility as and IANA. These local registries have the same role and
the regional registries within its designated geographical areas. These responsibility as the regional registries within its designated
areas are usually of national dimensions. geographical areas. These areas are usually of national
dimensions.
2. Allocation Framework 2. Allocation Framework
2.1 Guidelines for Internet Service Providers (ISPs) 2.1 Guidelines for Internet Service Providers (ISPs)
This document makes a distinction between the allocation of IP addresses This document makes a distinction between the allocation of IP
and the assignment of IP addresses. Addresses are allocated to ISPs by addresses and the assignment of IP addresses. Addresses are
regional registries to assign to its customer base. allocated to ISPs by regional registries to assign to its customer
base.
ISPs who exchange routing information with other ISPs at multiple loca- ISPs who exchange routing information with other ISPs at multiple
tions and operate without default routing may request space directly locations and operate without default routing may request space
from the regional registry in its geographical area. ISPs with no directly from the regional registry in its geographical area. ISPs
designated regional registry may contact any regional registry and the with no designated regional registry may contact any regional
regional registry may either handle the request or refer the request to registry and the regional registry may either handle the request or
an appropriate registry. refer the request to an appropriate registry.
To facilitate hierarchical addressing, implemented using Classless To facilitate hierarchical addressing, implemented using Classless
Inter-Domain Routing (CIDR), all other ISPs should request address space Inter-Domain Routing (CIDR), all other ISPs should request address
directly from its upstream provider. ISPs only request address space space directly from its upstream provider. ISPs only request address
directly from regional registries if their immediate requirement, when space directly from regional registries if their immediate
satisfied with a contiguous block allocation, has a reasonable probabil- requirement, when satisfied with a contiguous block allocation, has a
ity of being routable on the Internet, and they meet one or more of the reasonable probability of being routable on the Internet, and they
following conditions. meet one or more of the following conditions.
a) the ISP is directly connected to a major routing exchange a) the ISP is directly connected to a major routing exchange
(for purposes of this document, a major routing exchange (for purposes of this document, a major routing exchange
is defined as a neutral layer 2 exchange point connecting is defined as a neutral layer 2 exchange point connecting
four or more unrelated ISPs.) four or more unrelated ISPs.)
b) the ISP is multi-homed, that is, it has more than one b) the ISP is multi-homed, that is, it has more than one
simultaneous connection to the global Internet and no simultaneous connection to the global Internet and no
connection is favored over the other connection is favored over the other
Note that addresses issued directly from the IRs, (non-provider Note that addresses issued directly from the IRs (non-provider
based), are the least likely to be routable across the Internet.
based),
are the least likely to be routable across the Internet.
The following are the IP allocation guidelines for ISPs: The following are the IP allocation guidelines for ISPs:
1. CIDR addresses are allocated to ISPs in blocks. It is 1. CIDR addresses are allocated to ISPs in blocks. It is
recommended that those blocks remain intact. Fragmentation of recommended that those blocks remain intact. Fragmentation of
CIDR blocks is discouraged. More specifically, ISPs are CIDR blocks is discouraged. More specifically, ISPs are
encouraged to treat address assignments as loans for the encouraged to treat address assignments as loans for the
duration of the connectivity provision. At the termination duration of the connectivity provision. At the termination
of the Internet connectivity contract, e.g., the customer of the Internet connectivity contract, e.g., the customer
moves to another service provider, it is recommended the moves to another service provider, it is recommended the
customer return the network addresses currently in use and customer return the network addresses currently in use and
renumber into the new provider's address space. The ISP renumber into the new provider's address space. The ISP
should allow sufficient time for the renumbering process to be should allow sufficient time for the renumbering process to be
completed before the IP addresses are reused. completed before the IP addresses are reused.
2. To ensure efficient implementation and use of Classless 2. To ensure efficient implementation and use of Classless
Inter-Domain Routing (CIDR), the Regional Registries issue Inter-Domain Routing (IDR), the Regional Registries issue
address space on appropriate "CIDR-supported" bit boundaries. address space on appropriate "CIDR-supported" bit boundaries.
3. ISPs are required to utilize address space in an efficient 3. ISPs are required to utilize address space in an efficient
manner. To this end, ISPs should have documented manner. To this end, ISPs should have documented
justification available for each assignment. The regional justification available for each assignment. The regional
registry may, at any time, ask for this information. If the registry may, at any time, ask for this information. If the
information is not available, future allocations may be impacted. information is not available, future allocations may be impacted.
In extreme cases, existing loans may be impacted. In extreme cases, existing loans may be impacted.
4. IP addresses are allocated to ISPs using a slow-start 4. IP addresses are allocated to ISPs using a slow-start
procedure. New ISPs will receive a minimal amount based procedure. New ISPs will receive a minimal amount based
on immediate requirement. Thereafter, allocated blocks may be on immediate requirement. Thereafter, allocated blocks may be
increased based on utilization verification supplied to the increased based on utilization verification supplied to the
regional registry. The parent registries are responsible for regional registry. The parent registries are responsible for
determining appropriate initial and subsequent allocations. determining appropriate initial and subsequent allocations.
Additional address allocations will provide enough address space Additional address allocations will provide enough address space
to enable the ISP to assign addresses for three months to enable the ISP to assign addresses for three months
without requesting additional address space from its parent without requesting additional address space from its parent
registry. Please note that projected customer base has little registry. Please note that projected customer base has little
impact on the address allocations made by the parent registries. impact on the address allocations made by the parent registries.
Initial allocation will not be based on any current or future Initial allocation will not be based on any current or future
routing restrictions but on demonstrated requirements. routing restrictions but on demonstrated requirements.
5. Due to the requirement to increase the utilization efficiency 5. Due to the requirement to increase the utilization efficiency
of IPv4 address space, all assignments are made with the of IPv4 address space, all assignments are made with the
assumption that sites make use of variable length subnet mask assumption that sites make use of variable length subnet mask
(VLSM) and classless technologies within their network. Any (VLSM) and classless technologies within their network. Any
request for address space based on the use of classfull request for address space based on the use of classfull
assumptions will require a detailed justification. The use of assumptions will require a detailed justification. The use of
classfull technologies for the purposes of administrative classfull technologies for the purposes of administrative
convenience is generally insupportable due to the limited convenience is generally insupportable due to the limited
availability of free IPv4 address space. availability of free IPv4 address space.
6. Regional registries may set a maximum limit on assignment sizes 6. Regional registries may set a maximum limit on assignment sizes
such that a second opinion of the regional registry is required. such that a second opinion of the regional registry is required.
7. Due to constraints on the available free pool of IPv4 address 7. Due to constraints on the available free pool of IPv4 address
space, the use of static IP address assignments (e.g., one space, the use of static IP address assignments (e.g., one
address per customer) for dial-up users is strongly discouraged. address per customer) for dial-up users is strongly discouraged.
While it is understood that the use of static addressing may While it is understood that the use of static addressing may
ease some aspects of administration, the current rate of ease some aspects of administration, the current rate of
consumption of the remaining unassigned IPv4 address space does consumption of the remaining unassigned IPv4 address space does
not permit the assignment of addresses for administrative ease. not permit the assignment of addresses for administrative ease.
Organizations considering the use of static IP address assignment Organizations considering the use of static IP address assignment
are expected to investigate and implement dynamic assignment are expected to investigate and implement dynamic assignment
technologies whenever possible. technologies whenever possible.
2.2 Submission of Reassignment Information 2.2 Submission of Reassignment Information
It is imperative that reassignment information be submitted in a prompt It is imperative that reassignment information be submitted in a
and efficient manner to facilitate database maintenance and ensure prompt and efficient manner to facilitate database maintenance and
database integrity. Therefore, assignment information must be ensure database integrity. Therefore, assignment information must be
submitted to the regional registry immediately upon making the submitted to the regional registry immediately upon making the
assignment. The following reasons necessitate transmission of the assignment. The following reasons necessitate transmission of the
reassignment information: reassignment information:
a) to provide operational staff with information on who is using a) to provide operational staff with information on who is using
the network number and to provide a contact in case of the network number and to provide a contact in case of
operational/ security problems, operational/security problems,
b) to ensure that a provider has exhausted a majority of its b) to ensure that a provider has exhausted a majority of its
current CIDR allocation, thereby justifying an additional current CIDR allocation, thereby justifying an additional
allocation, allocation,
c) to assist in IP allocation studies. c) to assist in IP allocation studies.
Procedures for submitting the reassignment information will be Procedures for submitting the reassignment information will be
determined by each regional registry based on its unique requirements. determined by each regional registry based on its unique
requirements.
All sub-registries (ISPs, Local registries, etc.) must register with All sub-registries (ISPs, Local registries, etc.) must register with
their respective regional registry to receive information regarding their respective regional registry to receive information regarding
reassignment guidelines. No additional CIDR blocks will be reassignment guidelines. No additional CIDR blocks will be allocated
allocated by the regional registry or upstream providers until by the regional registry or upstream providers until approximately
approximately 80% of all reassignment information has been submitted. 80% of all reassignment information has been submitted.
3. Assignment Framework 3. Assignment Framework
An assignment is the delegation of authority over a block of IP An assignment is the delegation of authority over a block of IP
addresses to an end enterprise. The end enterprise will use addresses addresses to an end enterprise. The end enterprise will use
from an assignment internally only; it will not sub-delegate those addresses from an assignment internally only; it will not sub-
addresses. This section discusses some of the issues involved in delegate those addresses. This section discusses some of the issues
assignments and the framework behind the assignment of addresses. involved in assignments and the framework behind the assignment of
addresses.
In order for the Internet to scale using existing technologies, use of In order for the Internet to scale using existing technologies, use
regional registry services should be limited to the assignment of IP of regional registry services should be limited to the assignment of
addresses for organizations meeting one or more of the following condi- IP addresses for organizations meeting one or more of the following
tions: conditions:
a) the organization has no intention of connecting to a) the organization has no intention of connecting to
the Internet-either now or in the future-but it still the Internet-either now or in the future-but it still
requires a globally unique IP address. The organization requires a globally unique IP address. The organization
should consider using reserved addresses from RFC1918. should consider using reserved addresses from RFC1918.
If it is determined this is not possible, they can be If it is determined this is not possible, they can be
issued unique (if not Internet routable) IP addresses. issued unique (if not Internet routable) IP addresses.
b) the organization is multi-homed with no favored connection. b) the organization is multi-homed with no favored connection.
c) the organization's actual requirement for IP space is c) the organization's actual requirement for IP space is
very large, for example, the network prefix required to very large, for example, the network prefix required to
cover the request is of length /18 or shorter. cover the request is of length /18 or shorter.
All other requestors should contact its ISP for address All other requestors should contact its ISP for address space or
space or utilize the addresses reserved for non-connected networks utilize the addresses reserved for non-connected networks described
described in RFC1918 until an Internet connection is established. in RFC1918 until an Internet connection is established. Note that
Note that addresses issued directly from the IRs,(non-provider based), addresses issued directly from the IRs,(non-provider based), are the
are the least likely to be routable across the Internet. least likely to be routable across the Internet.
3.1 Common Registry Requirements 3.1 Common Registry Requirements
Because the number of available IP addresses on the Internet is limited, Because the number of available IP addresses on the Internet is
the utilization rate of address space will be a key factor in network limited, the utilization rate of address space will be a key factor
number assignment. Therefore, in the best interest of the Internet as a in network number assignment. Therefore, in the best interest of the
whole, specific guidelines have been created to govern the assignment of Internet as a whole, specific guidelines have been created to govern
addresses based on utilization rates. the assignment of addresses based on utilization rates.
Although topological issues may make exceptions necessary, the basic Although topological issues may make exceptions necessary, the basic
criteria that should be met to receive network numbers are listed below: criteria that should be met to receive network numbers are listed
below:
25% immediate utilization rate 25% immediate utilization rate
50% utilization rate within 1 year 50% utilization rate within 1 year
The utilization rate above is to be used as a guideline, there may be be The utilization rate above is to be used as a guideline, there may be
occasions when the 1 year rate does not fall exactly in this range. be occasions when the 1 year rate does not fall exactly in this
Organizations must exhibit a high confidence level in its 1 year utili- range. Organizations must exhibit a high confidence level in its 1
zation rate and supply documentation to justify the level of confidence. year utilization rate and supply documentation to justify the level
of confidence.
Organizations will be assigned address space based on immediate utiliza- Organizations will be assigned address space based on immediate
tion plus 1 year projected utilization. A prefix longer than /24 may be utilization plus 1 year projected utilization. A prefix longer than
issued if deemed appropriate. Organizations with less than 128 hosts /24 may be issued if deemed appropriate. Organizations with less
will not be issued an IP address directly from the IRs. Organizations than 128 hosts will not be issued an IP address directly from the
may be issued a prefix longer than /24 if the organization can provide IRs. Organizations may be issued a prefix longer than /24 if the
documentation from a registry recognized ISP indicating the ISP will organization can provide documentation from a registry recognized ISP
accept the long prefix for injection into the global routing system. indicating the ISP will accept the long prefix for injection into the
global routing system.
Exceptions to the criteria will not be made based on insufficient equip- Exceptions to the criteria will not be made based on insufficient
ment without additional detailed justification. Organizations should equipment without additional detailed justification. Organizations
implement variable length subnet mask (VLSM) internally to maximize the should implement variable length subnet mask (VLSM) internally to
effective utilization of address space. Address assignments will be maximize the effective utilization of address space. Address
made under the assumption that VLSM is or will be implemented. assignments will be made under the assumption that VLSM is or will be
implemented.
IP addresses are valid as long as the criteria continues to be met. The IP addresses are valid as long as the criteria continues to be met.
IANA reserves the right to invalidate any IP assignments once it is The IANA reserves the right to invalidate any IP assignments once it
determined the the requirement for the address space no longer exists. is determined the the requirement for the address space no longer
In the event of address invalidation, reasonable efforts will be made by exists. In the event of address invalidation, reasonable efforts
the appropriate registry to inform the organization that the addresses will be made by the appropriate registry to inform the organization
have been returned to the free pool of IPv4 address space. that the addresses have been returned to the free pool of IPv4
address space.
3.2 Network Engineering Plans 3.2 Network Engineering Plans
Before a registry makes an assignment, it must examine each address Before a registry makes an assignment, it must examine each address
space request in terms of the requesting organization's networking space request in terms of the requesting organization's networking
plans. These plans should be documented, and the following information plans. These plans should be documented, and the following
should be included: information should be included:
1. subnetting plans, including subnet masks and number of 1. subnetting plans, including subnet masks and number of
hosts on each subnet for at least one year hosts on each subnet for at least one year
2. a description of the network topology 2. a description of the network topology
3. a description of the network routing plans, including the 3. a description of the network routing plans, including the
routing protocols to be used as well as any limitations. routing protocols to be used as well as any limitations.
The subnetting plans should include: The subnetting plans should include:
a) a tabular listing of all subnets on the network a) a tabular listing of all subnets on the network
b) its associated subnet masks b) its associated subnet masks
c) the estimated number of hosts c) the estimated number of hosts
d) a brief descriptive remark regarding the subnet. d) a brief descriptive remark regarding the subnet.
If subnetting is not being used, an explanation why it cannot be imple- If subnetting is not being used, an explanation why it cannot be
mented is required. Care must be taken to ensure that the host and implemented is required. Care must be taken to ensure that the host
subnet estimates correspond to realistic requirements and are not based and subnet estimates correspond to realistic requirements and are not
on administrative convenience. based on administrative convenience.
3.3 Previous Assignment History 3.3 Previous Assignment History
To promote increased usage of address space, the registries will require To promote increased usage of address space, the registries will
an accounting of address space previously assigned to the enterprise, if require an accounting of address space previously assigned to the
any. In the context of address space allocation, an "enterprise" con- enterprise, if any. In the context of address space allocation, an
sists of all divisions and/or subsidiaries falling under a common parent "enterprise" consists of all divisions and/or subsidiaries falling
organization. The previous assignment history should include all net- under a common parent organization. The previous assignment history
work numbers assigned to the organization, plus the network masks for should include all network numbers assigned to the organization, plus
those networks and the number of hosts on each (sub-)network. Suffi- the network masks for those networks and the number of hosts on each
cient corroborating evidence should be provided to allow the assigning (sub-)network. Sufficient corroborating evidence should be provided
registry to be confident that the network descriptions provided are to allow the assigning registry to be confident that the network
accurate. Routing table efficiency will be taken into account by the descriptions provided are accurate. Routing table efficiency will be
regional registries and each request will be handled on a case by case taken into account by the regional registries and each request will
basis. be handled on a case by case basis.
3.4 Network Deployment Plans 3.4 Network Deployment Plans
In order to assign an appropriate amount of space in the required time In order to assign an appropriate amount of space in the required
frame, a registry may request deployment plans for a network. Deploy- time frame, a registry may request deployment plans for a network.
ment plans should include the number of hosts to be deployed per time Deployment plans should include the number of hosts to be deployed
period, expected network growth during that time period, and changes in per time period, expected network growth during that time period, and
the network topology that describe the growth. changes in the network topology that describe the growth.
3.5 Organization Information 3.5 Organization Information
A registry may request that an organization furnish a published descrip- A registry may request that an organization furnish a published
tion verifying that the organization is what it claims to be. This description verifying that the organization is what it claims to be.
information can consist of brochures, documents of incorporation, or This information can consist of brochures, documents of
similar published material. incorporation, or similar published material.
3.6 Expected Utilization Rate 3.6 Expected Utilization Rate
As stated in the foregoing text, one of the key factors in determining As stated in the foregoing text, one of the key factors in
how much address space is appropriate for an organization is the determining how much address space is appropriate for an organization
expected utilization rate of the network. The expected utilization rate is the expected utilization rate of the network. The expected
is the number of hosts connected to the network divided by the total utilization rate is the number of hosts connected to the network
number of hosts possible on the network. In addition, the estimated divided by the total number of hosts possible on the network. In
number of hosts should be projected over a reasonable time frame, i.e., addition, the estimated number of hosts should be projected over a
one in which the requesting enterprise has a high level of confidence. reasonable time frame, i.e., one in which the requesting enterprise
The minimal utilization rate is set by the IANA and may be changed at has a high level of confidence. The minimal utilization rate is set
any time. New utilization rates may be enforced by the regional regis- by the IANA and may be changed at any time. New utilization rates
tries prior to updating the written policy. may be enforced by the regional registries prior to updating the
written policy.
4. Operational Guidelines For Registries 4. Operational Guidelines For Registries
1. Regional Registries provide registration services as its 1. Regional Registries provide registration services as its
primary function. Therefore, regional registries may charge some primary function. Therefore, regional registries may charge some
fee for services rendered, generally in relation to the cost of fee for services rendered, generally in relation to the cost of
providing those services. providing those services.
2. Regardless of the source of its address space, sub-registries 2. Regardless of the source of its address space, sub-registries
(Local IRs, ISPs, etc.) must adhere to the guidelines of its (Local IRs, ISPs, etc.) must adhere to the guidelines of its
regional registry. In turn, it must also ensure that its regional registry. In turn, it must also ensure that its
customers follow those guidelines. customers follow those guidelines.
3. To maximize the effective use of address space, IP addresses need 3. To maximize the effective use of address space, IP addresses need
to be assigned/allocated in classless blocks. With this in mind, to be assigned/allocated in classless blocks. With this in mind,
assignments will not be made in Class Cs or Bs but by prefix assignments will not be made in Class Cs or Bs but by prefix
length. Consequently, an organization that would have been length. Consequently, an organization that would have been
assigned a Class B in the past will now be assigned a /16 prefix, assigned a Class B in the past will now be assigned a /16 prefix,
regardless of the actual address class. regardless of the actual address class.
4. All IP address requests are subject to audit and verification 4. All IP address requests are subject to audit and verification
by any means deemed appropriate by the regional registry. by any means deemed appropriate by the regional registry.
If any assignment is found to be based on false information, If any assignment is found to be based on false information,
the registry may invalidate the request and return the the registry may invalidate the request and return the
assigned addresses back to the pool of free addresses for assigned addresses back to the pool of free addresses for
later assignment. later assignment.
5. Due to technical and implementation constraints on the Internet 5. Due to technical and implementation constraints on the Internet
routing system and the possibility of routing overload, major routing system and the possibility of routing overload, major
transit providers may need to impose certain restrictions to transit providers may need to impose certain restrictions to
reduce the number of globally advertised routes. This may reduce the number of globally advertised routes. This may
include setting limits on the size of CIDR prefixes added to include setting limits on the size of CIDR prefixes added to
the routing tables, filtering of non-aggregated routes, etc. the routing tables, filtering of non-aggregated routes, etc.
Therefore, addresses obtained directly from regional registry Therefore, addresses obtained directly from regional registry
(provider-independent, also known as portable) are not (provider-independent, also known as portable) are not
guaranteed routable on the Internet. guaranteed routable on the Internet.
6. Information provided to request address space is often considered 6. Information provided to request address space is often considered
sensitive by the requesting organization. The assigning sensitive by the requesting organization. The assigning
registry must treat as confidential any and all information registry must treat as confidential any and all information
that the requesting organization specifically indicates as that the requesting organization specifically indicates as
sensitive. When a requesting organization does not have sensitive. When a requesting organization does not have
assurance of privacy, the parent of the assigning registry may assurance of privacy, the parent of the assigning registry may
be required to do the assignment. In such cases, the parent be required to do the assignment. In such cases, the parent
registry will provide the assigning registry with information registry will provide the assigning registry with information
regarding the appropriate amount of address space to allocate. regarding the appropriate amount of address space to allocate.
7. The transfer of IP addresses from one party to another must be 7. The transfer of IP addresses from one party to another must be
approved by the regional registries. The party trying to obtain approved by the regional registries. The party trying to obtain
the IP address must meet the same criteria as if they were the IP address must meet the same criteria as if they were
requesting an IP address directly from the IR. requesting an IP address directly from the IR.
5. In-ADDR.ARPA Domain Maintenance 5. In-ADDR.ARPA Domain Maintenance
The regional registries will be responsible for maintaining IN-ADDR.ARPA The regional registries will be responsible for maintaining IN-
records only on the parent blocks of IP addresses issued directly to the ADDR.ARPA records only on the parent blocks of IP addresses issued
ISPs or those CIDR blocks of less than /16. Local IRs/ISPs with a pre- directly to the ISPs or those CIDR blocks of less than /16. Local
fix length of /16 or shorter will be responsible for maintaining all IRs/ISPs with a prefix length of /16 or shorter will be responsible
IN-ADDR.ARPA resource records for its customers. for maintaining all IN-ADDR.ARPA resource records for its customers.
IN-ADDR.ARPA resource records for networks not associated with a IN-ADDR.ARPA resource records for networks not associated with a
specific provider will continue to be maintained by the regional regis- specific provider will continue to be maintained by the regional
try. registry.
6. Right to Appeal 6. Right to Appeal
If an organization feels that the registry that assigned its address has
not performed its task in the requisite manner, the organization has the
right of appeal to the parent registry.
In such cases, the assigning registry shall make available all relevant If an organization feels that the registry that assigned its address
documentation to the parent registry, and the decision of the parent has not performed its task in the requisite manner, the organization
registry shall be considered final (barring additional appeals to the has the right of appeal to the parent registry.
parent registry's parent). If necessary, after exhausting all other
avenues, the appeal may be forwarded to IANA for a final decision. Each
registry must, as part of their policy, document and specify how to
appeal a registry assignment decision.
7. References In such cases, the assigning registry shall make available all
relevant documentation to the parent registry, and the decision of
the parent registry shall be considered final (barring additional
appeals to the parent registry's parent). If necessary, after
exhausting all other avenues, the appeal may be forwarded to IANA for
a final decision. Each registry must, as part of their policy,
document and specify how to appeal a registry assignment decision.
[RFC 1519] V. Fuller, T. Li, J. Yu, K. Varadhan, 7. References
"Classless Inter- Domain Routing (CIDR): an Address
Assignment and Aggregation Strategy".
[RFC 1518] Y. Rekhter, T. Li, "An Architecture for IP [RFC 1519] Fuller, V., Li, T., Yu, J., and K. Varadhan,
Address Allocation with CIDR". "Classless Inter- Domain Routing (CIDR): an Address
Assignment and Aggregation Strategy", September 1993.
[RFC 1918] Y. Rekhter, B. Moskowitz, D. Karrenberg, G. de Groot, [RFC 1518] Rekhter, Y., and T. Li, "An Architecture for IP
"Address Allocation for Private Internets". Address Allocation with CIDR", September 1993.
[RFC 1814] E. Gerich, "Unique Addresses are Good" [RFC 1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., and
G. de Groot, "Address Allocation for Private Internets",
February 1996.
[RFC 1900] B. Carpenter, Y. Rekhter, "Renumbering Needs Work" [RFC 1814] Gerich, E., "Unique Addresses are Good", June 1995.
8. Authors' Addresses
Kim Hubbard [RFC 1900] Carpenter, B., and Y. Rekhter, "Renumbering Needs Work",
InterNIC Registration Services February 1996.
c/o Network Solutions
505 Huntmar Park Drive
Herndon, VA 22070
Phone: (703) 742-4870
email: kimh@internic.net
Jon Postel 8. Security Considerations
USC/Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292
Phone: 310-822-1511
EMail: Postel@ISI.EDU
Mark Kosters Security issues are not discussed in this memo.
InterNIC Registration Services
c/o Network Solutions
505 Huntmar Park Drive
Herndon, VA 22070
Phone: (703) 742-4795
email: markk@internic.net
David Conrad 9. Authors' Addresses
Asia Pacific Network Information Center
c/o United Nations University
53-70 Jingumae 5-chome,
Shibuya-ku, Tokyo 150
JP
Phone: +81-3-5467-7014
email: davidc@APNIC.NET
Daniel Karrenberg Kim Hubbard
RIPE NCC InterNIC Registration Services
Kruislaan 409 c/o Network Solutions
SJ Amsterdam NL-1098 505 Huntmar Park Drive
NL Herndon, VA 22070
Phone: +31 20 592 5065
email: dfk@RIPE.NET Phone: (703) 742-4870
EMail: kimh@internic.net
Mark Kosters
InterNIC Registration Services
c/o Network Solutions
505 Huntmar Park Drive
Herndon, VA 22070
Phone: (703) 742-4795
EMail: markk@internic.net
David Conrad
Asia Pacific Network Information Center
c/o United Nations University
53-70 Jingumae 5-chome,
Shibuya-ku, Tokyo 150
JP
Phone: +81-3-5467-7014
EMail: davidc@APNIC.NET
Daniel Karrenberg
RIPE NCC
Kruislaan 409
SJ Amsterdam NL-1098
NL
Phone: +31 20 592 5065
EMail: dfk@RIPE.NET
Jon Postel
USC/Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292
Phone: 310-822-1511
EMail: Postel@ISI.EDU
 End of changes. 92 change blocks. 
323 lines changed or deleted 299 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/