This document summarizes the history of IPv4 address transfer policies at APNIC and other Regional Internet Registries (RIRs), and provides an overview of the RIPE NCC's proposed policy for inter-RIR transfers. The proposal would allow transfers between RIRs as long as the recipient RIR's policies are compatible and the recipient fulfills any requirements defined by the sending RIR. It discusses whether ARIN may consider the RIPE NCC's policies to be sufficiently reciprocal and needs-based to allow such transfers. The presenter seeks community input on any issues or questions that should be raised at upcoming RIR meetings regarding inter-RIR transfer policies.

1. Update on RIPE NCC Inter-
RIR Transfer proposal
Adam Gosling
APNIC 38 Policy SIG Meeting
18 September 2014

2. Agenda
• Brief history of APNIC transfers
• ARIN Inter-RIR transfer policy
• RIPE transfer proposals
• Community discussion
2

3. Transfer policy history at APNIC
• prop-050: IPv4 address transfers
– Intra-RIR transfers only
– Prop-50 had no demonstrated need after final /8
• http://www.apnic.net/policy/proposals/prop-050
• prop-095: Inter-RIR IPv4 address transfer proposal
– Allow IPv4 transfer to other RIR regions
– Providing the counterpart RIR has a policy that allows transfers of
address space with APNIC account holders
– The conditions of the transfer defined by the source/recipient RIR
• http://www.apnic.net/policy/proposals/prop-095
3

4. ARIN Inter-RIR Transfers
• 8.4. Inter-RIR Transfers to Specified Recipients
– https://www.arin.net/policy/nrpm.html#eight4
• Inter-regional transfers may take place only via RIRs who agree
to the transfer and share reciprocal, compatible, needs-based
policies.
• Conditions on source:
– Source must meet any requirements defined by the RIR where the
source entity holds the registration.
• Conditions on recipient of the transfer:
– The conditions on a recipient outside of the ARIN region will be defined
by the policies of the receiving RIR.
– Recipients within the ARIN region must demonstrate the need for up to
a 24-month supply of IPv4 address space.
4

5. Transfer policy history at APNIC
• prop-096: Maintaining demonstrated needs requirement
in transfer policy after the final /8 phase
– Proposed that recipients of transfers continue to be required to justify
their need for IPv4 address space after the final /8 policy is activated.
5

6. Current APNIC transfer policy
• 4.2 Conditions on the source of the transfer
– Conditions on the source defined by the source RIR. This means:
– Where the source is in another region, the conditions on the source
as defined in the counterpart RIR's transfer policy at the time of
the transfer will apply.
• 4.3 Conditions on the recipient of the transfer
– For transfers to an APNIC recipient
• Recipients without IPv4 already must demonstrate a detailed plan for use within 24
months.
• Recipients that already hold IPv4 resources must provide a plan to use resources
within 24 months, show past usage rate, and, provide evidence of compliance
– Where the recipient is in another region
• The conditions on the recipient as defined in the counterpart RIR's transfer policy
• http://www.apnic.net/policy/transfer-policy#rir-transfer
6

7. RIPE NCC transfer policy status
• Section 5.1.3 Allocations made by the RIPE NCC to LIRs
– The LIR must confirm it will make assignment(s) from the allocation.
• http://www.ripe.net/ripe/docs/ripe-622#51
• Section 5.5 Transfers of Allocations
– Already permits intra-RIR transfers
– Re-allocated blocks are no different from the allocations made
directly by the RIPE NCC and so they must be used by the receiving
LIR according to the policies described in this document
• http://www.ripe.net/ripe/docs/ripe-622#55
• New Proposal
– Policy for Inter-RIR Transfers of Internet Resources
• http://www.ripe.net/ripe/policies/proposals/2014-05
7

8. RIPE NCC Proposal
• Any LIR is allowed to re-allocate complete or partial blocks
of IPv4 address space that were previously allocated to
them by the RIPE NCC or otherwise through the Regional
Internet Registry System.
• Address space may only be re-allocated to another LIR that
is a member of an RIR that allows transfers. The block that
is to be re-allocated must not be smaller than the minimum
allocation block size at the time of re-allocation.
• Re-allocation must be reflected in the RIPE Database. This
re-allocation may be on either a permanent or non-permanent
basis.
8

9. RIPE NCC Proposal cont’d
• When Internet number resources are transferred to another RIR,
the RIPE NCC will work with the destination RIR to allow the
transfer to the receiving LIR.
• When Internet number resources are transferred from another
RIR, the RIPE NCC will work with its member LIR to fulfil any
requirements of the sending RIR.
• If resources are transferred as legacy resources, the RIPE NCC
will apply the legacy policy when accepting these resources.
• LIRs that receive a re-allocation from another LIR cannot re-allocate
complete or partial blocks of the same address space to
another LIR within 24 months of receiving the re-allocation.
9

10. Proposed transfer: APNIC > RIPE NCC
Conditions on APNIC Source
• As defined in the counterpart
RIR's transfer policy
RIPE NCC Recipient
• Fulfill any requirements of the
sending RIR
10

11. Proposed transfer: APNIC > RIPE NCC
Conditions on APNIC Source
• As defined in the counterpart
RIR's transfer policy
RIPE NCC Recipient
• Fulfill any requirements of the
sending RIR
• Plus existing policy requirement
– Confirm will make allocations
– Cannot re-transfer for 24 months
11
Will the ARIN community see this relationship as a
reciprocal, compatible, needs-based policy?

12. Questions…
• The exact outcome of all this is difficult to predict until the
RIPE community approves an Inter-RIR policy.
– This will happen eventually
• Do we have issues/questions we should raise at the next:
– ARIN meeting (Baltimore, Maryland in October)?
– RIPE meeting (London, UK in November)
• Should the APNIC community consider policy changes?
12

13. Discuss!
13

14. Thank you
14
adam@apnic.net
@bout_policy