Re: @Sebby - Why did the IPv6 rollout have to be such a mess as to encourage these problems?
> Actually because real-life companies (banks as an example) have critical mission systems and other tens of thousands of host running just fine on their internal IPv4 networks
But the point is, they don't have to change their existing internal networks if they don't want to. They can continue using their existing IPv4 allocations, or use RFC1918 addresses.
But the pubic facing systems are a different matter - these are all relatively new (how many banks have old online banking portals ?) It's quite possible to upgrade the public facing portals while keeping IPv4 only on internal systems.
And while we know that many of the internal critical systems are old, IPv6 has been around for something like a couple of decades. It's because people have stuck their head in the sand (or up their backsides) for a couple of decades that we are in the current situation and still talking about methods (carrier grade NAT, where's the barf bucket ?) to try and keep IPv4 going - and often it's the same people putting effort into this that are still dragging their heels and trying to pretend that the rumbling noise they can feel through that shiny bit of metal they are standing on really isn't the IPv6 train coming down the line.
Biting the hand that feeds IT
