APNIC Home

diff_apnic-089-v002

 apnic-089-v001.txt   apnic-089-v002.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: 001 Version: 002
Date of original publication: 1 July 2002 Date of original publication: 1 July 2002
Date of this version: 1 July 2002 Date of this version: 16 August 2004
Review scheduled: n/a Review scheduled: n/a
Obsoletes: n/a Obsoletes: n/a
Status: Obsolete Status: Obsolete
Comments: n/a Comments: n/a
——————————————————————– ——————————————————————–
IPv6 Address Allocation and Assignment Policy IPv6 Address Allocation and Assignment Policy
June 26 2002
Status of this Memo Status of this Memo
This document was developed through joint discussions among the This document was developed through joint discussions among the
APNIC, ARIN and RIPE communities. APNIC, ARIN and RIPE communities.
Abstract Abstract
This document defines registry policies for the assignment and This document defines registry policies for the assignment and
allocation of globally-unique IPv6 addresses to ISPs and other allocation of globally-unique IPv6 addresses to ISPs and other
skipping to change at line 67 skipping to change at line 66
3.4. Aggregation 3.4. Aggregation
3.5. Conservation 3.5. Conservation
3.6. Fairness 3.6. Fairness
3.7. Minimized Overhead 3.7. Minimized Overhead
3.8. Conflict of goals 3.8. Conflict of goals
4. IPv6 Policy Principles 4. IPv6 Policy Principles
4.1. Address space not to be considered property 4.1. Address space not to be considered property
4.2. Routability not guaranteed 4.2. Routability not guaranteed
4.3. Minimum Allocation 4.3. Minimum Allocation
4.4. Consideration of IPv4 Infrastructure 4.4. Consideration of IPv4 infrastructure
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
5.1.2. Initial allocation size 5.1.2. Minimum initial allocation size
5.1.3. Larger initial allocations
5.2. Subsequent allocation 5.2. Subsequent allocation
5.2.1. Subsequent allocation criteria 5.2.1. Subsequent allocation criteria
5.2.2. Applied HD-Ratio 5.2.2. Applied HD-Ratio
5.2.3. Subsequent Allocation Size 5.2.3. Subsequent Allocation Size
5.3. LIR-to-ISP allocation 5.3. LIR-to-ISP allocation
5.4. Assignment 5.4. Assignment
5.4.1. Assignment address space size 5.4.1. Assignment address space size
5.4.2. Assignment of multiple /48s to a single end site 5.4.2. Assignment of multiple /48s to a single end site
5.4.3. Assignment to operator’s infrastructure. 5.4.3. Assignment to operator’s infrastructure.
5.5. Registration 5.5. Registration
skipping to change at line 104 skipping to change at line 104
8.4. Acknowledgment 8.4. Acknowledgment
1. Introduction 1. Introduction
1.1. Overview 1.1. Overview
This document describes policies for the allocation and assignment of This document describes policies for the allocation and assignment of
globally-unique Internet Protocol Version 6 (IPv6) address space. It globally-unique Internet Protocol Version 6 (IPv6) address space. It
updates and obsoletes the existing Provisional IPv6 Policies in updates and obsoletes the existing Provisional IPv6 Policies in
effect since 1999 [RIRv6-Policies]. Policies described in this effect since 1999 [RIRv6-Policies]. Policies described in this
document are are intended to be adopted by each registry. However, document are intended to be adopted by each registry. However,
adoption of this document does not preclude local variations in each adoption of this document does not preclude local variations in each
region or area. region or area.
[RFC2373, RFC2373bis] designate 2000::/3 to be global unicast address [RFC2373, RFC2373bis] designate 2000::/3 to be global unicast address
space that IANA may allocate to the RIRs. In accordance with space that IANA may allocate to the RIRs. In accordance with
[RFC2928, RFC2373bis, IAB-Request], IANA has allocated initial ranges [RFC2928, RFC2373bis, IAB-Request], IANA has allocated initial ranges
of global unicast IPv6 address space from the 2001::/16 address block of global unicast IPv6 address space from the 2001::/16 address block
to the existing RIRs. This document concerns the initial and to the existing RIRs. This document concerns the initial and
subsequent allocations of the 2000::/3 unicast address space, for subsequent allocations of the 2000::/3 unicast address space, for
which RIRs formulate allocation and assignment policies. Because end which RIRs formulate allocation and assignment policies. Because end
skipping to change at line 371 skipping to change at line 371
However, RIRs must apply procedures that reduce the possibility of However, RIRs must apply procedures that reduce the possibility of
fragmented address space which may lead to a loss of routability. fragmented address space which may lead to a loss of routability.
4.3. Minimum Allocation 4.3. Minimum Allocation
RIRs will apply a minimum size for IPv6 allocations, to facilitate RIRs will apply a minimum size for IPv6 allocations, to facilitate
prefix-based filtering. prefix-based filtering.
The minimum allocation size for IPv6 address space is /32. The minimum allocation size for IPv6 address space is /32.
4.4. Consideration of IPv4 Infrastructure 4.4. Consideration of IPv4 infrastructure
Where an existing IPv4 service provider requests IPv6 space for Subject to section 5.1.3, existing IPv4 networks may be considered in
eventual transition of existing services to IPv6, the number of determining the initial IPv6 allocation size.
present IPv4 customers may be used to justify a larger request than
would be justified if based solely on the IPv6 infrastructure.
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 assign /48s, by advertising that connectivity through its will assign /48s, by advertising that connectivity through its
single aggregated address allocation; and single aggregated address allocation; and
d) have a plan for making at least 200 /48 assignments to other d) have a plan for making at least 200 /48 assignments to other
organizations within two years. organizations within two years.
5.1.2. Initial allocation size Private networks (those not connected to the public Internet) may
also be eligible for an IPv6 address space allocation provided they
meet equivalent criteria to those listed above.
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.
Organizations may qualify for an initial allocation greater than /32 5.1.3. Larger initial allocations
by submitting documentation that reasonably justifies the request.
If so, the allocation size will be based on the number of existing Initial allocations larger than /32 may be justified if:
users and the extent of the organization’s infrastructure.
a) The organization provides comprehensive documentation of
planned IPv6 infrastructure which would require a larger allocation; or
b) The organization provides comprehensive documentation of all of the
following:
– its existing IPv4 infrastructure and customer base,
– its intention to provide its existing IPv4 services via IPv6, and
– 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
address requirement, in accordance with the HD-Ratio based 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
skipping to change at line 515 skipping to change at line 530
RIR/NIR database. RIR/NIR database.
RIR/NIRs will use registered data to calculate the HD-Ratio at the RIR/NIRs will use registered data to calculate the HD-Ratio at the
time of application for subsequent allocation and to check for time of application for subsequent allocation and to check for
changes in assignments over time. changes in assignments over time.
IRs shall maintain systems and practices that protect the security of IRs shall maintain systems and practices that protect the security of
personal and commercial information that is used in request personal and commercial information that is used in request
evaluation, but which is not required for public registration. evaluation, but which is not required for public registration.
Organizations that receive an allocation from APNIC can choose whether
or not their customer assignment registrations should be publicly
available. If the organization does not indicate a choice, or it chooses
to hide its customer assignment registrations, then those records will
not be visible in the public whois database. Whois queries on these
records will return details of the allocation.
5.6. Reverse lookup 5.6. Reverse lookup
When an RIR/NIR delegates IPv6 address space to an organization, it When an RIR/NIR delegates IPv6 address space to an organization, it
also delegates the responsibility to manage the reverse lookup zone also delegates the responsibility to manage the reverse lookup zone
that corresponds to the allocated IPv6 address space. Each that corresponds to the allocated IPv6 address space. Each
organization should properly manage its reverse lookup zone. When organization should properly manage its reverse lookup zone. When
making an address assignment, the organization must delegate to an making an address assignment, the organization must delegate to an
assignee organization, upon request, the responsibility to manage the assignee organization, upon request, the responsibility to manage the
reverse lookup zone that corresponds to the assigned address. reverse lookup zone that corresponds to the assigned address.
 End of changes. 11 change blocks. 
23 lines changed or deleted 46 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/