[address-policy-wg] [policy-announce]2014-05 New Draft Document and ImpactAnalysis Published (Policy for Inter-RIR Transfers of InternetResources) (Erik Bais)

Hi,

* John Curran

> Actually, that is not clear, as ARIN's Inter-RIR transfer policy language 
> requires that an RIR have needs-based policy in order to be compatible for 
> transfers to/from ARIN, and having solely a reference to the another RIR's
> policy could be argued (by some) to not be actual needs-based policy for 
> RIPE.

I see.

> Specific needs-based language in RIPE's policy would be much cleaner, as 
> well as having RIPE NCC implementing something defined by the RIPE community 
> rather than criteria that may change at any time without RIPE community 
> involvement.

Another issue that could hypothetically arise from having a hard-coded
24 month limit is if the ARIN community increases their limit.
Considering that the purpose of adding the limit to 2014-05 in the first
place is only be to appease the ARIN community, it would be an odd
outcome if 2014-05 ends up being more strict than ARIN's policy (even if
this situation only lasts for the policy cycle necessary for us to catch
up with you).

So, perhaps it would be better with something like «within 24 months or
the corresponding period defined in the transfer policy of the other
RIR, whichever is greater»?

>> «For transfers from RIR regions which require the RIPE region to have
>> needs-based policies, recipients must provide a plan to the RIPE NCC for
>> the use of the transferred resource within the time period defined by
>> the transfer policy of the other RIR».
> 
> Even noting the consideration noted above, I do believe your proposed text 
> above to be compatible, needs-based policy for purposes of ARIN's NRPM 8.4 
> Inter-RIR transfers.

Excellent. Thank you!

Tore