> I'm not comfortable with ipv6 in a world of Facebook and Google Instead you will get a world that's controlled by Amazon, Google and Azure, since they are ho

> I'm not comfortable with ipv6 in a world of Facebook and Google Instead you will get a world that's controlled by Amazon, Google and Azure, since they are hoarding as much IPv4 space as they can get their hands on (amazon alone has over 2 billion $ worth of IPv4 space). For startups it gets more and more expensive to acquire the necessary ip space. > providing plausible deniability as a core feature. Not really. In the non-carrier grade NAT (CGN) case (where you just do NAT at home) you still have a 1:1 mapping to your home network and the situation is exactly as good/bad as it is with IPv6. But with CGN the ISPs now have to keep logs on all connections being made for abuse tracking.. so much better (depending on the CGN implementation of course). > provides flow identification as part of the protocol. That's a good thing though and not any worse than before. Routers have to load balance traffic across multiple different paths and they do that based on flows (since load balancing one flow across multiple paths can cause reordering, etc.). And since src_host and dst_host is not enough entropy for that, typically routers also look at the TCP/UDP source and destination port to identify (with funny results when you use non-tcp/udp protocols or have different hashing algorithm between different routers). With the flow label the router just has to look at the IPv6 header and not concern itself whether it's a tcp or udp packet.