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 ]
Jim Reid
jim at rfc1035.com
Wed Feb 6 11:19:15 CET 2019
On 6 Feb 2019, at 09:39, Daniel Karrenberg <dfk at ripe.net> wrote: > > a) It is not tenable for the RIPE NCC to stop allocating IPv4 addresses > as long as it has blocks that are useful to route packets. In principle, yes. In practice, no. There will come a point where it will be more bother than it’s worth to allocate teeny blocks from the dregs of the dregs. [Do we really want to one day be issuing each new LIR with exactly 1 IPv4 address so they can plug in to a v4-only IXP or transit provider?] When that tipping point is reached, I would hope the NCC makes an orderly exit from its IPv4 allocation business instead of trying to keep it alive at all costs. The question here I think is what should be the trigger event. And then what happens to the remaining v4 addresses that fell down the back of the sofa, slipped through the cracks in the floorboards and ended up in a disused basement behind a locked door that has a “beware of the leopard” sign. Well OK. That’s two questions. :-) How much v4 space would the NCC be holding once it’s no longer got /22s to allocate? That’s three questions. :-)
- 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 ]