Presentation by Adam Gosling at APRICOT 2018 on Tuesday, 27 February 2018.

1. 2018#apricot2018 45
Policy Implementation
Report
Adam Gosling
Product Manager – Information Services
APNIC

2. 2018#apricot2018 45
Agenda
• Implemented on 4 August 2017
– prop-117
• Implemented on 20 November 2017
– prop-116
– prop-121
– prop-122
2

3. 2018#apricot2018 45 32017#apricot2017
Proposal reaching
consensus at APNIC 43

4. 2018#apricot2018 45
prop-117 - Returned IPv4 address management
and Final /8 exhaustion
Proposal
– Recovered 103/8 space will be placed in the 103/8
(Final /8) pool.
– Recovered non-103/8 space will be placed in the IPv4 Recovered
pool.
Status
– Implemented on 4 August 2017
4

5. 2018#apricot2018 45 5
Proposals reaching
consensus at APNIC 44

6. 2018#apricot2018 45
prop-116: Prohibit to transfer IPv4 addresses in
the final /8 block
Proposal
• Prohibit the transfer of IPv4 addresses from the final /8 (103/8) block until
they have been delegated for at least five years.
• Applies to both market and M&A transfers.
Status
– Implemented on 20 November 2017
• Implementation lifted a moratorium on 103/8 block transfers
– Document published after editorial comment period
• Published on 20 December 2017
6

7. 2018#apricot2018 45
Final /8 103/8 Moratorium
• During APNIC 44 APNIC Executive Council (EC) placed an
immediate moratorium on all transfers from the 103/8 block
– From 14 September 2017
– Until 20 November 2017
• After prop-116 implemented
– Moratorium removed
– Secretariat processed approved 103/8 transfers and rejected those
not allowed under policy
7

8. 2018#apricot2018 45
prop-121: Updating “Initial IPv6 allocation”
policy
Proposal
• This proposal seeks to make sure policy is aligned with a wider set of
possible IPv6 deployment cases and facilitate the justification of the
allocation/assignment size if a bigger address block (versus the default
one) is requested.
Status
• Implemented on 20 November 2017
8

9. 2018#apricot2018 45
prop-122: Updating “Subsequent IPv6 allocation”
policy
Proposal
• This proposal seeks to make sure that the subsequent IPv6 allocation
policy is synchronized with the initial allocation one.
Status
• Implemented on 20 November 2017
9

10. 2018#apricot2018 45
9.2.2. Account holders without existing IPv4
space
To qualify for an initial allocation of IPv6 address space, an
organization must:
1. Be an LIR
2. Not be an end site
3. Plan, within two years, to provide IPv6 connectivity to other
organizations/end-users to which it will make assignments.
The allocation size, in case an address block bigger than the
default one is requested, will be based on the number of users,
the extent of the organisation's infrastructure, the hierarchical
and geographical structuring of the organisation, the
segmentation of infrastructure for security and the planned
longevity of the allocation.
10

11. #apricot2018
19 – 28 February 2018KATHMANDU, NEPAL
2018
45