If you turn on IPv6 in a typical home today over half the traffic will move to IPv6. In the future the shift will be greater.

For Comcast, this means that ~15% of their traffic from the home is IPv6, and the overall home traffic is ~6Tbps.

One packet in six is IPv6.

The ability to more easily diagnose network problems without having to deal with the consequence of address and port translations.

A default deny in firewall is as easy to manage as a NAT and it doesn't mangle the addresses or ports.

Truly, you should be able to connect a box to the Internet without a firewall and it should be fine. If it isn't the manufacture has not done due diligence. That said mistakes happen. Keeping up to date with maintenance releases is the way to address this issue.

Governments could help here by requiring manufactures to supply security fixes indefinitely for any internet connectable software. For consumer electronics this could be 20 years or more. Note the fix may be "upgrade to release X" where X involves a feature jump.

And you can to this at the application layer. You do not need a firewall to restrict service to particular clients.

Which shows more about you local network that slashdot.
Yes. I do have IPv6 enabled and have done so for the last decade.

% dig -6 slashdot.org +short
216.34.181.45
%

Given the size of usb sticks. Searching a coin box would be reasonable.

You still haven't show why a commercial operator should require a certificate when a hobbyist doesn't for the same class of drone. If a class of drone requires equipment to be fitted it should be independent of whether the drone is commercially operated or not.

The commercial operating certificate is to protect the fare paying passengers by ensuring that you have the requisite experience.

Last time I looked drones were not carrying passengers. The two situations are in no way comparable.

Which is why you also put in a speed camera on such lights as well as a red light camera with a big sign saying "Red Light - Speed Camera". All new red light cameras are both speed and red light camera here with the old red light cameras being retrofitted with speed timing loops.

If you speed up to make the light you get a speeding fine. Traffic actually obeys the speed limits as there are enough of these to make it a pain to speed up and then slow down for the intersections.

Bridges have massive error tolerances built into the design. A single bolt/rivet failing won't bring down a bridge. Bridges are designed to cope with these sorts of failures.

Software as almost zero tolerance for errors. A single bit error can destroy a program.

Firstly use ULA for local stability.

As for DNS, UPDATE + TSIG works with just about all name servers as does UPDATE + SIG(0).

Mac's already support UPDATE + TSIG.

255.255.255.255.255.255.255.255.255.255.255.255.255.255.255.255 vs ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff

Which would you rather type, read etc.

Comcast has over 25% of their network IPv6 enabled as of November last year. This is much more that "3 cities".

As for taking back IPv4 addresses, that has to be the most ludicrous thing I have heard. There is a huge amount of IPv4 only content out there which you need IPv4 addresses to reach. Now you can make the consumer IPv6 only by use NAT64 + DNS64 to reach this content but you still need IPv4 addresses on the public side of the NAT64. Additionally NAT64 breaks functionality you get with having direct, unshared, IPv4 connectivity.

About 3.5% of Google's traffic is IPv6. This is more than double what it was last year at this time. If the grow continues on this curve we will be at 10% within a year and a half. This sort of traffic is more than enough for sites to enable IPv6.

If you can enable IPv6 at home over 50% of typical home usage is IPv6 (Google and FaceBook). There is no reason for Consumer ISP's to not enable IPv6 as there is enough volume to make it worthwhile.

IPv6 was designed to co-exist with IPv4. You give new hardware a IPv6 address as well as a IPv4 address and after 10 or so years all your machines have both IPv4 and IPv6 addresses and there are basically no IPv4 only machines left. This would have worked if CPE vendors shipped IPv6 capable routers and ISP
enabled IPv6 on the customer links.

Today almost all the cell phones and general purpose computers support both IPv4 and IPv6. Linux, Windows, MacOS, iOS, *BSD, Solaris, Android all support IPv6. What hasn't happened is turning on IPv6 on the ISP links and that is mainly but not solely due to lack of IPv6 in home routers.