APNIC Home

diff_apnic-089-v003

 apnic-089-v002.txt   apnic-089-v003.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: 002 Version: 003
Date of original publication: 1 July 2002 Date of original publication: 1 July 2002
Date of this version: 16 August 2004 Date of this version: 26 May 2005
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
Status of this Memo Status of this Memo
This document was developed through joint discussions among the This document was initially developed through joint discussions
APNIC, ARIN and RIPE communities. among the APNIC, ARIN and RIPE communities. The document also
incorporates APNIC-specific policies.
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
organizations. This document obsoletes the “Provisional IPv6 organizations. This document obsoletes the “Provisional IPv6
assignment and allocation policy document”. assignment and allocation policy document”.
This document was developed jointly by the communities of APNIC, This document was developed jointly by the communities of APNIC,
ARIN, and RIPE. ARIN, and RIPE.
Contents Contents
Status of this Memo Status of this Memo
1. Introduction 1. Introduction
1.1. Overview
1.1. Overview
2. Definitions 2. Definitions
2.1. Internet Registry (IR)
2.2. Regional Internet Registry (RIR) 2.1. Internet Registry (IR)
2.3. National Internet Registry (NIR) 2.2. Regional Internet Registry (RIR)
2.4. Local Internet Registry (LIR) 2.3. National Internet Registry (NIR)
2.5. Allocate 2.4. Local Internet Registry (LIR)
2.6. Assign 2.5. Allocate
2.7. Utilization 2.6. Assign
2.8. HD-Ratio 2.7. Utilization
2.9. End site 2.8. HD-Ratio
2.9. End site
2.10. Internet Exchange Point (IXP)
3. Goals of IPv6 address space management 3. Goals of IPv6 address space management
3.1. Goals
3.2. Uniqueness 3.1. Goals
3.3. Registration 3.2. Uniqueness
3.4. Aggregation 3.3. Registration
3.5. Conservation 3.4. Aggregation
3.6. Fairness 3.5. Conservation
3.7. Minimized Overhead 3.6. Fairness
3.8. Conflict of goals 3.7. Minimized Overhead
3.8. Conflict of goals
4. IPv6 Policy Principles 4. IPv6 Policy Principles
4.1. Address space not to be considered property
4.2. Routability not guaranteed 4.1. Address space not to be considered property
4.3. Minimum Allocation 4.2. Routability not guaranteed
4.4. Consideration of IPv4 infrastructure 4.3. Minimum Allocation
4.4. Consideration of IPv4 infrastructure
5. Policies for allocations and assignments 5. Policies for allocations and assignments
5.1. Initial allocation
5.1.1. Initial allocation criteria 5.1. Initial allocation
5.1.2. Minimum initial allocation size
5.1.3. Larger initial allocations 5.1.1. Initial allocation criteria
5.2. Subsequent allocation 5.1.2. Minimum initial allocation size
5.2.1. Subsequent allocation criteria 5.1.3. Larger initial allocations
5.2.2. Applied HD-Ratio
5.2.3. Subsequent Allocation Size 5.2. Subsequent allocation
5.3. LIR-to-ISP allocation
5.4. Assignment 5.2.1. Subsequent allocation criteria
5.4.1. Assignment address space size 5.2.2. Applied HD-Ratio
5.4.2. Assignment of multiple /48s to a single end site 5.2.3. Subsequent Allocation Size
5.4.3. Assignment to operator’s infrastructure.
5.5. Registration 5.3. LIR-to-ISP allocation
5.6. Reverse lookup
5.7. Existing IPv6 address space holders 5.4. Assignment
5.4.1. Assignment address space size
5.4.2. Assignment of multiple /48s to a single end site
5.4.3. Assignment to operator’s infrastructure
5.5. Registration
5.6. Reverse lookup
5.7. Existing IPv6 address space holders
5.8. Assignments to IXPs and critical infrastructure
5.8.1. Internet Exchange Points
5.8.2. Critical infrastructure
6. References 6. References
7. Appendix A: HD-Ratio 7. Appendix A: HD-Ratio
8. Appendix B: Background information 8. Appendix B: Background information
8.1. Background
8.2. Why a joint policy 8.1. Background
8.3. The size of IPv6’s address space 8.2. Why a joint policy
8.4. Acknowledgment 8.3. The size of IPv6’s address space
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 intended to be adopted by each registry. However, document are intended to be adopted by each registry. However,
skipping to change at line 243 skipping to change at line 265
An end site is defined as an end user (subscriber) who has a business An end site is defined as an end user (subscriber) who has a business
relationship with a service provider that involves: relationship with a service provider that involves:
– that service provider assigning address space to the end user – that service provider assigning address space to the end user
– that service provider providing transit service for the end user – that service provider providing transit service for the end user
to other sites to other sites
– that service provider carrying the end user’s traffic. – that service provider carrying the end user’s traffic.
– that service provider advertising an aggregate prefix route that – that service provider advertising an aggregate prefix route that
contains the end user’s assignment contains the end user’s assignment
2.10. Internet Exchange Point (IXP)
An Internet Exchange Point (IX or IXP) is a layer 1 and layer 2 network
structure that interconnects three or more Autonomous Systems (AS) for
the purpose of Internet traffic interchange.
3. Goals of IPv6 address space management 3. Goals of IPv6 address space management
3.1. Goals 3.1. Goals
IPv6 address space is a public resource that must be managed in a IPv6 address space is a public resource that must be managed in a
prudent manner with regards to the long-term interests of the prudent manner with regards to the long-term interests of the
internet. Responsible address space management involves balancing a internet. Responsible address space management involves balancing a
set of sometimes competing goals. The following are the goals set of sometimes competing goals. The following are the goals
relevant to IPv6 address policy. relevant to IPv6 address policy.
skipping to change at line 559 skipping to change at line 587
Organizations that received /35 IPv6 allocations under the previous Organizations that received /35 IPv6 allocations under the previous
IPv6 address policy [RIRv6-Policies] are immediately entitled to have IPv6 address policy [RIRv6-Policies] are immediately entitled to have
their allocation expanded to a /32 address block, without providing their allocation expanded to a /32 address block, without providing
justification, so long as they satisfy the criteria in Section 5.1.1. justification, so long as they satisfy the criteria in Section 5.1.1.
The /32 address block will contain the already allocated smaller The /32 address block will contain the already allocated smaller
address block (one or multiple /35 address blocks in many cases) that address block (one or multiple /35 address blocks in many cases) that
was already reserved by the RIR for a subsequent allocation to the was already reserved by the RIR for a subsequent allocation to the
organization. Requests for additional space beyond the minimum /32 organization. Requests for additional space beyond the minimum /32
size will be evaluated as discussed elsewhere in the document. size will be evaluated as discussed elsewhere in the document.
5.8. Assignments to IXPs and critical infrastructure
5.8.1 Internet Exchange Points
Internet Exchange Points are eligible to receive a portable assignment
from APNIC to be used exclusively to connect the IXP participant devices
to the Exchange Point.
The minimum assignment made under these terms is /48.
Global routability of the portable assignment is left to the discretion
of the IXP and its participants.
5.8.2 Critical infrastructure
The following critical infrastructure networks, if operating in the Asia
Pacific region, are eligible to receive a portable assignment:
– root domain name system (DNS) server;
– global top level domain (gTLD) nameservers;
– country code TLD (ccTLDs) nameservers;
– IANA;
– Regional Internet Registry (RIRs); and
– National Internet Registry (NIRs).
Assignments to critical infrastructure are available only to the actual
operators of the network infrastructure performing such functions. Registrar
organisations which do not actually host the network housing the registry
infrastructure, will not be eligible for an assignment under this policy.
The minimum assignment made under these terms is /32.
Exchanges made under this policy remain subject to the address space license
policy.
6. References 6. References
[RFC1715] “The H Ratio for Address Assignment Efficiency”, C. [RFC1715] “The H Ratio for Address Assignment Efficiency”, C.
Huitema. November 1994, RFC 1715. Huitema. November 1994, RFC 1715.
[IAB-Request] “Email from IAB to IANA“, [IAB-Request] “Email from IAB to IANA“,
http://www.iab.org/iab/DOCUMENTS/IPv6addressspace.txt. http://www.iab.org/iab/DOCUMENTS/IPv6addressspace.txt.
[RFC2373] “IP Version 6 Addressing Architecture”, R. Hinden, S. [RFC2373] “IP Version 6 Addressing Architecture”, R. Hinden, S.
Deering. July 1998, RFC 2373. Deering. July 1998, RFC 2373.
 End of changes. 12 change blocks. 
47 lines changed or deleted 110 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/