This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/address-policy-wg@ripe.net/
[address-policy-wg] APNIC temporarily freezing v4 transfers to RIPE NCC?
- Previous message (by thread): [address-policy-wg] APNIC temporarily freezing v4 transfers to RIPE NCC?
- Next message (by thread): [address-policy-wg] APNIC temporarily freezing v4 transfers to RIPE NCC?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marco Schmidt
mschmidt at ripe.net
Wed Mar 11 14:24:52 CET 2015
Hello Nick, On 11/03/15 11:22, Nick Hilliard wrote: > Unfortunately, this is not respected in the ARIN inter-rir transfer policy: > > https://www.arin.net/policy/nrpm.html#eight4 > > which includes the text: > > "Recipients within the ARIN region will be subject to current ARIN policies > and sign an RSA for the resources being received." > > In other words, multinational organisations headquartered in the ARIN > region who receive resources transferred to another RIR will be subject to > ARIN policies. > > This is potentially a serious problem because transferring policy > encumbrances is likely to cause policy problems in future, if RIR policy > differences crop up. > > So the question is: can the RIPE NCC accept transfers from ARIN if the > receiver organisation has signed the ARIN RSA for these resources? And if > transfers are accepted within these terms and there's a conflict between > RIPE NCC policy and ARIN policy, whose policies takes precedence? RIPE's > or ARIN's? The proposed RIPE Policy for Inter-RIR Transfers of Internet Resources includes the statement: "While the transfer is in process, during the time the internet number resources are registered in the RIPE NCC service region, then RIPE policies will apply." https://www.ripe.net/ripe/policies/proposals/2014-05 And the RIPE NCC impact analysis states: "For transfers to the RIPE NCC service region, the resources will only be registered in the RIPE Registry when the transfer is completed. It is the RIPE NCC’s understanding that resources being transferred are subject to the policies of an RIR as long their are registered in its registry. " ARIN has confirmed that the proposed policy text is compatible with its own inter-RIR transfer policy. No potential issues have been indicated. Further, the complete paragraph 8.4 of the ARIN Number Resource Policy Manual says: "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 will be subject to current ARIN policies and sign an RSA for the resources being received. - Recipients within the ARIN region must demonstrate the need for up to a 24-month supply of IPv4 address space. - The minimum transfer size is a /24." https://www.arin.net/policy/nrpm.html#eight4 Regards, Marco Schmidt Policy Development Officer RIPE NCC
- Previous message (by thread): [address-policy-wg] APNIC temporarily freezing v4 transfers to RIPE NCC?
- Next message (by thread): [address-policy-wg] APNIC temporarily freezing v4 transfers to RIPE NCC?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]