|
apnic-127-v002.txt |
|
apnic-127-v003.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: 002 |
|
Version: 003 |
|
|
Date of original publication: 5 March 2015 |
|
Date of original publication: 5 March 2015 |
|
|
|
Date of this version: 10 November 2015 |
|
Date of this version: 10 February 2016 |
|
|
Review scheduled: n/a |
|
Review scheduled: n/a |
|
|
|
Obsoletes: apnic-127-v001 |
|
Obsoletes: apnic-127-v002 |
|
|
Status: Obsolete |
|
Status: Obsolete |
|
|
|
Comments: Reduces duplication and contradictions |
|
Comments: Implements prop-113 and prop-114. |
|
|
in combined resource policies. |
|
|
|
|
Corrects typographical errors. |
|
|
|
|
———————————————————————- |
|
———————————————————————- |
|
|
|
|
|
|
|
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 1626 ¶ |
|
skipping to change at line 1624 ¶ |
|
|
– Have used a /24 from their upstream provider or demonstrate an |
|
– Have used a /24 from their upstream provider or demonstrate an |
|
|
immediate need for a /24, |
|
immediate need for a /24, |
|
|
– Have complied with applicable policies in managing all address |
|
– Have complied with applicable policies in managing all address |
|
|
space previously delegated to it (including Historical |
|
space previously delegated to it (including Historical |
|
|
delegations), and |
|
delegations), and |
|
|
– Demonstrate a detailed plan for use of at least a /23 within |
|
– Demonstrate a detailed plan for use of at least a /23 within |
|
|
a year |
|
a year |
|
|
|
|
|
|
|
6.2.2. IPv4 for multihoming |
|
6.2.2. IPv4 for multihoming |
|
|
————————— |
|
————————— |
|
|
|
An organization is eligible if it is currently multihomed with |
|
An organization is eligible to receive an IPv4 delegation if: |
|
|
provider-based addresses, or demonstrates a plan to multihome |
|
|
|
|
within one month. |
|
– it is currently multihomed, or |
|
|
|
|
– it is currently using at least a /24 from its upstream |
|
|
|
|
provider and intends to be multihomed, or |
|
|
|
|
– it intends to be multihomed, and advertise the prefixes within |
|
|
|
|
6 months |
|
|
|
|
|
|
|
Organizations requesting a delegation under these terms must |
|
Organizations requesting a delegation under these terms must |
|
|
demonstrate that they are able to use 25% of the requested |
|
demonstrate that they are able to use 25% of the requested |
|
|
addresses immediately and 50% within one year. |
|
addresses immediately and 50% within one year. |
|
|
|
|
|
|
|
6.2.3. IPv4 for critical infrastructure |
|
6.2.3. IPv4 for critical infrastructure |
|
|
————————————— |
|
————————————— |
|
|
The following critical infrastructure networks, if operating in |
|
The following critical infrastructure networks, if operating in |
|
|
the Asia Pacific region, are eligible to receive a delegation: |
|
the Asia Pacific region, are eligible to receive a delegation: |
|
|
|
|
|
|
|
|
|
|
|
|
skipping to change at line 2160 ¶ |
|
skipping to change at line 2162 ¶ |
|
|
any allocations to be invalid and will require that they be |
|
any allocations to be invalid and will require that they be |
|
|
returned. |
|
returned. |
|
|
|
|
|
|
|
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 it: |
|
An organization is eligible for an ASN assignment if: |
|
|
1. is multihomed; and |
|
– it is currently multihomed, or |
|
|
2. has a single, clearly defined routing policy that is different |
|
– it holds previously-allocated provider independent address space |
|
|
from its providers’ routing policies. |
|
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. |
|
14 lines changed or deleted |
|
16 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/ |