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 ]
Kurt Kayser
kurt_kayser at gmx.de
Tue Dec 6 15:17:41 CET 2011
Hi Axel, > >> ok, i'll bite. what is the ncc doing instead? or is the need > >> no longer perceived? > > > > need continues. Have instructed staff to find fitting address space in > > the current holdings, and if needed, restructure / renumber. > > appreciate the answer. 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. Regards, Kurt -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
- 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 ]