APNIC Home

diff-apnic-127-v007

 apnic-resource-policies.txt   apnic-resource-policies-v007-draft.txt 
———————————————————————– ———————————————————————–
APNIC Document identity APNIC Document identity
Title: APNIC Internet Number Resource Policies Title: APNIC Internet Number Resource Policies
Short title: apnic-resource-policies Short title: apnic-resource-policies
Document ref: APNIC-127 Document ref: APNIC-127
Version: 006 Version: 007
Date of original publication: 5 March 2015 Date of original publication: 5 March 2015
Date of this version: 09 May 2019 Date of this version: 2 July 2019
Review scheduled: n/a Review scheduled: n/a
Obsoletes: apnic-127-v005 Obsoletes: apnic-127-v006
Status: Active Status: Draft
Comments: Implements prop-125 and prop-127 Comments: Implements prop-128 and prop-129
———————————————————————- ———————————————————————-
Table of Contents Table of Contents
—————– —————–
Part 1: Policy Environment Part 1: Policy Environment
————————– ————————–
1.0. Introduction 1.0. Introduction
skipping to change at line 1596 skipping to change at line 1596
6.1. Minimum and maximum IPv4 delegations 6.1. Minimum and maximum IPv4 delegations
—————————————– —————————————–
The current minimum delegation size for IPv4 is a /24 (256 The current minimum delegation size for IPv4 is a /24 (256
addresses). addresses).
Since Thursday, 28 February 2019, each APNIC account holder Since Thursday, 28 February 2019, each APNIC account holder
is only eligible to receive IPv4 address delegations totalling is only eligible to receive IPv4 address delegations totalling
a maximum /23 from the APNIC 103/8 IPv4 address pool. a maximum /23 from the APNIC 103/8 IPv4 address pool.
On Tuesday, 27 May 2014, each APNIC account holder became eligible On Tuesday, 2 July 2019, non-103/8 resources waiting list was abolished
to receive additional delegations up to a maximum of /22 address and only new APNIC account holders are eligible to receive IPv4 delegation
space from the APNIC non-103/8 Recovered IPv4 address pool. from the remaining IPv4 pool.
Note: Resources may not always be available from the recovered
(non-103/8) address pool. APNIC has created a waiting list for those
IPv4 requests that cannot be fulfilled. These requests are fulfilled
in order of request, as space becomes available.
To receive delegations from either of these pools, they must
demonstrate their eligibility by meeting the criteria specified
below.
6.1.1. Additional allocation rounds Note: A waiting list will be created once APNIC runs out of all IPv4
———————————– addresses. Any requests received from the new APNIC account holders for IPv4
Recovered 103/8 address space returned to APNIC will be added to resources will be put on this waiting list on a first come first served.
the 103/8 IPv4 address pool. Recovered non-103/8 address space APNIC will maintain one IPv4 pool for all recovered as well as IANA delegated
or addresses allocated to APNIC from the ‘IANA Recovered IPv4 address space and this pool will be used to provide IPv4 resources to the
Pool’ will be added to the non-103/8 IPv4 address pool. waiting list requests.
If address space in this pool becomes sufficient to delegate a To receive delegations from this pool, they must demonstrate their
further /22 to each APNIC account holder, additional delegation eligibility by meeting the criteria specified below.
rounds will be announced.
6.2. IPv4 request criteria 6.2. IPv4 request criteria
————————– ————————–
To qualify for an IPv4 address delegation from APNIC, requestors To qualify for an IPv4 address delegation from APNIC, requestors
must demonstrate their eligibility under one of the following four must demonstrate their eligibility under one of the following four
criteria; criteria;
– IPv4 for LIRs – IPv4 for LIRs
– IPv4 for multihoming – IPv4 for multihoming
– IPv4 for critical infrastructure – IPv4 for critical infrastructure
– IPv4 for Internet Exchange Points – IPv4 for Internet Exchange Points
skipping to change at line 2213 skipping to change at line 2203
Part 4: ASN Policy Part 4: ASN Policy
—————— ——————
12.0. ASN assignments 12.0. ASN assignments
——————— ———————
12.1. Evaluation of eligibility 12.1. Evaluation of eligibility
——————————- ——————————-
An organization is eligible for an ASN assignment if: An organization is eligible for an ASN assignment if:
– it is currently multihomed, or – it is currently multihomed, or
– it holds previously-allocated provider independent address space – has the need to interconnect with other AS.
and intends to multihome in the future.
An organization will also be eligible if it can demonstrate that it An organization will also be eligible if it can demonstrate that it
will meet the above criteria upon receiving an ASN (or within a will meet the above criteria upon receiving an ASN (or within a
reasonably short time thereafter). reasonably short time thereafter).
Requests for ASNs under these criteria will be evaluated using the Requests for ASNs under these criteria will be evaluated using the
guidelines described in RFC1930 ‘Guidelines for the creation, guidelines described in RFC1930 ‘Guidelines for the creation,
selection and registration of an Autonomous System’ (AS). selection and registration of an Autonomous System’ (AS).
12.2. Requesting an ASN 12.2. Requesting an ASN
 End of changes. 7 change blocks. 
28 lines changed or deleted 17 lines changed or added
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/