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] stockpiling IPv6
- Previous message (by thread): [address-policy-wg] stockpiling IPv6
- Next message (by thread): [address-policy-wg] stockpiling IPv6
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mikael Abrahamsson
swmike at swm.pp.se
Wed Oct 28 13:54:09 CET 2020
On Wed, 28 Oct 2020, JORDI PALET MARTINEZ via address-policy-wg wrote: > We must remind that the allocation/assignment of resources is based on > justified need. And yes, we have a lot of IPv6 space, but it is really > justified and the same organization, having different LIRs, can use it > as a trick for stockpiling if there is not such justified need? My only concern here is routing table size over time, and it's not a very big concern of mine. One area that perhaps could be optimized is to have some kind of process where if someone is merging multiple LIRs and they're not yet using some of the /29, they might be given the option to hand back address space and receive a larger, contiguous address block if they so choose. If we give 65k ASNs a /29 each, this is a /13 worth of addresses. This is not a concern, addresswise. Routing table wise, if this can be cut in half or something, could be worth doing. -- Mikael Abrahamsson email: swmike at swm.pp.se
- Previous message (by thread): [address-policy-wg] stockpiling IPv6
- Next message (by thread): [address-policy-wg] stockpiling IPv6
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]