This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/address-policy-wg@ripe.net/
[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 ]
Nick Hilliard
nick at inex.ie
Tue Jun 9 14:22:21 CEST 2015
On 09/06/2015 12:15, Sascha Luck [ml] wrote: > This is also the (only) reason why I oppose this proposal. It > sets a precedent for ex post facto rule changes which is, IMO, > dangerous, especially in light of other appetites for stricter > IPv4 rationing that have been voiced in this discussion. not really, no. RIPE NCC assigned number resources were and are assigned on the basis of the resource holder adhering to RIPE policy. Policy changes which apply retroactively to existing number resources have been made in the past, notably 2007-01. I.e. this policy change doesn't set a precedent. Nick
- 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 ]