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 ]
Radu-Adrian FEURDEAN
ripe-wgs at radu-adrian.feurdean.net
Mon May 11 19:24:46 CEST 2015
On Mon, May 11, 2015, at 19:00, Sascha Luck [ml] wrote: > Why, a policy could be enacted that retroactively invalidates > allocation/assignment criteria, resulting in LIRs having to It is not retroactive, and it does not change the allocation criteria. It only changes transfer rules, and my understanding is that it will only apply from the moment it becomes policy (at best, more realistic is the time NCC is ready to implement, which may be some days/weeks later). What you say is suggesting the fact that obtaining an allocation for the sole purpose of transfer is acceptable behaviour, and I suppose most people here don't agree with that.
- 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 ]