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] IPv6 Stockpiling
- Previous message (by thread): [address-policy-wg] IPv6 Stockpiling
- Next message (by thread): [address-policy-wg] IPv6 Stockpiling
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Fri Oct 29 16:38:46 CEST 2021
Hi, > One reason for a LIR to have multiple /29 is when a lir (ISP in this case) buys smaller operators and consolidates them. > Since all of these blocks had some use before consolidation and its tedious to renumber.... > > I don’t see this as stockpiling, they will be even more in use in the future anyway, and we need to have enough use before being able to obtain more space... If this is indeed the reason I see no problem with it. That's just operational reality. If there is some misunderstanding causing LIRs to accumulate many IPv6 allocations then we can look at better education. And if there is some malign reason for it, then we can look at changing the policy. I think we need to understand the symptoms better to be able work on the cure :) Sander
- Previous message (by thread): [address-policy-wg] IPv6 Stockpiling
- Next message (by thread): [address-policy-wg] IPv6 Stockpiling
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]