It should be "So Many I can't locate them all". Or. "So many, but I know exactly where they are".
We're not there yet. You can check the activities in sunset4 wg at ietf about disabling ipv4.
I see consistently faster times with my IPv6 vs IPv4 with my native service at home, even with just pings. This seems to be the norm with most networks. If you are using a tunnel broker, such as he.net or otherwise you are most likely going a longer path with those artificial midpoints. Also, your browser may be broken as it doesn't implement rfc6555 properly.
Perhaps you missed world IPv6 day when they both jumped at the same time to enable their front pages? There are a lot of things that don't work right in an IPv6 only world, such as Skype but the list of things that doesn't work is getting shorter. If you take a look at the statistics it's quite encouraging to see a steady growth curve.
 for your assertion. Been deploying IPv6 at a major ISP/carrier for 13 years now. If you bought the wrong stuff or didn't ask for IPv6, you may be right but the proper gear is out there and doesn't cost any more. I can even get IPv6 over my VPN connection.
The issue is one of mentality and training. Above someone says "turned off IPv6, problem went away". That's certainly one way to say "I blame IPv6". They didn't troubleshoot the problem. Perhaps it's a DNS problem or something else they haven't properly diagnosed. Without actually understanding how the protocols work, one is doomed to failure and blame.
When you look at the major players who have deployed IPv6, including Netflix, Google, Yahoo to name but a few and compare that with the statistics on the cellular side... VZ Wireless sees over 60% IPv6 traffic. With the coming "great mobile demotion" tomorrow, it's more likely those devices if they come over 3GPP/LTE will perhaps visit you via IPv6 than via IPv4 if you properly enable your front door. If you are a CDN customer, it's a button to turn on IPv6. Cloudflare has it on by default, Akamai you have to ask, same for Limelight.
The edge protocols have only really reached maturity in the past 2 years to deliver a connection to the edge or your home. CPE lifetime is somewhere in the 3-7 year range, we are still another generation away from having the home properly IPv6 enabled, but it's more often just going to be there and "just work". There are a lot of IT workers who haven't invested enough to learn about the subtle differences in V6, such as NDP vs ARP, etc and will block all ICMPv6 not understanding they are blocking NDP so can't see a response to their NS. This too will pass much in the same way as those who only knew appletalk or IPX routing.
Not really, Fiber is the same cost to put in the ground and you can get fusion splicers for around $1500 these days. The cost is all in putting the cable into the ground. If you are touching the earth, that's the expensive part. Permits (which understandably people want to leverage Title II to assist with repairs/upgrades/deployment) can actually be 1/3rd of the cost. next 1/3rd is labor and last 1/3rd is the fiber.
There is a cultural split here, many people want things for the cheapest possible amount, or will switch for the next "deal" in 1-2 years because it saves them $5/mo and comes with a gift-card, but they have to take the day off for an installer to come by, costing them more than their savings in lost wages. Some people flat out value their time at $0.
The community of Slashdot may be willing to pay $70/mo for google fiber plus $100/yr for Prime, $96/yr for Netflix, etc. The cost per home to wire for fiber is about $2500, if you think the cell phone subsidy model in the US is an issue, try getting someone to write a check for that. Shared tenant buildings like Apartments are quite complex, including in NYC as the telco can get access to the building riser/copper but would have to install fiber. Who is responsible for the in-building wiring in that case?
AT&T has fiber about 1200 feet from me but the only speeds offered are 768k and 1.5M down. I would be willing to pay for a FTTH install, but there is no way for them to figure out how to do it. Last time I got a quote for a build, it was about $60k to build fiber. Moving easily becomes an option at that point.
It's not farmer john you have to worry about, that long strech of fiber likely already exists, and they can give right of way much easier. It's the Township, County and Road Commission that has got to get paid for permits and labor costs, not the cost of the fiber.
Gardening leave is usually about having time for someone else to be forced to look at their work and ask questions while they're still around on payroll.
I'm actually surprised more people don't use something like RFC1760 to authenticate with systems. The passwords are one-time use and back in the days before SSH this is what we used to get behind the packet filtering to servers when using cleartext authentication.
The challenge here is the other costs that are unaccounted for. Sure, you see power at 5c/10c per KWH, but all the other parts cost money as well, such as poles. Sure, the pole may be split in cost between the power, phone and cable companies, but that's still an expensive asset. http://www.dailyherald.com/art... provides a view into what this costs to be maintained. If a pole costs $1-3k, how many are you sharing the cost of as part of the rate. This is part of the "ugly profit" people gripe about with some of these shared assets, both in an electric network and the ways the bits reach your screen here.
If I get to a bill of zero due to investing and net-metering, someone else is going to be paying for those grid parts either in higher rates, or I need to pay for some usage of that giant battery network. No free lunch, etc..
I've been working on various aspects of the CPE equation for almost 2 years now as part of the various OpenResolverProject, OpenNTPProject, and other related aspects. Most CPE can't even do DNS correctly, let alone securely.
Take Netgear for example, they can't even process RFC1035 4.2.2 correctly to say a client should support DNS over TCP (it's not just for zone transfers), but instead of just not responding, or sending back some error that allows the DNS client to try the next resolver it has, you get it sending REFUSED: https://www.cloudshark.org/cap...
These devices are unmaintained outside of the few who actually upgrade them, and it's most likely still got default passwords on it causing all sorts of other possible pain and xss abuse/malware concerns. This is only going to get worse as more things have an IP address and communicate with the rest of the world.
https://www.youtube.com/watch?... should help explain it to you.
This isn't possible, nor should it be.
Actually, I know of some people who have built their own network appliances to perform this task. It's feasible and can work but requires encapsulate and decapsulation on each end. You can MSS clamp for TCP and timestamp/reassemble the UDP frames. Not impossible, but certainly requires effort. The people I know who did this was for redundancy between DSL + Business DOCSIS services so they would get the fastest performance of each direction from their links with redundancy should one fail.