diff_apnic-086-v007

 apnic-086-v006.txt   apnic-086-v007.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: 006 Version: 007
Date of original publication: 21 December 2001 Date of original publication: 21 December 2001
Date of this version: 13 December 2005 Date of this version: 4 August 2008
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 489 skipping to change at line 489
not connected to the Internet. not connected to the Internet.
6.10 Minimum practical allocations 6.10 Minimum practical allocations
Because the goals of aggregation and conservation conflict, Because the goals of aggregation and conservation conflict,
it is necessary to apply a minimum practical size for address it is necessary to apply a minimum practical size for address
space allocations. This minimum allocation size may be space allocations. This minimum allocation size may be
reviewed from time to time, as technologies and administrative reviewed from time to time, as technologies and administrative
conditions evolve. conditions evolve.
The current minimum practical allocation is a /21 (2,048 The current minimum practical allocation is a /22 (1,024
addresses). addresses).
6.11 Documentation 6.11 Documentation
To properly evaluate requests, IRs must carefully examine all To properly evaluate requests, IRs must carefully examine all
relevant documentation relating to the networks in question. relevant documentation relating to the networks in question.
This documentation may include: This documentation may include:
* network engineering plans; * network engineering plans;
* subnetting plans; * subnetting plans;
skipping to change at line 693 skipping to change at line 693
* receipts for purchase of equipment, * receipts for purchase of equipment,
* purchase orders, or * purchase orders, or
* 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 /23 from their upstream provider or demonstrate * have used a /24 from their upstream provider or demonstrate
an immediate need for a /23; 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;
* demonstrate a detailed plan for use of a /22 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
 End of changes. 5 change blocks. 
6 lines changed or deleted 6 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/