[address-policy-wg] 2015-01 Draft Document and Impact Analysis Published (Alignment of Transfer Requirements for IPv4 Allocations)
- Previous message (by thread): [address-policy-wg] 2015-01 Draft Document and Impact Analysis Published (Alignment of Transfer Requirements for IPv4 Allocations)
- Next message (by thread): [address-policy-wg] 2015-01 Draft Document and Impact Analysis Published (Alignment of Transfer Requirements for IPv4 Allocations)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Baeza (Red y Sistemas TVT)
d.baeza at tvt-datos.es
Mon May 11 19:29:23 CEST 2015
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,
- Previous message (by thread): [address-policy-wg] 2015-01 Draft Document and Impact Analysis Published (Alignment of Transfer Requirements for IPv4 Allocations)
- Next message (by thread): [address-policy-wg] 2015-01 Draft Document and Impact Analysis Published (Alignment of Transfer Requirements for IPv4 Allocations)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]