APNIC Home

diff_apnic-086-v008

 apnic-086-v007.txt   apnic-086-v008.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: 007 Version: 008
Date of original publication: 21 December 2001 Date of original publication: 21 December 2001
Date of this version: 4 August 2008 Date of this version: 16 February 2009
Review scheduled: n/a Review scheduled: n/a
Obsoletes: All previous versions Obsoletes: All previous versions
Status: Obsolete Status: Obsolete
Comments: n/a 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
——————- ——————-
skipping to change at line 50 skipping to change at line 50
4 Definitions 4 Definitions
4.1 Internet Registry (IR) 4.1 Internet Registry (IR)
4.1.1 Regional Internet Registry (RIR) 4.1.1 Regional Internet Registry (RIR)
4.1.2 National Internet Registry (NIR) 4.1.2 National Internet Registry (NIR)
4.1.3 Local Internet Registry (LIR) 4.1.3 Local Internet Registry (LIR)
4.2 Internet Exchange Point 4.2 Internet Exchange Point
4.3 Address space 4.3 Address space
4.4 Allocated and Assigned address space 4.4 Allocated and Assigned address space
4.4.1 Allocated 4.4.1 Allocated
4.4.2 Assigned 4.4.2 Assigned
4.5 Current resources
4.6 Historical resources
5 Goals of address space management 5 Goals of address space management
5.1 Goals 5.1 Goals
5.1.1 Uniqueness 5.1.1 Uniqueness
5.1.2 Registration 5.1.2 Registration
5.1.3 Aggregation 5.1.3 Aggregation
5.1.4 Conservation 5.1.4 Conservation
5.1.5 Fairness 5.1.5 Fairness
5.2 Conflict of goals 5.2 Conflict of goals
skipping to change at line 101 skipping to change at line 103
9.2.1 Exceptions to slow start 9.2.1 Exceptions to slow start
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
9.10 Distribution of the final /8 worth of space in the
unallocated APNIC IPv4 address pool
9.10.1 Allocations to LIRs
9.10.2 Allocations for future uses
10 LIR 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 Sub-allocations by LIRs 10.3 Sub-allocations by LIRs
10.3.1 Effect of sub-allocations on LIR‘s usage rate 10.3.1 Effect of sub-allocations on LIR‘s usage rate
10.4 Registration requirements 10.4 Registration requirements
10.4.1 Updating registration details 10.4.1 Updating registration details
10.4.2 Registering contact persons 10.4.2 Registering contact persons
10.5 Responsibility to maintain in-addr.arpa records 10.5 Responsibility to maintain in-addr.arpa records
skipping to change at line 170 skipping to change at line 176
IPv4 addresses are distributed in accordance with the hierarchical IPv4 addresses are distributed in accordance with the hierarchical
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 | | LACNIC | : Potential : | ARIN | |RIPE NCC| | APNIC | | LACNIC | | AfriNIC|
+——–+ +——–+ +——–+ +——–+ :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 295 skipping to change at line 301
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.
4.5 Current resources
Current resources are Internet resources registered by APNIC under
explicit policies and agreements. Resources include public IPv4 and
IPv6 addresses, Autonomous System numbers, and reverse DNS
delegations.
4.6 Historical resources
Historical resources are Internet resources registered under early
registry policies without formal agreements and include:
* Registrations transferred to APNIC as part of the AUNIC to APNIC
migration;
* Registrations transferred as part of the Early Registration
Transfer (ERX) project;
* Historical APNIC resources.
For more information on historical resources, see:
* Policies for historical Internet resources in the APNIC Whois
Database
http://www.apnic.net/policy/historical-resource-policies.html
5 Goals of address space management 5 Goals of address space management
—————————————– —————————————–
5.1 Goals 5.1 Goals
The goals described here were formulated by the Internet The goals described here were formulated by the Internet
community and reflect the mutual interest of all members of community and reflect the mutual interest of all members of
that community in ensuring that the Internet is able to that community in ensuring that the Internet is able to
function and grow to the maximum extent possible. function and grow to the maximum extent possible.
skipping to change at line 593 skipping to change at line 623
time and will maintain a request tracking system for efficient time and will maintain a request tracking system for efficient
request management. request management.
8.4 General requirements for allocation requests 8.4 General requirements for allocation requests
All requests for address space must be supported by All requests for address space must be supported by
documentation describing: documentation describing:
* the network infrastructure of the organisation making the * the network infrastructure of the organisation making the
request; request;
* any address space currently held by that organisation; * any address space currently held by that organisation (including
* previous assignments made by that organisation; and historical address space);
* previous assignments made by that organisation(including
assignments made from historical address allocations); and
* the intended use for the address space requested. * the intended use for the address space requested.
In addition to this general requirement, more specific In addition to this general requirement, more specific
documentation may also be requested (see Sections 9.2, 9.3, documentation may also be requested (see Sections 9.2, 9.3,
and 9.4). and 9.4).
8.5 Organisations seeking address space from multiple IRs 8.5 Organisations seeking address space from multiple IRs
Organisations must obtain their address space from only one Organisations must obtain their address space from only one
IR at a time. Organisations requesting address space from any IR at a time. Organisations requesting address space from any
skipping to change at line 696 skipping to change at line 728
* signed project contracts indicating the immediate network * signed project contracts indicating the immediate network
requirements to be met by the LIR. requirements to be met by the LIR.
9.3 Criteria for initial allocation 9.3 Criteria for initial allocation
To be eligible to obtain an initial allocation, an LIR must: To be eligible to obtain an initial allocation, an LIR must:
* have used a /24 from their upstream provider or demonstrate * have used a /24 from their upstream provider or demonstrate
an immediate need for a /24; an immediate need for a /24;
* have complied with applicable policies in managing all * have complied with applicable policies in managing all
address space previously allocated to it; address space previously allocated to it (including historical
allocations);
* demonstrate a detailed plan for use of a /23 within a year; * demonstrate a detailed plan for use of a /23 within a year;
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 and sub-allocations from relevant the LIR made assignments and sub-allocations from relevant
past allocations); past allocations, including historical 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 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 a period of less than one year, then they allocation based on a period of less than one year, then 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.
skipping to change at line 749 skipping to change at line 782
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 Address aggregation 9.7 Address aggregation
It is a condition of all allocations, that the allocated It is a condition of all allocations, that the allocated
address space is aggregated by the LIR within a minimum address space is aggregated by the LIR within a minimum
number of route announcements (preferably one). number of route announcements (preferably one).
LIRs must only assign or sub-allocation addresses to LIRs must only assign or sub-allocation addresses to
customers who will be using those addresses in relation to customers who will be using those addresses in relation to
network connectivity services provided by the LIR. 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 the customers specifying that the end-user will hold the
addresses only for so long as the end-user remains a customer addresses only for so long as the end-user remains a customer
of that 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.
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
incomplete. incomplete.
skipping to change at line 789 skipping to change at line 822
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.
9.10 Distribution of the final /8 worth of space in the unallocated
APNIC IPv4 address pool
When the total remaining space in the unallocated APNIC address
pool reaches a threshold of a total of one /8, the following
policies will come into force.
9.10.1 Allocations to LIRs
Each APNIC account holder will be eligible to request and receive a
single allocation from the remaining /8 worth of space, with the
following conditions:
* Each allocation will consist of the minimum IPv4 allocation size;
* The account holder must meet the criteria for receiving an IPv4
allocation specified in one of the following sections of this
policy document:
9.3 Criteria for initial allocation
9.4 Criteria for subsequent allocations
* All APNIC account holders are eligible to receive only one
allocation from the final /8 worth of address space. This applies
to both current and future account holders.
9.10.2 Allocations for future uses
A /16 will be held in reserve for future uses, as yet unforeseen.
If the reserved /16 remains unused by the time the rest of the
remaining /8 worth of space has been allocated, the /16 will be
returned to the APNIC pool for distribution under the policy
described in the Section 9.10.1, “Allocations to LIRs”.
10 LIR address space management 10 LIR address space management
———————————— ————————————
Subject to the following provisions, LIRs may either sub-allocate or Subject to the following provisions, LIRs may either sub-allocate or
assign address space to their customers. 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
 End of changes. 12 change blocks. 
14 lines changed or deleted 81 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/