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 ]
Nick Hilliard
nick at inex.ie
Wed Mar 11 14:40:44 CET 2015
Hi Marco, There are two fundamental problems here, one operational- and one policy-related. On 11/03/2015 13:24, Marco Schmidt wrote: [...] > ARIN has confirmed that the proposed policy text is compatible with its own > inter-RIR transfer policy. No potential issues have been indicated. 1. If there is a future incompatibility between RIPE policy and ARIN policy which concerns resources transferred under this category: > - Recipients within the ARIN region will be subject to current ARIN > policies and sign an RSA for the resources being received. ... whose policy applies? RIPE's or ARIN's? 2. As a separate but related issue, I am struggling to understand why the RIPE community should accept that that if ARIN resources are transferred to RIPE, that ARIN will retain a policy encumbrance on those resources in some situations. Nick
- 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 ]