[sig-policy] prop-085: Eligibility for critical infrastructure assignmen
The following proposal, 'Eligibility for critical infrastructure
assignments from the final /8', has been sent to the Policy SIG for
review. It will be presented at the Policy SIG at APNIC 30.
We invite you to review and comment on the proposal on the mailing list
before the meeting.
The comment period on the mailing list before an APNIC meeting is an
important part of the policy development process. We encourage you to
express your views on the proposal:
- Do you support or oppose this proposal?
- Does this proposal solve a problem you are experiencing? If so,
tell the community about your situation.
- Do you see any disadvantages in this proposal?
- Is there anything in the proposal that is not clear?
- What changes could be made to this proposal to make it more
effective?
Information about this and other policy proposals is available from:
http://www.apnic.net/policy/proposals/prop-085
randy, Ching-Heng, and Terence
________________________________________________________________________
prop-085-v001: Eligibility for critical infrastructure assignments from
the final /8
________________________________________________________________________
Authors: Terence Zhang Yinghao <zhangyinghao at cnnic dot cn>
Wendy Zhao Wei <zhaowei at cnnic dot cn>
Version: 1
Date: 22 July 2010
1. Introduction
----------------
This policy proposal seeks to make it possible for critical
infrastructure account holders (such as new ccTLDs or gTLDs) to receive
portable IPv4 assignments from the final /8 space.
In the spirit of the current final /8 policy [1], this proposal still
ensures each account holder is only eligible to receive one single
allocation OR assignment from the final /8 space.
2. Summary of the current problem
----------------------------------
Currently, critical infrastructure networks such as TLDs (Top Level
Domains) are eligible to receive portable IPv4 assignments under the
critical infrastructure policy [2].
But the current final /8 policy permits only allocations to account
holders to be made. This means that during the final /8 phase, it will
be impossible to make IPv4 addresses assignments to end users under
the critical infrastructure policy.
With the recent launch of Internationalized Domain Name country code
TLDs (IDN ccTLDs) and ongoing discussion on policy for open global TLDs
(gTLDs), we can expect dozens of IDN TLDs and gTLDs to be created in the
next few years.
Even if we have great developments in IPv6 deployment during these few
years, legacy IPv4 networks will remain in co-existence with IPv6 for
many years. Critical infrastructure networks like TLD nameservers will
still need IPv4 addresses to serve the IPv4 Internet.
3. Situation in other RIRs
---------------------------
AfriNIC has a policy proposal under discussion that permits assignments
as well as allocations to be made from AfriNIC's last /8 from IANA:
AFPUB-2010-v4-002: IPv4 Soft Landing Proposal
http://www.afrinic.net/docs/policies/AFPUB-2010-v4-002.htm
ARIN has adopted a policy that will take effect when ARIN receives its
final /8 from IANA. This policy permits both assignments and allocations
to be made from a reserved /10 block as long as the requestor can
demonstrate immediate IPv6 deployment requirements:
NRPM section 4.10, Dedicated IPv4 block to facilitate IPv6
Deployment
https://www.arin.net/policy/nrpm.html#four10
RIPE has a policy proposal under discussion that permits allocations to
be made from RIPE's last /8 worth of space, but not assignments:
Allocations from the last /8
http://www.ripe.net/ripe/policies/proposals/2010-02.html
LACNIC has adopted a policy that permits critical infrastructure
assignments to new members from LACNIC's final /12:
LACNIC Policy Manual, section 10.1, Special IPv4 Allocations/
Assignments Reserved for New Members
http://www.lacnic.net/en/politicas/manual11.html
4. Details
-----------
It is proposed that each APNIC account holder will be eligible to
request and receive a single assignment from the remaining /8 worth of
space, with the following conditions:
4.1 The account holder must meet the criteria for receiving an IPv4
portable assignment specified in section 11.3, "Critical
infrastructure" in "Policies for IPv4 address space management in
the Asia Pacific region"[2].
4.2 Each assignment will consist of the minimum IPv4 assignment size
for critical infrastructure, or the minimum IPv4 allocation size,
whichever is smaller.
4.3 All APNIC account holders are eligible to receive only one
allocation OR assignment from the final /8 worth of address
space. This applies to both current and future account holders.
5. Pros/Cons
-------------
5.1 Advantages
- This proposal makes it possible for critical infrastructure
account holders to receive portable assignments from the final /8
space.
5.2 Disadvantages
- None.
6. Effect on APNIC Members
---------------------------
APNIC Members with critical infrastructures may receive IPv4 address
assignments from the final /8.
7. Effect on NIRs
------------------
Same as effect on APNIC Members.
8. References
-------------
[1] See section 9.10, Distribution of the final /8 worth of space in the
unallocated APNIC IPv4 address pool" in "Policies for IPv4 address
space management in the Asia Pacific region"
http://www.apnic.net/policy/add-manage-policy.html#9.10
[2] See section 11.3, "Critical infrastructure" in "Policies for IPv4
address space management in the Asia Pacific region"
http://www.apnic.net/policy/add-manage-policy.html#11