The IPv6 Adoption Curve
community.infoblox.com
community.infoblox.com
It was only after doing this that I realized the problem with IPv6 adoption in the US: the network sucks! Most ISPs (including mine) are using 6rd gateways to get their customers onto the IPv6 backbone. The gateway servers are poorly placed (rarely local) and totally overloaded. The performance was so bad that it was making my everyday web browsing experience feel broken. I killed v6 at home and haven't looked back.
Maybe some day ISPs will do a proper deployment with real routing and I will try it again.
The lesson learned from 6bone, HE, 6to4, 6rd, and Teredo is that we need native IPv6 or nothing. Tunneled IPv6 is worse than no IPv6 due to its unreliability.
They are essentially donating IPv6 bandwidth to the tune of 50Mbit per tunnel.
There exist this project that track performance for v6 vs v4. In some countries v6 has above performance to v4, in others places it is worse. You seems to had the bad luck of getting the worse end of the variance.
I don't know what "a couple of years ago" is, but all tier-1 ISPs have IPv6 backbones. There should be no reason for your access ISP to have to tunnel anything to get to a tier-1.
Your statement "Most ISPs (including mine) are using 6rd gateways to get their customers onto the IPv6 backbone" is kind of a red flag. If ISPs aren't connected to a backbone, can you even call them an ISP?
Most of the big US ISPs are using 6rd: AT&T, CenturyLink, and Cox. As far as I know, Comcast is the only one with true IPv6 to the curb but I might be wrong about that.
A while later (2014?), I was annoyed by my poor bandwidth. A bit of sleuthing revealed that IPv6 was the culprit: turning that off in the ISP's control panel doubled my bandwidth!
I know that a lot of internet routers didn't have IPv6 acceleration. IPv6 packets jumped out of the (fast) data plane to be processed by the (slower) control plane. At the time this made sense considering the rarity of IPv6. I suppose Free, being a cheap ISP, were still using these older routers.
In 2013, the telephony-focused router company I worked for still hadn't implemented data-plane processing of IPv6, because there was no requirement from it.
Hopefully in 2017, driven by Comcast or other IPv6-dependant phone operators, most routers do IPv6 acceleration.
Even the discontinued Catalyst 6500, which was used (and still is) by a lot of ISPs with the SUP720 supervisor, can do native IPv6.
I think you are completely wrong about this. Routers with native IPv6 were available 15 years ago, and are already getting pulled out to be replaced by the new stuff.
The reality is that, that ISP tier 1s use either Juniper MX or Cisco ASR9000 routers. These routers have good IPv6 performance.
I remember reading about Facebook's migration as a great case study. One example problem they had was that their switches couldn't handle getting a BGP feed with IPv6 addresses when they had not been configured for IPv6.
In other words, when they added IPv6 to their BGP feeds they crashed an entire network segment worth of switches.
This is another massive headache w.r.t IPv6 switchover: all the bugs and edge cases we've found with IPv4 thirty years ago are all brand new wild country problem with IPv6.
Now, we're adopting IPv6 in earnest, but everybody is whining that they want to hang onto NAT.
So, before IPv6 got deployed, everybody shot themselves in the left foot by deploying NAT. And, now that IPv6 is deployed, they continue shooting themselves in the right foot by hanging onto NAT.
https://www.a10networks.com/resources/glossary/carrier-grade...
There's a fixed pool of IP Addresses that can be allocated. When that allocation pool runs out, no more can be allocated. Allocation occurs in blocks at a very high level and then at subsequent levels more sub block allocation happens.
The INAN ran out of IPs to hand out. That doesn't mean that all of the IPs have been assigned to physical devices attached to the internet. For example the US Government Agencies have tons of IPs they aren't using but that had been previously allocated to them decades ago and can't be taken back.
Also some under-utilized IPv4 address blocks have been recently re-claimed. MIT recently sold off half of its class A to Amazon:
https://www.networkworld.com/article/3191503/internet/mit-se...
And garbage like this is why I cannot wait for the IPv6-only future, CIDR let us stall IPv4 address exhaustion but it has caused severe bloating in routing tables. Considering an IPv6 route at the internet level is capped at 64-bits (the max length of a proper network prefix, you can technically do smaller ones but WHY, and nobody will take your BGP advertisement for it either) I expect even with a 2X increase in size occupied by each individual route the size of a full BGP table is going to be dramatically smaller.