On Oct 21, 2014, at 11:39 AM, Tore Anderson <tore@fud.no> wrote:
To be clear, ARIN policy for inter-RIR transfers does not require any specific need period - my text was solely to be an example. There must be policy text that refers to needs-based (i.e. some operational need for the address space), but any change in ARIN's policy for transfers within the ARIN region should not require a change to RIPE policy for needs-based compatibility in any circumstance.
Really? I would have thought that the periods would need to be the same for the policies to be compatible. Otherwise, we could have set a ridiculously long period like 1000 years. Even if it that would be compatible with the letter of the ARIN policy I highly doubt it would be compatible with the spirit. :-)
I imagine that ARIN community would propose a policy change in the face of such antics, but ARIN's existing Inter-RIR transfer policy language is intentionally not proscriptive in this regard.
By ensuring identical periods are used, there can be no argument that differing periods cause incompatibility or any form of loopholes. Maybe that's not a concern for compatibility with ARIN today, but it might be tomorrow with another RIR. In any case, it shouldn't hurt compatibility with ARIN's policy, right?
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. 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.
Once the RIPE Inter-RIR transfer policy is determined to be needs-based and compatible, then processing of individual requests can easily be handled by RIPE NCC without any need for sharing of requesters information with other parties. This works quite well quite Inter-RIR transfers between APNIC and the ARIN region today, whereas there are likely to be potential implementation issues with your proposed approach that would need to be carefully explored; for example, ARIN has no relationship to a requestor in the RIPE region, no non-disclosure agreement, etc.
Good point about the NDA. You're right, let's not go there.
Indeed, a tad messy...
Then I have:
«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».
Like I said before, it would be good to have an indication from you or another ARIN official on whether or not this would indeed be deemed as compatible with ARIN's inter-region transfer policy. That way, hopefully this WG won't have to do too many iterations of 2014-05 before settling on a piece of text that works for everyone involved.
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. Thanks, /John John Curran President and CEO ARIN