[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 ]
Sascha Luck [ml]
apwg at c4inet.net
Mon May 11 19:45:31 CEST 2015
On Mon, May 11, 2015 at 07:25:42PM +0200, Andre Keller wrote: >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. Your interpretation is the same as mine, correct or not ;) The crux is, though: it changes ripe-623, the "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" document, not a hypothetical "Transfer Policies" document. This sets a precedent for changing *everything else* in this document and applying the changes retrospectively. I can't be the only one who does not want to go there? rgds, Sascha Luck
- 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 ]