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 ]
Sander Steffann
sander at steffann.nl
Mon Feb 4 14:49:17 CET 2019
Hi Jim, > A policy to deal with whatever /24s the NCC might find stuffed down the back of the sofa will be more bother than its worth. Unless someone can provide compelling arguments -- ie there’s still a lot of v4 for the NCC to allocate -- I just don’t see the point. Sorry. > > How much of this hypothetical /24 space does the NCC hold anyway? How long might it last? It's more about that the NCC does with returned address space. The current pools will indeed run out very quickly, no point trying to extend those. The usefulness of this policy can be seen in https://ripe77.ripe.net/presentations/71-Andrea_Cima_RIPE_77_APWG.pdf slide 14. When we use the returned space in /22 chunks there is not much point in having a waiting list. If we use /24 there is. That's all :) Sander
- 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 ]