APNIC Home

diff_apnic-086-v003

 apnic-086-v002.txt   apnic-086-v003.txt 
-——————————————————————- ——————————————————————-
APNIC Document identity APNIC Document identity
Title: Policies for IPv4 address space management in the Asia Title: Policies for IPv4 address space management in the Asia
Pacific region Pacific region
Short title: add-manage-policy Short title: add-manage-policy
Document ref: APNIC-086 Document ref: APNIC-086
Version: 002 Version: 003
Date of original publication: 21 December 2001 Date of original publication: 21 December 2001
Date of this version: 19 May 2002 Date of this version: 29 November 2002
Review scheduled: n/a Review scheduled: n/a
Obsoletes: APNIC-076 Obsoletes: Previous versions
Status: Obsolete Status: Obsolete
Comments: Fully implemented 19 May 2002 Comments: n/a
——————————————————————–
Policies for IPv4 address space management in the Asia Pacific region Policies for IPv4 address space management in the Asia Pacific region
About this document About this document
——————- ——————-
This document represents current APNIC practices and policies for IPv4 This document represents current APNIC practices and policies for IPv4
address space. address space.
This document should be read in conjunction with other APNIC documents, This document should be read in conjunction with other APNIC documents,
skipping to change at line 102 skipping to change at line 102
9.3 Criteria for initial allocation 9.3 Criteria for initial allocation
9.4 Criteria for subsequent allocations 9.4 Criteria for subsequent allocations
9.4.1 No guarantee of contiguous allocations 9.4.1 No guarantee of contiguous allocations
9.5 Prior allocations to be used first 9.5 Prior allocations to be used first
9.5.1 Special circumstances – large assignments 9.5.1 Special circumstances – large assignments
9.6 Reservations not supported 9.6 Reservations not supported
9.7 Non-portable address assignments 9.7 Non-portable address assignments
9.8 Validity of allocations and assignments 9.8 Validity of allocations and assignments
9.9 Transfer of address space 9.9 Transfer of address space
10 Address space management 10 LIR address space management
10.1 Assignment window for LIRs 10.1 Assignment window for LIRs
10.2 Assignment usage estimates 10.2 Assignment usage estimates
10.3 Registration requirements 10.3 Sub-allocations by LIRs
10.3.1 Updating registration details 10.3.1 Effect of sub-allocations on LIR‘s usage rate
10.3.2 Registering contact persons 10.4 Registration requirements
10.4 Responsibility to maintain in-addr.arpa records 10.4.1 Updating registration details
10.4.2 Registering contact persons
10.5 Responsibility to maintain in-addr.arpa records
11 Assignments and exchanges 11 Assignments and exchanges
11.1 Small multihoming assignments 11.1 Small multihoming assignments
11.2 Internet Exchange Points 11.2 Internet Exchange Points
11.3 Renumbering to promote aggregation 11.3 Critical infrastructure
11.4 Renumbering to promote aggregation
12 Mergers, acquisitions, and takeovers of LIRs 12 Mergers, acquisitions, and takeovers of LIRs
12.1 Updating registration details 12.1 Updating registration details
12.2 Effect on membership agreement 12.2 Effect on membership agreement
12.3 Consequences for allocations 12.3 Consequences for allocations
12.4 Closure of LIRs 12.4 Closure of LIRs
13 Request evaluation guidelines 13 Request evaluation guidelines
Part 1: Background, definitions, goals, and environment Part 1: Background, definitions, goals, and environment
skipping to change at line 169 skipping to change at line 172
structure described in RFC2050, represented simply in fig.1. structure described in RFC2050, represented simply in fig.1.
[Figure 1: Diagram of distribution hierarchy] [Figure 1: Diagram of distribution hierarchy]
fig.1 +——–+ fig.1 +——–+
| IANA | | IANA |
+——–+ +——–+
| |
+———–+———–+………..+………….+ +———–+———–+………..+………….+
| | | : : | | | : :
+——–+ +——–+ +——–+ +……….+ +……….+ +——–+ +——–+ +——–+ +——–+ +………..+
| ARIN | |RIPE NCC| | APNIC | : Potential future RIRs : | ARIN | |RIPE NCC| | APNIC | | LACNIC | : Potential :
+——–+ +——–+ +——–+ +……….+ +……….+ +——–+ +——–+ +——–+ +——–+ :future RIRs:
| | +………..+
+————–+————-+ +————–+————-+
| | | |
+——+ | +——+ |
| NIR | | National Internet | NIR | | National Internet
+——+ | Registries +——+ | Registries
| | | |
+——+–+——+ | +——+–+——+ |
| | | | Local Internet | | | | Local Internet
+——+ | | +——+ Registries +——+ | | +——+ Registries
| LIR | | | | LIR | | LIR | | | | LIR |
skipping to change at line 231 skipping to change at line 234
* National Internet Registries (NIRs); * National Internet Registries (NIRs);
* Local Internet Registries (LIRs), unless the specific * Local Internet Registries (LIRs), unless the specific
context of the reference requires otherwise. context of the reference requires otherwise.
4.1.1 Regional Internet Registry (RIR) 4.1.1 Regional Internet Registry (RIR)
Regional Internet Registries (RIRs) are established under the Regional Internet Registries (RIRs) are established under the
authority of IANA to serve and represent large geographical authority of IANA to serve and represent large geographical
regions. Their primary role is to manage, distribute, and regions. Their primary role is to manage, distribute, and
register public Internet address space within their respective register public Internet address space within their respective
regions. Currently, there are three RIRs: APNIC, RIPE NCC, and regions. Currently, there are four RIRs: APNIC, RIPE NCC,
ARIN, although a small number of additional RIRs may be LACNIC and ARIN, although a small number of additional RIRs
established in the future. may be established in the future.
4.1.2 National Internet Registry (NIR) 4.1.2 National Internet Registry (NIR)
A National Internet Registry (NIR) primarily allocates address A National Internet Registry (NIR) primarily allocates address
space to its members or constituents, which are generally LIRs space to its members or constituents, which are generally LIRs
organised at a national level. NIRs are expected to apply their organised at a national level. NIRs are expected to apply their
policies and procedures fairly and equitably to all members of policies and procedures fairly and equitably to all members of
their constituency. their constituency.
The policies in this document apply to NIRs; however, this The policies in this document apply to NIRs; however, this
skipping to change at line 282 skipping to change at line 285
4.4 Allocated and Assigned address space 4.4 Allocated and Assigned address space
For the purposes of understanding APNIC address space policies, For the purposes of understanding APNIC address space policies,
it is important to make a clear distinction between the terms it is important to make a clear distinction between the terms
“allocated” and “assigned”. “allocated” and “assigned”.
4.4.1 Allocated 4.4.1 Allocated
Allocated address space is address space that is distributed Allocated address space is address space that is distributed
to IRs for the purpose of subsequent distribution by them. to IRs or other organisations for the purpose of subsequent
distribution by them.
4.4.2 Assigned 4.4.2 Assigned
Assigned address space is address space that is delegated to Assigned address space is address space that is delegated to
an ISP or end-user, for specific use within the Internet an ISP or end-user, for specific use within the Internet
infrastructure they operate. infrastructure they operate.
Assignments must only be made for specific, documented purposes Assignments must only be made for specific, documented purposes
and may not be sub-assigned. and may not be sub-assigned.
skipping to change at line 629 skipping to change at line 633
* maintain fully independent network infrastructures and are * maintain fully independent network infrastructures and are
routed under different Autonomous System numbers; or routed under different Autonomous System numbers; or
* or can otherwise demonstrate a justified need to obtain * or can otherwise demonstrate a justified need to obtain
address space from more than one IR. address space from more than one IR.
9 Address allocation 9 Address allocation
————————– ————————–
9.1 Address space license 9.1 Address space license
APNIC will allocate Internet resources on a ‘license’ basis, APNIC will allocate and assign Internet resources on a
with such licenses to be of specific limited duration ‘license’ basis, with such licenses to be of specific limited
(normally one year). duration (normally one year).
The conditions of all licenses are described in the APNIC The conditions of all licenses are described in the APNIC
membership agreements, service agreements, and other relevant membership agreements, service agreements, and other relevant
APNIC documents. APNIC documents.
Licenses to organisations shall be renewable on the following Licenses to organisations shall be renewable on the following
conditions: conditions:
* the original basis of the allocation or assignment remains * the original basis of the allocation or assignment remains
valid; and valid; and
skipping to change at line 706 skipping to change at line 710
and and
* commit to renumber from previously deployed space into the * commit to renumber from previously deployed space into the
new address space within one year. new address space within one year.
9.4 Criteria for subsequent allocations 9.4 Criteria for subsequent allocations
After the initial allocation to an LIR, all subsequent After the initial allocation to an LIR, all subsequent
allocations will depend on the following: allocations will depend on the following:
* the LIR‘s verified usage rate (which is the rate at which * the LIR‘s verified usage rate (which is the rate at which
the LIR made assignments from relevant past allocations); the LIR made assignments and sub-allocations from relevant
past allocations);
* their documented plans for address space; and * their documented plans for address space; and
* their degree of compliance with APNIC policies with respect * their degree of compliance with APNIC policies with respect
to relevant past allocations. to relevant past allocations.
Based on these factors, APNIC and NIRs will allocate enough Based on these factors, APNIC and NIRs will allocate enough
address space to meet the LIR‘s estimated assignment needs for address space to meet the LIR‘s estimated needs for
a period up to one year. If APNIC or the NIR make an a period up to one year. If APNIC or the NIR make an
allocation based on for a period of less than one year, then allocation based on a period of less than one year, then they
they must inform the LIR of the length of the period and the must inform the LIR of the length of the period and the
reasons for selecting it. reasons for selecting it.
9.4.1 No guarantee of contiguous allocations 9.4.1 No guarantee of contiguous allocations
APNIC will attempt to make subsequent allocations contiguous APNIC will attempt to make subsequent allocations contiguous
with previous allocations, but cannot guarantee that this will with previous allocations, but cannot guarantee that this will
possible. possible.
9.5 Prior allocations to be used first 9.5 Prior allocations to be used first
skipping to change at line 746 skipping to change at line 751
9.6 Reservations not supported 9.6 Reservations not supported
When an LIR wants to assign address space for customers, it When an LIR wants to assign address space for customers, it
must make the assignments from any address space it currently must make the assignments from any address space it currently
holds. holds.
When evaluating allocation requests, reserved address space is When evaluating allocation requests, reserved address space is
considered to be unassigned. considered to be unassigned.
9.7 Non-portable address assignments 9.7 Address aggregation
LIRs must only assign address to customers who will be using It is a condition of all allocations, that the allocated
those addresses in relation to network connectivity services address space is aggregated by the LIR within a minimum
provided by the LIR. Assignments are non-portable. number of route announcements (preferably one).
LIRs must only assign or sub-allocation addresses to
customers who will be using those addresses in relation to
network connectivity services provided by the LIR.
LIRs are expected to enter into agreements with their LIRs are expected to enter into agreements with their
customers specifying that the end-user will hold assignments customers specifying that the end-user will hold the
only for so long as the end-user remains a customer of that addresses only for so long as the end-user remains a customer
LIR. Such agreements should also be consistent with the of that LIR. Such agreements should also be consistent with the
licence under which the address space is being used by the licence under which the address space is being used by the
LIR. LIR.
When an end-user changes service providers they must return
the space assigned to them by the first LIR and renumber into
the new LIR‘s address block.
APNIC policy recognises that there will be cases where
portable address space assignments may be appropriate (see
Section 11). Only APNIC is authorised to make portable
assignments. Organisations may either request their relevant
NIR or LIR to obtain address space from APNIC on their behalf
or seek the address space directly from APNIC themselves.
9.8 Validity of allocations and assignments 9.8 Validity of allocations and assignments
An allocation or assignment of address space is valid only An allocation or assignment of address space is valid only
while the original criteria on which the allocation or while the original criteria on which the allocation or
assignment was based continue to be valid. assignment was based continue to be valid.
An allocation or assignment becomes invalid if it is: An allocation or assignment becomes invalid if it is:
* made for a specific purpose that no longer exists; or * made for a specific purpose that no longer exists; or
* based on information that is later found to be false or * based on information that is later found to be false or
skipping to change at line 793 skipping to change at line 791
address space must be returned to the appropriate IR. address space must be returned to the appropriate IR.
9.9 Transfer of address space 9.9 Transfer of address space
Subject to the more specific provisions of Section 12, APNIC Subject to the more specific provisions of Section 12, APNIC
does not recognise the sale or unauthorised transfer of does not recognise the sale or unauthorised transfer of
address space and will consider all such transfers to be address space and will consider all such transfers to be
invalid. APNIC will require organisations holding such invalid. APNIC will require organisations holding such
transfers to return them to the appropriate IR. transfers to return them to the appropriate IR.
10 Address space management 10 LIR address space management
————————————
Subject to the following provisions, LIRs may either sub-allocate or
assign address space to their customers.
10.1 Assignment window for LIRs 10.1 Assignment window for LIRs
APNIC and NIRs shall apply an assignment window mechanism to APNIC and NIRs shall apply an assignment window mechanism to
help LIRs understand and comply with APNIC policies and the help LIRs understand and comply with APNIC policies and the
address management goals. address management goals.
The assignment window indicates the maximum number of The assignment window indicates the maximum number of
addresses that an LIR may assign to an end-user without first addresses that an LIR may assign or sub-allocate to an
seeking a ‘second opinion’. If an LIR wishes to make an end-user without first seeking a ‘second opinion’. If an LIR
assignment that exceeds its assignment window, the LIR must wishes to make an ssignment or sub-allocation that exceeds
first submit a second opinion request before proceeding with its assignment window, the LIR must first submit a second
the assignment. opinion request.
LIRs start with an assignment window of zero, meaning all LIRs start with an assignment window of zero, meaning all
proposed assignments must first be approved. proposed assignments must first be approved.
APNIC or the relevant NIR will regularly assess the APNIC or the relevant NIR will regularly assess the
proficiency of LIR staff in making assignments and seeking proficiency of LIR staff in making assignments and
second opinions, and will review the size of the assignment sub-allocations and seeking second opinions, and will review
window accordingly. As the LIR staff become more proficient, the size of the assignment window accordingly. As the LIR
the size of their assignment window may be raised. staff become more proficient, the size of their assignment
window may be raised.
The maximum assignment window given to any LIR will be a /19 The maximum assignment window given to any LIR will be a /19
(8,192 addresses). (8,192 addresses).
If an LIR‘s staff appears to become less proficient (for If an LIR‘s staff appears to become less proficient (for
example, due to the training of new staff or other relevant example, due to the training of new staff or other relevant
circumstances) then that LIR‘s assignment window may be circumstances) then that LIR‘s assignment window may be
temporarily reduced. temporarily reduced.
10.2 Assignment usage estimates 10.2 Assignment usage estimates
skipping to change at line 850 skipping to change at line 852
should base their assignment requests on the assumption that should base their assignment requests on the assumption that
25 percent of the address space will be used immediately and 25 percent of the address space will be used immediately and
50 percent used within one year. 50 percent used within one year.
The end-user must provide documentation that supports its one The end-user must provide documentation that supports its one
year usage estimate. If it is not possible for the end-user to year usage estimate. If it is not possible for the end-user to
estimate confidently what the two year usage rate will be, estimate confidently what the two year usage rate will be,
then APNIC or the NIR may make an allocation that will be then APNIC or the NIR may make an allocation that will be
sufficient for the one year needs only. sufficient for the one year needs only.
10.3 Registration requirements 10.3 Sub-allocations by LIRs
LIRs may sub-allocate address space to their downstream
customers which are operating networks, such as ISPs, subject
to the following conditions:
* Sub-allocations are non-portable and must be returned to
the LIR if the downstream customer ceases to receive
connectivity from the LIR.
* Sub-allocations are subject to the LIR‘s assignment window.
Requests for sub-allocations which exceed the LIR‘s
assignment window must first be referred to APNIC for
second opinion approval.
* The downstream customer which receives a sub-allocation
from an LIR is not permitted o further sub-allocate the
address space.
10.3.1 Effect of sub-allocations on lIR’s usage rate
For the purposes of evaluating the LIR‘s usage rate (see
sections 9.4 and 9.5), sub-allocated address space will be
considered as “used”. However, APNIC will give careful
consideration to the registration of assignments within the
allocations, and may request supporting documentation as
necessary.
10.4 Registration requirements
IRs are responsible for promptly and accurately registering IRs are responsible for promptly and accurately registering
their allocations and assignments in the APNIC Whois Database, their allocations, sub-allocations, and assignments in the
as follows: APNIC Whois Database, as follows:
* All allocations must be registered. * All allocations and sub-allocations must be registered.
* Assignments for networks greater than /30 must be * Assignments for networks greater than /30 must be
registered. registered.
* Assignments for networks of /30 or less may be registered, * Assignments for networks of /30 or less may be registered,
at the discretion of the IR and the network administrator. at the discretion of the IR and the network administrator.
* Assignments to hosts may be registered, at the discretion * Assignments to hosts may be registered, at the discretion
of the IR and the end-user. of the IR and the end-user.
10.3.1 Updating registration details 10.4.1 Updating registration details
IRs must update the APNIC Whois Database when any of the IRs must update the APNIC Whois Database when any of the
registration information changes. This is the responsibility registration information changes. This is the responsibility
of the IR concerned, but may be formally delegated to the end- of the IR concerned, but may be formally delegated to the end-
user as a condition of the original assignment. user as a condition of the original assignment.
10.3.2 Registering contact persons 10.4.2 Registering contact persons
Administrative and technical contact persons must be Administrative and technical contact persons must be
registered. registered.
The registered administrative contact (‘admin-c’) must be The registered administrative contact (‘admin-c’) must be
someone who is physically located at the site of the network, someone who is physically located at the site of the network,
subject to the following exceptions: subject to the following exceptions:
* For residential networks or users, the IR‘s technical * For residential networks or users, the IR‘s technical
contact may be registered as admin-c. contact may be registered as admin-c.
* For networks in exceptional circumstances that make it * For networks in exceptional circumstances that make it
impractical to maintain an on-site administrative contact, impractical to maintain an on-site administrative contact,
an off-site person may be registered as the admin-c. an off-site person may be registered as the admin-c.
The technical contact (‘tech-c’) need not be physically The technical contact (‘tech-c’) need not be physically
located at the site of the network, but must be a person who located at the site of the network, but must be a person who
is responsible for the day-to-day operation of the network. is responsible for the day-to-day operation of the network.
10.4 Responsibility to maintain in-addr.arpa records 10.5 Responsibility to maintain in-addr.arpa records
LIRs should maintain in-addr.arpa resource records for their LIRs should maintain in-addr.arpa resource records for their
customers’ networks. If a network is not specifically customers’ networks. If a network is not specifically
associated with an LIR then the in-addra.arpa records should associated with an LIR then the in-addra.arpa records should
be maintained by either the appropriate NIR or APNIC. be maintained by either the appropriate NIR or APNIC.
11 Assignments and exchanges 11 Assignments and exchanges
——————————— ———————————
11.1 Small multihoming assignments 11.1 Small multihoming assignments
skipping to change at line 933 skipping to change at line 961
Internet Exchange Points are eligible to receive a portable Internet Exchange Points are eligible to receive a portable
assignment from APNIC for use on their IXP transit LAN. assignment from APNIC for use on their IXP transit LAN.
A special condition of all assignments made under these terms A special condition of all assignments made under these terms
is that the IXP must not announce the address space to the is that the IXP must not announce the address space to the
global Internet routing table. global Internet routing table.
The minimum assignment made under these terms is /24. The minimum assignment made under these terms is /24.
11.3 Renumbering to promote aggregation 11.3 Critical infrastructure
The following critical infrastructure networks, if operating
in the Asia Pacific region, are eligible to receive a
portable assignment:
* root domain name system (DNS) server;
* global top level domain (gTLD) nameservers;
* country code TLD (ccTLDs) nameservers;
* IANA;
* Regional Internet Registry (RIRs); and
* National Internet Registry (NIRs).
Assignments to critical infrastructure are available only to
the actual operators of the network infrastructure performing
such functions. Registrar organisations which do not actually
host the network housing the registry infrastructure, will
not be eligible for an assignment under this policy.
The minimum assignment made under these terms is /24.
Exchanges made under this policy remain subject to the
address space license policy.
11.4 Renumbering to promote aggregation
Organisations holding multiple non-aggregated portable address Organisations holding multiple non-aggregated portable address
blocks may return them in exchange for a single, aggregated blocks may return them in exchange for a single, aggregated
range, under what is referred to as the “No questions asked range, under what is referred to as the “No questions asked
policy”. This exchange may be requested without the policy”. This exchange may be requested without the
requirement to document the efficiency of existing assignments requirement to document the efficiency of existing assignments
and the usage rates. and the usage rates.
Exchanges made under this policy remain subject to the address Exchanges made under this policy remain subject to the address
space license policy. space license policy.
 End of changes. 29 change blocks. 
62 lines changed or deleted 116 lines changed or added
This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/