APNIC Home

diff_apnic-089-v012

 apnic-089-v011.txt   apnic-089-v012.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: 011 Version: 012
Date of original publication: 1 July 2002 Date of original publication: 1 July 2002
Date of this version: 19 August 2012 Date of this version: 18 February 2013
Review scheduled: n/a Review scheduled: n/a
Obsoletes: apnic-089-v010 Obsoletes: apnic-089-v011
Status: Active Status: Obsolete
Comments: Implementation of prop-102 Comments: Obsoleted by apnic-127
——————————————————————– ——————————————————————–
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 developed since that time. incorporates APNIC-specific policies developed since that time.
skipping to change at line 111 skipping to change at line 111
5.7 Reverse lookup 5.7 Reverse lookup
5.8 Existing IPv6 address space holders 5.8 Existing IPv6 address space holders
5.9 Portable assignments 5.9 Portable assignments
5.9.1 Small multihoming assignments 5.9.1 Small multihoming assignments
5.9.2 Internet Exchange Points 5.9.2 Internet Exchange Points
5.9.3 Critical infrastructure 5.9.3 Critical infrastructure
5.9.4 Provider Independent assignment
5.9.4.1 Initial assignment
5.9.4.2 Subsequent assignment
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.1 Background
8.2 Why a joint policy 8.2 Why a joint policy
8.3 The size of IPv6’s address space 8.3 The size of IPv6’s address space
skipping to change at line 654 skipping to change at line 657
address blocks in many cases) that was already reserved by the RIR address blocks in many cases) that was already reserved by the RIR
for a subsequent allocation to the organization. Requests for for a subsequent allocation to the organization. Requests for
additional space beyond the minimum /32 size will be evaluated as additional space beyond the minimum /32 size will be evaluated as
discussed elsewhere in the document. discussed elsewhere in the document.
5.9 Portable assignments 5.9 Portable assignments
5.9.1 Small multihoming assignments 5.9.1 Small multihoming assignments
An organization is eligible to receive a portable assignment from An organization is eligible to receive a portable assignment from
APNIC if it is currently multihomed or plans to be multihomed APNIC if it is currently, or plans to be, multihomed.
within three months.
An organization is considered to be multihomed if its network An organization is considered to be multihomed if its network
receives full-time connectivity from more than one ISP and has one receives full-time connectivity from more than one ISP and has one
or more routing prefixes announced by at least two of its ISPs. or more routing prefixes announced by at least two of its ISPs.
The minimum assignment made under these terms is /48. The minimum assignment made under these terms is /48.
Address space assigned under these terms and not used for
multihoming three months after assignment by APNIC will be
reclaimed.
5.9.2 Internet Exchange Points 5.9.2 Internet Exchange Points
Internet Exchange Points are eligible to receive a portable Internet Exchange Points are eligible to receive a portable
assignment from APNIC to be used exclusively to connect the IXP assignment from APNIC to be used exclusively to connect the IXP
participant devices to the Exchange Point. participant devices to the Exchange Point.
The minimum assignment made under these terms is /48. The minimum assignment made under these terms is /48.
Global routability of the portable assignment is left to the Global routability of the portable assignment is left to the
discretion of the IXP and its participants. discretion of the IXP and its participants.
skipping to change at line 702 skipping to change at line 700
actual operators of the network infrastructure performing such actual operators of the network infrastructure performing such
functions. Registrar organizations which do not actually host the functions. Registrar organizations which do not actually host the
network housing the registry infrastructure, will not be eligible network housing the registry infrastructure, will not be eligible
for an assignment under this policy. for an assignment under this policy.
The maximum assignment made under these terms is /32 per operator. The maximum assignment made under these terms is /32 per operator.
Exchanges made under this policy remain subject to the address Exchanges made under this policy remain subject to the address
space license policy. space license policy.
5.9.4 Provider Independent assignment
Organizations with a previously delegated IPv4 assignment from
APNIC are eligible for an appropriately sized IPv6 block under
Section 5.1 above.
Requests made under 5.9.4 must include a detailed plan of intended
usage of the proposed address block over at least the 12 months
following the allocation.
5.9.4.1 Initial assignment
Organizations are eligible for an IPv6 Provider Independent
delegation if they are able to demonstrate a valid reason that an
assignment from their ISP, or LIR, is not suitable.
For guidelines on what will be considered a valid technical or
other reason, see “APNIC guidelines for IPv6 allocation and
assignment requests”.
http://www.apnic.net/ipv6-guidelines
The minimum assignment made under this policy is a /48. Larger
blocks may be delegated in circumstances outlined in “APNIC
guidelines for IPv6 allocation and assignment requests”.
http://www.apnic.net/ipv6-guidelines
5.9.4.2 Subsequent assignment
Subsequent Provider Independent assignments may be delegated to
organizations that are able to demonstrate why an additional
portable assignment is required and why an assignment from an ISP
or other LIR cannot be used for this purpose; that the use of the
initial provider independent delegation generated the minimum
possible number of global routing announcements and the maximum
aggregation of that block; and, how the subsequent assignment will
be managed to minimise the growth of the global IPv6 routing
table.
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. 7 change blocks. 
11 lines changed or deleted 49 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/