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] Cleaning up Unused AS Numbers
- Previous message (by thread): [address-policy-wg] Cleaning up Unused AS Numbers
- Next message (by thread): [address-policy-wg] Cleaning up Unused AS Numbers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sascha Luck [ml]
apwg at c4inet.net
Mon Mar 27 13:02:27 CEST 2017
On Mon, Mar 27, 2017 at 01:46:32AM +0200, Kai 'wusel' Siering wrote: >What's the calculated gain, what's the overall benefit, given >the limited control (see above)? It's fine that the process is >automated on RIPE NCC's end, but LIRs will face additional work. >With now 32 bits at hand for AS numbers, what's the operational >benefit for the RIPE community as a whole if all "invisible" >6,6k ASNs would be returned after this effort? Especially as RFC >4893 is celebrating it's 10th birthday in a few weeks? I think this is a misunderstanding. The goal is not to reclaim "unused" ASNs, AIUI it is to re-establish contact with ASNs lost in the "swamp" over time. Any reclamations would presumably be incidental. It's just the NCC doing its job as a registry. rgds, Sascha Luck
- Previous message (by thread): [address-policy-wg] Cleaning up Unused AS Numbers
- Next message (by thread): [address-policy-wg] Cleaning up Unused AS Numbers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]