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 ]
boggits
boggits at gmail.com
Mon Feb 4 17:30:14 CET 2019
On Mon, 4 Feb 2019 at 12:04, Marco Schmidt <mschmidt at ripe.net> wrote: > > This proposal aims to reduce the IPv4 allocation size to a /24 once the > RIPE NCC is unable to allocate contiguous /22 ranges. > Is it worth having a period of handing out two or three (potentially non-contiguous) /24s when the last complete /22 disappears, before moving to just a single /24 (with a step at 2 if we start at 3)? I can see the logic between the change in sizes, I'm just wondering if there was a case for intermediatory steps to reduce the pain Either way, I support the proposal with or without this change Thx J -- James Blessing 07989 039 476 -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/address-policy-wg/attachments/20190204/1eae502c/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 ]