Forcing owners of legacy /8's to give them up is hugely cost prohibitive for them. Various orgs with their own /8's might not announce them, but use them extensively internally.
Also, it wouldn't really help stave off the amount of IP's required, and we'd still be out in months.
You do realize most of the legacy /8 owners are actively using them, right?
Re:IPv6 enabled Christmas Tree
by api_or_ipa on Thursday December 15, 2016 @01:58PM
(#13187128)
I'm sure Apple, Ford and the US postal service are all using all 16 million addresses. The fact is that most intra-network traffic doesn't need an IPv4 address since it'll be NAT'd anyways. So even if Apple has 16 million IoT devices around campus, it doesn't actually need 16 million addresses.
Fun fact, Stanford used to have an /8 but returned it since it wasn't using all it's addresses.
CGNAT prevents users from hosting personal services - its a PitA.
Re:IPv6 enabled Christmas Tree
by tlrobinson on Thursday December 15, 2016 @02:37PM
(#13187503)
Yeah, I just discovered my ISP (WebPass) has exhausted their IPv4 allocation [1] and is transitioning residential customers to private IPv4 addresses, and I'm not really sure how to set up a VPN on IPv4 now. I guess I need to set up a tunnel over IPv6 somehow?
Re:IPv6 enabled Christmas Tree
by syncsynchalt on Thursday December 15, 2016 @04:23PM
(#13188531)
I (hope to) see CGNAT as the stick - with v6 being the carrot that allows point-to-point apps and personal hosting to work reliably again.
That requires the ISP to offer v6, of course. I'm on Comcast which, say what you will about them, has been years ahead of everyone else for carrier-grade v6 support.
Re:IPv6 enabled Christmas Tree
by syncsynchalt on Thursday December 15, 2016 @04:21PM
(#13188516)
Each /8 only gives us about a month of runway. Not worth the bother.
2) would also help a lot with the upcoming IoT security shitstorm