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] 2011-03 New Policy Proposal (Post-depletion IPv4 address recycling)
- Previous message (by thread): [address-policy-wg] 2011-03 New Policy Proposal (Post-depletion IPv4 address recycling)
- Next message (by thread): [address-policy-wg] 2011-03 New Policy Proposal (Post-depletion IPv4 address recycling)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Tue May 24 10:33:25 CEST 2011
Hi, > 2. It's not explicitly defined because it all depends on the address space > returned. As I already indicated in another email, the long term effect of > this is likely to be that all /8s managed by the RIPE NCC will have a > minimum allocation size of a /22; and if we then run out of /22s or larger > and need to hand out multiple smaller blocks (moving to clause 4) a few > additional /8s might get *really* unlucky. But that will only happen when > we're scraping the RIPE NCC barrel. If we reach that point people can be glad they get *any* addresses. It's either this or no IPv4 addresses at all. They might hit prefix-length filters, but still, at least they have a chance to try something. - Sander
- Previous message (by thread): [address-policy-wg] 2011-03 New Policy Proposal (Post-depletion IPv4 address recycling)
- Next message (by thread): [address-policy-wg] 2011-03 New Policy Proposal (Post-depletion IPv4 address recycling)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]