Hi John,
Per <https://www.ripe.net/ripe/policies/proposals/2014-05>e
[...] (although its adoption will have no effect on Inter-RIR transfers between ARIN and the APNIC region.)”
There it is indeed, black on white. Thank you for pointing out my poor short time memory. :-) I suppose that the reason why this was being brought up as a possible problem at the APNIC meeting was that this clarification had not yet been made at that point.
The existence of RIPE 2014-05 was raised last week during the ARIN 34 meeting, and I noted the ARIN staff determination on this matter (that APNIC's inter-RIR transfer policy remains compatible with ARIN policy if RIPE 2014-05 is adopted by the RIPE community.) The ARIN community is aware that they would need to propose some change to ARIN's Inter-RIR transfer policy if another outcome is desired.
Ack. This is reasonable and what I would expect. I would find it interesting to watch this discussion from the ARIN 34 meeting, hopefully recordings from it will be made available at some point.
p.s. The RIPE and APNIC RIR policy development staff should be thanked for their foresight in researching this topic in advance, and arranging for the very coherent "Compatibility with other RIRs" section in the RIPE 2014-05 Impact Analysis... thanks! :-)
Indeed, it is important to know if the new policy is going to work at all before adopting it. Not much point in doing it if not... I guess what remains to be done with 2014-05 in this regard, is to clarify it so that APNIC (or any other RIR for that matter) realises that its language isn't meant to cause a "policy loop", but rather to be accommodating to RIR communities that would like to explicitly insist that a out of region transfer source/destination entity must be invariably subjected to a certain set of conditions (which are not necessarily duplicated in the policies of the region of the aforementioned entity). Tore