Search RPD Archives
[rpd] Fwd: [arin-ppml] Revised: ARIN-2017-4: Remove Reciprocity Requirement for Inter-RIR Transfers
ernest at afrinic.net
Tue Sep 12 04:05:51 UTC 2017
FYI - the ARIN community is discussing an updated version of
proposal 2017-4 that aims to remove the "reciprocity" requirement
for inter RIR transfers.
The proposal, if approved, would allow AFRINIC to receive IPv4
addresses from ARIN even if our policies do not allow for ARIN to
receive from AFRINIC.
(Of course we would need a policy to allow for inter RIR transfers
Full proposal text below.
-------- Forwarded Message --------
Subject: [arin-ppml] Revised: ARIN-2017-4: Remove Reciprocity
Requirement for Inter-RIR Transfers
From: ARIN <info at arin.net>
To: arin-ppml at arin.net
Draft Policy ARIN-2017-4: Remove Reciprocity Requirement for
AFRINIC and LACNIC are currently considering one-way inter-RIR
transfer proposals. Those RIR communities feel a one-way policy a
policy that allows network operators in their regions to obtain
space from another region and transfer it into AFRINIC and LACNIC
may best meet the needs of the operators in that region.
ARIN staff, in reply to an inquiry from AFRINIC, have formally
indicated that ARINs 8.4 policy language will not allow ARIN to
participate in such one-way transfers. The staff formally indicate
to AFRINIC that the word reciprocal in 8.4 prohibits ARIN from
allowing ARIN-registered space to transfer directly to AFRINIC (in
ARIN as a community should recognize that other RIR operator
communities have different needs than we do. We should recognize that:
- network operators in AFRINIC in LACNIC have need to obtain space
in the market;
- have reasons they think are important to not allow two-way
- we should understand that the history of the RIR system has led to
LACNIC and AFRINIC having multiple orders of magnitude less IPv4
address space than ARIN does.
Add the following sentence after the first sentence of NRPM 8.4:
Inter-RIR transfers may take place to an RIR with a non-reciprocal
inter-RIR transfer policy only when the recipient RIR has an IPv4
total inventory less than the average (mean) of the IPv4 total
inventory among all of the RIRs.
Timetable for implementation: Upon the ratification of any inter-RIR
transfer policy at another RIR that is one-way as described in the
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
Unsubscribe or manage your mailing list subscription at:
Please contact info at arin.net if you experience any issues.
More information about the RPD