Hi Scott, On 11/03/2015 19:28, Scott Leibrand wrote: > That was not the intent of the policy language as drafted. Rather, than > clause was meant to apply to 8.4 inter-RIR transfers inbound to the ARIN > region from a source outside the ARIN region. So if someone in the RIPE > region decides for some reason to transfer resources to someone in the ARIN > region, and the addresses end up registered in the ARIN database, then the > recipient must sign an RSA and will be subject to current ARIN policies.
Right, ok. > This was *not* intended to apply to a transfer from the ARIN region to an > organization in the RIPE region, where the addresses will end up registered > in the RIPE NCC database. So it shouldn't matter whether the recipient > also has a presence in the ARIN region, or has an ARIN account. The actual > recipient should be considered to be in the RIPE region (not the ARIN > region) if the addresses are going to end up registered in the RIPE NCC > database. > > ARIN staff can comment on their interpretation of the language, but > hopefull it matches our original intent as summarized above. It would be helpful if we had a clear statement of interpretation from ARIN. As it stands, the language is ambiguous enough to allow misinterpretation of the original intent. Nick
