Jonathan Perkin

I have many, many issues with #IPv6, but at least there was always the confidence that the address space was never going to run out, because nobody would be dumb enough to repeat the mistakes learned from IPv4 allocation, right?

https://whois.arin.net/rest/net/NET6-2630-2

Oh.

Whois-RWS

Dec 13, 2023 at 11:10amWeb
Show threadhax 📡Dec 13, 2023
@jperkin In 2015 the british military and Kaufland asked for more than a /29. https://www.ripe.net/participate/policies/proposals/2015-03
Assessment Criteria for IPv6 Initial Allocation Size

2015-03: Assessment Criteria for IPv6 Initial Allocation Size

RIPE Network Coordination Centre
Show threadJima Dec 13, 2023

@hax404 @jperkin @onepict There appear to be 60 IPv6 allocations larger than /29 in RIPE-NCC land, spanning from 2003-2020.

(Granted, the largest are the three /19s.)

Show threadFink Dec 13, 2023
@jperkin aah, thats only the INTERNAL net, wait until you see DMZ and EXTERNAL  
Show threadLisPiDec 13, 2023
@jperkin @nytpu I suggest we ignore their registration.
Show threadKevin P. FlemingDec 14, 2023
@jperkin W. T. F.
Show threadMatt NordhoffDec 14, 2023

@jperkin

"The bank has approximately 750 branches, including 30 café style locations,[3] and 2,000 ATMs."

Great so they can divide that in half, assign a /28 to each ATM, and go back to ARIN and request another /16 if they add 49 more?

Show threadSebastian DO2SGFDec 14, 2023
@jperkin "No one has the intention to burn IPv6 address space" /s
Show threadTerrorBite 🦁Dec 14, 2023
@jperkin what would you even do with 5192296858534827628530496329220096 different IP addresses?
Show threadPeter TribbleDec 14, 2023
@jperkin
One of the arguments with IPv6 was that because the address space is inexhaustible, you can just give out arbitrarily large chunks and never need to worry about efficient allocations of the address space. Similar sort of magical thinking that describes cloud as "infinitely scalable".