|
apnic-127-v003.txt |
|
apnic-resource-policies.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: 003 |
|
Version: 004 |
|
|
Date of original publication: 5 March 2015 |
|
Date of original publication: 5 March 2015 |
|
|
|
Date of this version: 10 February 2016 |
|
Date of this version: 4 August 2017 |
|
|
Review scheduled: n/a |
|
Review scheduled: n/a |
|
|
|
Obsoletes: apnic-127-v002 |
|
Obsoletes: apnic-127-v003 |
|
|
Status: Active |
|
Status: Draft |
|
|
Comments: Implements prop-113 and prop-114. |
|
Comments: Implements prop-117. |
|
|
———————————————————————- |
|
———————————————————————- |
|
|
|
|
|
|
|
Table of Contents |
|
Table of Contents |
|
|
—————– |
|
—————– |
|
|
|
|
|
|
|
Part 1: Policy Environment |
|
Part 1: Policy Environment |
|
|
————————– |
|
————————– |
|
|
|
|
|
|
|
1.0. Introduction |
|
1.0. Introduction |
|
|
1.1. Scope |
|
1.1. Scope |
|
|
|
|
|
|
|
skipping to change at line 451 ¶ |
|
skipping to change at line 451 ¶ |
|
|
|
|
|
|
|
2.3.1. Autonomous System Number (ASN) |
|
2.3.1. Autonomous System Number (ASN) |
|
|
————————————- |
|
————————————- |
|
|
An Autonomous System Number (ASN) is a unique two- or four-byte |
|
An Autonomous System Number (ASN) is a unique two- or four-byte |
|
|
number associated with an AS. The ASN is used as an identifier |
|
number associated with an AS. The ASN is used as an identifier |
|
|
to allow the AS to exchange dynamic routing information with |
|
to allow the AS to exchange dynamic routing information with |
|
|
other Autonomous Systems. |
|
other Autonomous Systems. |
|
|
|
|
|
|
|
2.4. Multihomed |
|
2.4. Multihomed |
|
|
————— |
|
————— |
|
|
|
Multihoming is a way of connecting an organization�??s network to the |
|
Multihoming is a way of connecting an organization���s network to the |
|
|
public Internet through more than one AS. |
|
public Internet through more than one AS. |
|
|
|
|
|
|
|
2.5. Internet resources |
|
2.5. Internet resources |
|
|
———————– |
|
———————– |
|
|
Internet resources are public IPv4 and IPv6 address numbers, |
|
Internet resources are public IPv4 and IPv6 address numbers, |
|
|
Autonomous System Numbers, and reverse DNS delegations. |
|
Autonomous System Numbers, and reverse DNS delegations. |
|
|
|
|
|
|
|
2.5.1. Current resources |
|
2.5.1. Current resources |
|
|
———————— |
|
———————— |
|
|
Current resources are Internet resources registered by APNIC |
|
Current resources are Internet resources registered by APNIC |
|
|
|
|
|
|
|
skipping to change at line 1594 ¶ |
|
skipping to change at line 1594 ¶ |
|
|
On Tuesday, 27 May 2014, each APNIC account holder became eligible |
|
On Tuesday, 27 May 2014, each APNIC account holder became eligible |
|
|
to receive additional delegations up to a maximum of /22 address |
|
to receive additional delegations up to a maximum of /22 address |
|
|
space from the APNIC non-103/8 IPv4 address pool. |
|
space from the APNIC non-103/8 IPv4 address pool. |
|
|
|
|
|
|
|
To receive delegations from either of these pools, they must |
|
To receive delegations from either of these pools, they must |
|
|
demonstrate their eligibility by meeting the criteria specified |
|
demonstrate their eligibility by meeting the criteria specified |
|
|
below. |
|
below. |
|
|
|
|
|
|
|
6.1.1. Additional allocation rounds |
|
6.1.1. Additional allocation rounds |
|
|
———————————– |
|
———————————– |
|
|
|
Address space returned to APNIC, or allocated to APNIC from the |
|
Recovered 103/8 address space returned to APNIC will be added to |
|
|
‘IANA Recovered IPv4 Pool’ will be added to the non-103/8 IPv4 |
|
the 103/8 IPv4 address pool. Recovered non-103/8 address space |
|
|
address pool. If address space in this pool becomes sufficient |
|
or addresses allocated to APNIC from the ‘IANA Recovered IPv4 |
|
|
to delegate a further /22 to each APNIC account holder, |
|
Pool’ will be added to the non-103/8 IPv4 address pool. |
|
|
additional delegation rounds will be announced. |
|
|
|
|
|
|
If address space in this pool becomes sufficient to delegate a |
|
|
|
|
further /22 to each APNIC account holder, additional delegation |
|
|
|
|
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 |
|
|
|
|
|
|
| End of changes. 5 change blocks. |
|
11 lines changed or deleted |
|
14 lines changed or added |
|
|
This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |
