APNIC policies and the PDP
An overview of the APNIC Policy Development Process, current resource policies, and the policy proposals recently discussed and implemented for SANOG 24.
Published on: Mar 4, 2016
Transcripts - APNIC policies and the PDP
APNIC Policies and the PDP
SANOG24, Delhi, India
• What are APNIC Policies?
• What is the PDP?
APNIC Resource Policies
• Policy environment for Internet number resource
distribution in the Asia Pacific
– Outlines the overall structure, principals, definitions, and goals.
• Policies for IPv4 address space management in the Asia
– Policies for IPv4 address space.
• IPv6 address allocation and assignment policy
– Policies for IPv6 addresses.
• Policies for Autonomous System number management in
the Asia Pacific region
– Policies for AS numbers.
APNIC Resource Policies cont’d
• APNIC transfer, merger, acquisition, and takeover policy
– Describes current APNIC policies for the transfer of resources.
• Policies for historical Internet resources in the APNIC
– Policies for the management of historical resource registrations in the
APNIC Whois Database.
• Experimental allocations policy
Policies for the temporary delegation of resources for experimental
Internet Resource Policies
• Policies evolve to always meet the operational
needs of ISPs and other network operators
• There is a system in place called the Policy
Development Process (PDP)
– Anyone can propose a policy
– Anyone can participate in decisions
– All decisions & policies documented & freely available to
is a cycle
Multistakeholder policy development
– Anyone can propose, discuss, and help decide policy
– APNIC publicly documents all policy discussions and decisions
• Bottom up
– The PDP itself and the resource policies are determined by the
community they serve
Policy SIG Charter
• Develop policies and procedures which relate to the
management and use of Internet address resources by APNIC,
NIRs and ISPs within the Asia Pacific region
• APNIC Policy
• APNIC Policy Development Process
• APNIC Policy SIG
• SIG Guidelines
• Mailing list subscription archive
Steps to Implementation
1. Proposal submission
2. Mailing list discussion before Open Policy Meeting
3. Must reach consensus at the OPM
4. Must reach consensus at the APNIC Member Meeting
5. Comment Period to confirm consensus
6. Executive Council endorsement
7. Editorial Comment period
Consensus Decision Making
• Consensus = “general agreement” taking into consideration
comments on the mailing list and at the meeting.
• Show of hands is a way of “broadly gauging opinion”
• Comments via Remote Participation are welcome
• Example definitions from Tao of IETF:
– a very large majority of those who care must agree
– strongly held objections must be debated until most people are
satisfied that these objections are wrong
• Minor Objections
– some problems may occur for some members of the group
• Major Objections
– major problems will occur for parts of the community
• Participants should “work together” to resolve objections
• The Secretariat’s role in the PDP is to facilitate the PDP
and implement the policy
• prop-105: Distribution of returned IPv4 address
(Modification of prop-088)
– This policy proposes to define a separate distribution policy for all non-103 IPv4 address blocks in
the APNIC pool, to start the distributions once "Global policy for post exhaustion IPv4 allocation
mechanisms by the IANA" is activated.
• prop-107: AS Number transfer policy proposal
– This policy would permit the transfer of Autonomous System Numbers (ASNs) within the APNIC
region and between regions with compatible inter-regional ASN transfer policies.
• prop-108: Suggested changes to the APNIC Policy
• prop-109: Allocate 18.104.22.168/24 and 22.214.171.124/24 to APNIC Labs
as Research Prefixes
– The objective of this proposal is to allocate 126.96.36.199/24 and 188.8.131.52/24 to APNIC Labs, to be used as
Policy Proposals at APNIC 37
• prop-111: Request-based expansion of IPv6 default
– Proposal did not reach consensus at the Policy SIG and was
returned to the author for further development
• This proposal modifies the eligibility for an organization to receive an initial IPv6
allocation up to a /29 by request basis.
• prop-110: Designate 184.108.40.206/24 as Anycast to support DNS
– The proposal reached consensus at the Policy SIG, but failed to
reach consensus at the AMM
• Returned to mailing list for further consideration, but later withdrawn by the author
• APNIC 38: Brisbane, Australia, 9-19 Sep 2014
• APRICOT 2015: Fukuoka, Japan, 24 Feb-6 Mar 2015