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] can deadbeat LIRs reverse IPv4 exhaustion?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Carlos Friaças
cfriacas at fccn.pt
Thu Feb 7 08:59:09 CET 2019
On Wed, 6 Feb 2019, Daniel Karrenberg wrote: (...) >> ... Keep /22 possibility so the >> complete runout of IPv4 won't be postponed. > > See above. I do not see the point about 'complete runout'. We *have* run > out already. This is about the very very tail end. Allow me to disagree. People are still getting IPv4 addresses from the NCC. "Declaring runout" is not exactly the same as stopping handing out IPv4 addresses. Even when the pools reach ZERO, if 1000 LIRs stop paying fees (and that's only one example/route), the "runout" will be temporarily reverted, and handing out IPv4 addresses will be again, in theory, possible. The "reversion" won't happen if there is a policy in place stating RIPE NCC will not allocate any more IPv4 addresses -- who wants to propose that? I don't. Disclaimer: I have been advocating and deploying IPv6 since ~2001. I just think reducing by decree/policy the ability of people to use/deploy IPv4 is not the correct way to go. Cheers, Carlos > Daniel > >
- 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] can deadbeat LIRs reverse IPv4 exhaustion?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]