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] RIPE NCC address request retracted
- Previous message (by thread): [address-policy-wg] RIPE NCC address request retracted
- Next message (by thread): [address-policy-wg] RIPE NCC address request retracted
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nigel Titley
nigel at titley.com
Tue Dec 6 17:27:06 CET 2011
On 06/12/11 14:17, Kurt Kayser wrote: > > True, ideally I would also like to see a comparison of effort of new address space to be used vs. legacy space analyzed and reorganized in order to save new request. (unit to measured in man-hours and amount of address space under discussion). > Idea is to motivate people to start considering reorg vs. new blocks + requests for distribution. I also understand that above a certain size, this never would make sense. > On the other hand I'd rather not see any more wasted time go down this rat-hole. Nigel
- Previous message (by thread): [address-policy-wg] RIPE NCC address request retracted
- Next message (by thread): [address-policy-wg] RIPE NCC address request retracted
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]