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] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
- Previous message (by thread): [address-policy-wg] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
- Next message (by thread): [address-policy-wg] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jan Ingvoldstad
frettled at gmail.com
Tue Feb 5 11:22:15 CET 2019
On Tue, Feb 5, 2019 at 11:16 AM Sander Steffann <sander at steffann.nl> wrote: > Hi Michiel, > > > Just another point for discussion: what to do when this /24-only policy > is in effect and RIPE NCC happens to recover a large chunk (e.g. /16 or > more) and is able to hand-out multiple /22's again? > > The policy explicitly states that once the waiting list policy is in > effect the old policy is removed. So the large block would be used to > process requests from the waiting list. > > Yup, and also: a /16 isn't a large chunk in comparison to the waiting list. It's only 256x /24 blocks. If I read the graphs right, it would be gone in less than a month. -- Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/address-policy-wg/attachments/20190205/7f76e311/attachment.html>
- Previous message (by thread): [address-policy-wg] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
- Next message (by thread): [address-policy-wg] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]