|
apnic-089-v005.txt |
|
apnic-089-v006.txt |
|
|
|
|
|
|
|
|
——————————————————————- |
|
——————————————————————- |
|
|
APNIC Document identity |
|
APNIC Document identity |
|
|
|
|
|
|
|
Title: IPv6 Address Allocation and Assignment Policy |
|
Title: IPv6 Address Allocation and Assignment Policy |
|
|
|
|
|
|
|
Short title: ipv6-address-policy |
|
Short title: ipv6-address-policy |
|
|
Document ref: APNIC-089 |
|
Document ref: APNIC-089 |
|
|
|
Version: 005 |
|
Version: 006 |
|
|
Date of original publication: 1 July 2002 |
|
Date of original publication: 1 July 2002 |
|
|
|
Date of this version: 19 March 2007 |
|
Date of this version: 4 August 2008 |
|
|
Review scheduled: n/a |
|
Review scheduled: n/a |
|
|
Obsoletes: Previous versions |
|
Obsoletes: Previous versions |
|
|
Status: Obsolete |
|
Status: Obsolete |
|
|
Comments: n/a |
|
Comments: n/a |
|
|
——————————————————————– |
|
——————————————————————– |
|
|
|
|
|
|
|
|
IPv6 Address Allocation and Assignment Policy |
|
IPv6 Address Allocation and Assignment Policy |
|
|
|
|
|
|
|
Status of this Memo |
|
Status of this Memo |
|
|
|
|
|
|
|
This document was initially developed through joint discussions |
|
This document was initially developed through joint discussions |
|
|
among the APNIC, ARIN and RIPE communities. The document also |
|
among the APNIC, ARIN and RIPE communities. The document also |
|
|
incorporates APNIC-specific policies. |
|
incorporates APNIC-specific policies. |
|
|
|
|
|
|
|
Abstract |
|
Abstract |
|
|
|
|
|
|
|
This document defines registry policies for the assignment and |
|
This document defines registry policies for the assignment and |
|
|
|
|
|
|
|
skipping to change at line 408 |
|
skipping to change at line 409 |
|
|
|
|
|
|
|
5. Policies for allocations and assignments |
|
5. Policies for allocations and assignments |
|
|
|
|
|
|
|
5.1. Initial allocation |
|
5.1. Initial allocation |
|
|
|
|
|
|
|
5.1.1. Initial allocation criteria |
|
5.1.1. Initial allocation criteria |
|
|
|
|
|
|
|
To qualify for an initial allocation of IPv6 address space, an |
|
To qualify for an initial allocation of IPv6 address space, an |
|
|
organization must: |
|
organization must: |
|
|
|
|
|
|
|
|
a) be an LIR; |
|
a) be an LIR |
|
|
b) not be an end site; |
|
b) not be an end site |
|
|
c) plan to provide IPv6 connectivity to organizations to which it |
|
c) plan to provide IPv6 connectivity to organizations to which it |
|
|
will make assignments, by advertising that connectivity through |
|
will make assignments, by advertising that connectivity through |
|
|
|
its single aggregated address allocation; and |
|
its single aggregated address allocation |
|
|
d) have a plan for making at least 200 assignments to other |
|
d) meet one of the two following criteria: |
|
|
organizations within two years. |
|
– have a plan for making at least 200 assignments to other |
|
|
|
|
organizations within two years OR |
|
|
|
|
– be an existing LIR with IPv4 allocations from APNIC or an NIR |
|
|
|
|
that will make IPv6 assignments or sub-allocations to other |
|
|
|
|
organizations and announce the allocation in the inter-domain |
|
|
|
|
routing system within two years |
|
|
|
|
|
|
|
Private networks (those not connected to the public Internet) may |
|
Private networks (those not connected to the public Internet) may |
|
|
also be eligible for an IPv6 address space allocation provided they |
|
also be eligible for an IPv6 address space allocation provided they |
|
|
meet equivalent criteria to those listed above. |
|
meet equivalent criteria to those listed above. |
|
|
|
|
|
|
|
5.1.2. Minimum initial allocation size |
|
5.1.2. Minimum initial allocation size |
|
|
|
|
|
|
|
Organizations that meet the initial allocation criteria are eligible |
|
Organizations that meet the initial allocation criteria are eligible |
|
|
to receive a minimum allocation of /32. |
|
to receive a minimum allocation of /32. |
|
|
|
|
|
|
|
5.1.3. Larger initial allocations |
|
5.1.3. Larger initial allocations |
|
|
|
|
|
|
|
Initial allocations larger than /32 may be justified if: |
|
Initial allocations larger than /32 may be justified if: |
|
|
|
|
|
|
|
a) The organization provides comprehensive documentation of |
|
a) The organization provides comprehensive documentation of |
|
|
|
planned IPv6 infrastructure which would require a larger allocation; or |
|
planned IPv6 infrastructure which would require a larger |
|
|
|
|
allocation; or |
|
|
|
|
|
|
|
|
b) The organization provides comprehensive documentation of all of the |
|
b) The organization provides comprehensive documentation of all of |
|
|
following: |
|
the following: |
|
|
– its existing IPv4 infrastructure and customer base, |
|
– its existing IPv4 infrastructure and customer base, |
|
|
– its intention to provide its existing IPv4 services via IPv6, and |
|
– its intention to provide its existing IPv4 services via |
|
|
– its intention to move some of its existing IPv4 customers to IPv6 |
|
IPv6, and |
|
|
within two years. |
|
– its intention to move some of its existing IPv4 customers to |
|
|
|
|
IPv6 within two years. |
|
|
|
|
|
|
|
|
In either case, an allocation will be made which fulfills the calculated |
|
In either case, an allocation will be made which fulfills the |
|
|
address requirement, in accordance with the HD-Ratio based utilization |
|
calculated address requirement, in accordance with the HD-Ratio based |
|
|
policy. |
|
utilization policy. |
|
|
|
|
|
|
|
5.2. Subsequent allocation |
|
5.2. Subsequent allocation |
|
|
|
|
|
|
|
Organizations that hold an existing IPv6 allocation may receive a |
|
Organizations that hold an existing IPv6 allocation may receive a |
|
|
subsequent allocation in accordance with the following policies. |
|
subsequent allocation in accordance with the following policies. |
|
|
|
|
|
|
|
5.2.1. Subsequent allocation criteria |
|
5.2.1. Subsequent allocation criteria |
|
|
|
|
|
|
|
Subsequent allocation will be provided when an organization (ISP/LIR) |
|
Subsequent allocation will be provided when an organization (ISP/LIR) |
|
|
satisfies the evaluation threshold of past address utilization in |
|
satisfies the evaluation threshold of past address utilization in |
|
|
|
|
|
|
End of changes. 9 change blocks. |
|
18 lines changed or deleted |
|
26 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/ |