[address-policy-wg] 2015-01 Draft Document and Impact Analysis Published (Alignment of Transfer Requirements for IPv4 Allocations)

Hi Daniel,

Thanks for your questions.

The proposal would only put into place a 24 month holding period for 
allocations that were made by the RIPE NCC. For allocations that are 
transferred between LIRs, an identical (24 month) holding period already 
exists.

It has already been mentioned on the mailing list, but I would like to 
confirm that the RIPE NCC would not revert any previous transfers if the 
proposal is accepted. But for all new transfer requests, the RIPE NCC 
would check that at least 24 months had elapsed since the allocation was 
originally made.

I hope this helps.

Kind regards

Marco Schmidt
Policy Development Officer
RIPE NCC

On 11/05/15 19:29, Daniel Baeza (Red y Sistemas TVT) wrote:
> Hi
>
> El 11/05/2015 a las 19:25, Andre Keller escribió:
>> Hi,
>>
>> On 11.05.2015 19:15, Daniel Baeza (Red y Sistemas TVT) wrote:
>>> It will be retroactive? How this will be handled?
>>
>> If my interpretation of the IA is correct, the retroactive part is
>> restricted to evaluation of transfer requests. It means if/once the
>> policy is implemented, it applies to resources already allocated by RIPE
>> NCC but not yet transferred. Resources already transferred wont be
>> affected. I think this is a sensible approach.
>
> Quoting Marco:
>
> >The proposal would apply to allocations that were made in the past. 
> >Whenthe RIPE NCC received a transfer request, we would check to see 
> >that at least 24 months had elapsed since the allocation was made. 
> For >example, a /22 allocation that was made 23 months before the 
> proposal >was accepted would have a waiting period of one month before 
> it could >be transferred.
>
> What kind of allocations is talking Marco about? RIPE to LIR or LIR to 
> LIR?
>
> Regards,
>
>