On Mon, Mar 25, 2013 at 1:35 PM, Scott Leibrand <scottleibrand@gmail.com> wrote:

On Thu, Mar 21, 2013 at 11:53 PM, Tore Anderson <tore@fud.no> wrote:

This issue might be resolved by having 2012-02 add some text that
upholds the need principle for transfers coming in from regions that
demand it (read: ARIN), or for the recipient LIRs of such transfers
overall. I have no suggestion on exactly how this text could look like,
I'm afraid.

Perhaps the key would be to have RIPE continue doing needs assessment on transfers, while allowing LIRs to reassign space to customers without any particular requirements. I'm not sure if RIPE would still have to collect some sort of usage information on reassigned space in the event an LIR came back for another block via transfer, but I suspect that'd be a much lower burden than the current needs-assessment-on-everything situation.

Specifically, maybe we could simply use the same language used in the APNIC transfer policy (http://www.apnic.net/policy/transfer-policy), which is currently being used for inter-RIR transfers between ARIN and APNIC:

3.3 Conditions on recipient of the transfer

The recipient entity will be subject to current APNIC policies.

Recipients that do not already hold IPv4 resource must demonstrate a detailed plan for the use of the transferred resource within 24 months.

Recipients that already hold IPv4 resources must:

Demonstrate a detailed plan for the use of the transferred resource within 24 months,

Show past usage rate, and

Provide evidence of compliance with APNIC policies with respect to past delegations.

-Scott