nanog mailing list archives
Re: 202401100645.AYC Re: IPv4 address block
From: Saku Ytti <saku () ytti fi>
Date: Thu, 11 Jan 2024 13:03:44 +0200
On Thu, 11 Jan 2024 at 12:57, Christopher Hawker <chris () thesysadmin au> wrote:
Reclassifying this space, would add 10+ years onto the free pool for each RIR. Looking at the APNIC free pool, I would estimate there is about 1/6th of a /8 pool available for delegation, another 1/6th reserved. Reclassification would see available pool volumes return to pre-2010 levels.
Just enough time for us to retire comfortably and let some other fool fix the mess we built? We don't need to extend IPv4, we need to figure out why we are in this dual-stack mess, which was never intended, and how to get out of it. We've created this stupid anti-competitive IPv4 market and as far as I can foresee, we will never organically stop using IPv4. We've added CAPEX and OPEX costs and a lot of useless work, for no other reason, but our failure to provide a reasonable solution going from IPv4 to IPv6. I can't come up with a less stupid way to fix this, than major players commonly signing a pledge to drop IPv4 in their edge at 2040-01-01, or some such. To finally create an incentive and date when you need to get your IPv6 affairs in order, and to fix the IPv4 antitrust issue. Only reason people need IPv4 to offer service is because people offering connectivity have no incentive to offer IPv6. In fact if you've done any IPv6 at all, you're wasting money and acting against the best interest of your shareholders, because there is no good reason to spend time and money on IPv6, but there should be. -- ++ytti
Current thread:
- Re: One Can't Have It Both Ways Re: Streamline the CG-NAT Re: EzIP Re: IPv4 address block, (continued)
- Re: One Can't Have It Both Ways Re: Streamline the CG-NAT Re: EzIP Re: IPv4 address block Forrest Christian (List Account) (Jan 15)
- RE: 202401100645.AYC Re: IPv4 address block KARIM MEKKAOUI (Jan 10)
- Re: 202401100645.AYC Re: IPv4 address block Tom Beecher (Jan 10)
- Re: 202401100645.AYC Re: IPv4 address block Nick Hilliard (Jan 10)
- Re: 202401100645.AYC Re: IPv4 address block Michael Butler via NANOG (Jan 10)
- Re: 202401100645.AYC Re: IPv4 address block Tom Beecher (Jan 10)
- Re: 202401100645.AYC Re: IPv4 address block Dave Taht (Jan 11)
- Re: 202401100645.AYC Re: IPv4 address block Nick Hilliard (Jan 11)
- Streamline The CG-NAT Re: 202401100645.AYC Re: IPv4 address block Abraham Y. Chen (Jan 11)
- Re: 202401100645.AYC Re: IPv4 address block Christopher Hawker (Jan 11)
- Re: 202401100645.AYC Re: IPv4 address block Saku Ytti (Jan 11)
- Re: 202401100645.AYC Re: IPv4 address block Benny Lyne Amorsen (Jan 11)
- IPv6? Re: 202401100645.AYC Re: IPv4 address block Abraham Y. Chen (Jan 11)
- Re: 202401100645.AYC Re: IPv4 address block Randy Bush (Jan 11)
- Re: 202401100645.AYC Re: IPv4 address block Giorgio Bonfiglio via NANOG (Jan 11)
- Re: 202401100645.AYC Re: IPv4 address block Emanuele Balla (Jan 11)
- Re: 202401100645.AYC Re: IPv4 address block Randy Bush (Jan 12)
- Backward Compatibility Re: 202401100645.AYC Re: IPv4 address block Abraham Y. Chen (Jan 12)
- Re: Backward Compatibility Re: 202401100645.AYC Re: IPv4 address block Randy Bush (Jan 12)
- Re: Backward Compatibility Re: 202401100645.AYC Re: IPv4 address block Eric Parsonage (Jan 12)
- Re: Backward Compatibility Re: 202401100645.AYC Re: IPv4 address block Tom Beecher (Jan 12)