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/[email protected]/
[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 21:32:19 CEST 2015
On Mon, May 11, 2015, at 20:59, Sascha Luck [ml] wrote: > it can now be done for 2015-01. So if, next week, the community > decides that all allocations > /22 should never have been made, I > lose the ones I have already? Because it was already done for This is borderline to bad faith. Policy only affect future, and this is also valid for 2015-01. If you made some assumptions in the past and were not yet able to benefit from what you supposed - bad luck/hurry up (2015-01 is not YET policy). If we manage to change some of the *transfer* conditions, it is because the community belives that there's a problem to be solved. Want to see some really retroactive stuff still not considered so ? Spend a few years here in France :)
- 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 ]