APNIC Home

diff-apnic-127-v008

 apnic-resource-policies.txt  apnic-127-v008-draft.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: 007 Version: 008
Date of original publication: 5 March 2015 Date of original publication: 5 March 2015
Date of this version: 2 July 2019 Date of this version: xx January 2020
Review scheduled: n/a Review scheduled: n/a
Obsoletes: apnic-127-v006 Obsoletes: apnic-127-v007
Status: Active Status: Draft
Comments: Implements prop-128 and prop-129 Comments: Implements prop-131 and prop-132
———————————————————————- ———————————————————————-
Table of Contents Table of Contents
—————– —————–
Part 1: Policy Environment Part 1: Policy Environment
————————– ————————–
1.0. Introduction 1.0. Introduction
skipping to change at line 94 skipping to change at line 94
4.1.1. Review 4.1.1. Review
4.1.2. Validity of delegations 4.1.2. Validity of delegations
4.2. Closure and recovery 4.2. Closure and recovery
4.2.1. Recovery of unused historical resources 4.2.1. Recovery of unused historical resources
5.0. Resource Management 5.0. Resource Management
5.1. How APNIC manages address space 5.1. How APNIC manages address space
5.1.1. Reservation for future uses 5.1.1. Reservation for future uses
5.1.2. Sparse allocation framework 5.1.2. Sparse allocation framework
5.1.3. IPv4 addresses returned to APNIC 5.1.3. IPv4 addresses returned to APNIC
5.1.4. Preventing the Use of Undelegated APNIC Address Space
5.2. LIR address space management 5.2. LIR address space management
5.2.1. Assignment window for LIRs 5.2.1. Assignment window for LIRs
5.2.2. IPv4 address usage estimates 5.2.2. IPv4 address usage estimates
5.2.3. IPv4 Delegations to downstream IRs 5.2.3. IPv4 Delegations to downstream IRs
5.2.3.1. Effect of delegation to downstream IRs on upstream LIR’s 5.2.3.1. Effect of delegation to downstream IRs on upstream LIR’s
usage rate usage rate
5.2.4. Policies for LIR IPv6 allocation and assignment 5.2.4. Policies for LIR IPv6 allocation and assignment
5.2.4.1. LIR-to-ISP allocation 5.2.4.1. LIR-to-ISP allocation
5.2.4.2. Assignment address space size 5.2.4.2. Assignment address space size
5.2.4.3. Assignment of multiple /48s to a single end site 5.2.4.3. Assignment of multiple /48s to a single end site
skipping to change at line 1038 skipping to change at line 1039
5.1.3. IPv4 addresses returned to APNIC 5.1.3. IPv4 addresses returned to APNIC
————————————— —————————————
Any IPv4 resources received by APNIC will be placed into the Any IPv4 resources received by APNIC will be placed into the
APNIC IPv4 pool for delegation under the policies described in APNIC IPv4 pool for delegation under the policies described in
this document. This placement applies to any IPv4 addresses this document. This placement applies to any IPv4 addresses
APNIC receives from IANA and/or holders of addresses in the APNIC receives from IANA and/or holders of addresses in the
APNIC Whois Database, subject to any future global policy for APNIC Whois Database, subject to any future global policy for
the redistribution of addresses received by IANA from the RIRs. the redistribution of addresses received by IANA from the RIRs.
5.1.4. Preventing the Use of Undelegated APNIC Address Space
————————————————————
Undelegated APNIC Address Space (IPv4 or IPv6) should not be
publicly advertised by any Autonomous System. To prevent its
use, APNIC will create RPKI ROAs with origin AS0 (AS zero) for
all undelegated address space (marked as �Available� and �Reserved�
in the delegated-apnic-extended-latest stats file) for which it is
the current administrator.
While any current resource holder can create AS0 ROA for the resources
they have under their account administration, only APNIC has the
authority to create AS0 ROAs for APNIC address space not yet delegated
to an organization. When APNIC delegates address space to an organization,
APNIC will remove the prefix from the AS0 ROA.
5.2. LIR address space management 5.2. LIR address space management
——————————— ———————————
LIRs may delegate address space to their customers subject to the LIRs may delegate address space to their customers subject to the
following provisions. following provisions.
5.2.1. Assignment window for LIRs 5.2.1. Assignment window for LIRs
——————————— ———————————
APNIC and NIRs shall apply an assignment window mechanism to APNIC and NIRs shall apply an assignment window mechanism to
help LIRs understand and comply with APNIC policies and the help LIRs understand and comply with APNIC policies and the
address management goals. address management goals.
skipping to change at line 1141 skipping to change at line 1157
sites are required to be registered either by the LIR or its sites are required to be registered either by the LIR or its
subordinate ISPs in such a way that the RIR/NIR can properly subordinate ISPs in such a way that the RIR/NIR can properly
evaluate the HD-Ratio when a subsequent allocation becomes evaluate the HD-Ratio when a subsequent allocation becomes
necessary. necessary.
5.2.4.2. Assignment address space size 5.2.4.2. Assignment address space size
————————————– ————————————–
LIRs must make IPv6 assignments in accordance with the LIRs must make IPv6 assignments in accordance with the
following provisions. following provisions.
End-users are assigned an end site assignment from their LIR End-users are assigned an end site assignment from their LIR or ISP.
or ISP. The exact size of the assignment is a local decision The size of the assignment is a local decision for the LIR or ISP to
for the LIR or ISP to make, using a minimum value of a /64 make, using a value of “n” x /64.
(when only one subnet is anticipated for the end site) up to
the normal maximum of /48, except in cases of extra large
end sites where a larger assignment can be justified.
RIRs/NIRs are not concerned about which address size an RIRs/NIRs are not concerned about which address size an
LIR/ISP actually assigns. Accordingly, RIRs/NIRs will not LIR/ISP actually assigns. Accordingly, RIRs/NIRs will not
request the detailed information on IPv6 user networks as request the detailed information on IPv6 user networks as
they do in IPv4, except for the cases described in Section they do in IPv4, except for the cases described in Section
9.2.1. and for the purposes of measuring utilization as 9.2.1. and for the purposes of measuring utilization as
defined in this document. defined in this document.
5.2.4.3. Assignment of multiple /48s to a single end site 5.2.4.3. Assignment of multiple /48s to a single end site
——————————————————— ———————————————————
When a single end site requires an additional /48 address Assignment larger than /48 (shorter prefix) or additional assignments
block, it must request the assignment with documentation or exceeding a total of /48 must be made based on address usage, or because
materials that justify the request. Requests for multiple or of different routing requirements exist for additional assignments.
additional /48s will be processed and reviewed (i.e.,
evaluation of justification) at the RIR/NIR level.
Note: There is no experience at the present time with the
assignment of multiple /48s to the same end site. Having the
RIR review all such assignments is intended to be a
temporary measure until some experience has been gained and
some common policies can be developed. In addition,
additional work at defining policies in this space will
likely be carried out in the near future.
5.2.4.4. Assignment to operator’s infrastructure In case of a review or when making a request for a subsequent allocation, the
———————————————— LIR must be able to present documentation justifying the need for assignments
An organization (ISP/LIR) may assign a /48 per PoP as the shorter than a /48 to a single end site.
service infrastructure of an IPv6 service operator. Each
assignment to a PoP is regarded as one assignment regardless
of the number of users using the PoP. A separate assignment
can be obtained for the in-house operations of the operator.
5.3. Registration requirements 5.3. Registration requirements
—————————— ——————————
5.3.1. Registration requirements for IPv4 addresses 5.3.1. Registration requirements for IPv4 addresses
————————————————— —————————————————
IRs are responsible for promptly and accurately registering IRs are responsible for promptly and accurately registering
their address space use with APNIC as follows: their address space use with APNIC as follows:
– All delegations from APNIC to the IR must be registered. – All delegations from APNIC to the IR must be registered.
– All delegations to downstream IRs must be registered. – All delegations to downstream IRs must be registered.
– Delegations made to networks greater than a /30 must be – Delegations made to networks greater than a /30 must be
skipping to change at line 2134 skipping to change at line 2133
—————————- —————————-
Organizations are eligible for an IPv6 Provider Independent Organizations are eligible for an IPv6 Provider Independent
delegation if they are able to demonstrate a valid reason that delegation if they are able to demonstrate a valid reason that
an assignment from their ISP, or LIR, is not suitable. an assignment from their ISP, or LIR, is not suitable.
For guidelines on what will be considered a valid technical or For guidelines on what will be considered a valid technical or
other reason, see “APNIC guidelines for IPv6 allocation and other reason, see “APNIC guidelines for IPv6 allocation and
assignment requests”. assignment requests”.
http://www.apnic.net/ipv6-guidelines http://www.apnic.net/ipv6-guidelines
The minimum assignment made under this policy is a /48. Larger The minimum size of the assignment is a /48. The considerations of, Section
blocks may be delegated in circumstances outlined in “APNIC 5.2.4.3 Assignment of multiple /48s to a single end site, must be followed if
guidelines for IPv6 allocation and assignment requests”. needed.
http://www.apnic.net/ipv6-guidelines http://www.apnic.net/ipv6-guidelines
10.1.4.2. Subsequent assignment 10.1.4.2. Subsequent assignment
——————————- ——————————-
Subsequent Provider Independent assignments may be delegated Subsequent Provider Independent assignments may be delegated
to organizations that are able to demonstrate to organizations that are able to demonstrate
– why an additional portable assignment is required and why – why an additional portable assignment is required and why
an assignment from an ISP or other LIR cannot be used for an assignment from an ISP or other LIR cannot be used for
this purpose; this purpose;
 End of changes. 9 change blocks.
34 lines changed or deleted 33 lines changed or added
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/