3 ms·

> Adoption has been declining for years. Source? > Many devices don't support it. Source? > Many services seemingly support it but break in strange ways. G

> Adoption has been declining for years. Source? > Many devices don't support it. Source? > Many services seemingly support it but break in strange ways. Got any examples? > And not to mention it's a subtle and yet powerful privacy attack vector. This is the only statement you've made that has any merit, and even then very little. Privacy Addresses have been a thing for a while, and most OS's support it. No longer are there stable addresses being generated from the MAC address, and all outbound connections are now on randomized addresses from the /64 that is announced through SLAAC. Just like IPv4 having a single address for a household, IPv6 has a /64 per household (although many ISP's let you request more if you want). IPv6 is growing, more and more traffic is going over IPv6 and it is not likely to go away any time soon.

zamadatix 4y ago
Taking some points from their side not because I necessarily agree with the conclusion but just because this comment comes off a little strong: Adoption hasn't been declining by any measure but the adoption rate isn't as high as it was 5 years ago. Of course eventually the rate has to slow down because there is less and less to change over so that doesn't mean much. Overall though adoption has continued to increase without any long term dips. Many devices don't support it is probably one I consider true though. It's getting way better as the years go on but it's fair to say the world isn't past IPv4 only devices in households by any measure. Typically embedded products are the worst. Home security stuff, point of sale gear, older or just crappy media devices, oddly some IoT type devices like a fridge. Plenty of gear also supports it but just very poorly. Of those that do not all understand NAT64 either so while they may support IPv6 but they don't necessarily work without IPv4 (this also getting better as more services move to supporting IPv6 too). SIP and WebSocket are examples of some protocols that can break services under NAT64, especially with so much of the web being v4 only. They should be fine if the world ever moves 100% to IPv6 though. The era of misconfigured AAAA records wreaking havoc thankfully seems to have come to an end. I don't have anything to add on the privacy discussion, I think you nailed it there.
- winstonprivacy 4y ago
  > Many devices don't support it is probably one I consider true though. It's getting way better as the years go on but it's fair to say the world isn't past IPv4 only devices in households by any measure. Typically embedded products are the worst. Home security stuff, point of sale gear, older or just crappy media devices, oddly some IoT type devices like a fridge. Plenty of gear also supports it but just very poorly. Of those that do not all understand NAT64 either so while they may support IPv6 but they don't necessarily work without IPv4 (this also getting better as more services move to supporting IPv6 too). This is very much the case. I used to compile statistics about various devices for our network gateway. ipv6 support was very hit or miss and was the root cause of many spurious support tickets.
winstonprivacy 4y ago
Here you go: https://www.potaroo.net/ispcol/2022-02/ipv6-fig4.png https://www.potaroo.net/ispcol/2022-02/ipv6-fig4.png also: https://www.potaroo.net/ispcol/2022-02/ipv6-fig5.png https://www.potaroo.net/ispcol/2022-02/ipv6-fig5.png You can answer the rest of your own questions. I am not your personal Google.
- zamadatix 4y ago
  Allocations describe how many new blocks are being assigned. For adoption you'd want something like this link https://bgp.potaroo.net/v6/as2.0/index.html https://bgp.potaroo.net/v6/as2.0/index.html which displays the number of IPv6 advertisements at a given time, including assignments that were made in previous years from prior allocations.
- icehawk 4y ago
  When you look at the same graph for IPv4, its pretty obvious that graph isn't showing data that supports the conclusions you're drawing from it: https://www.potaroo.net/ispcol/2022-01/addrfig2.png https://www.potaroo.net/ispcol/2022-01/addrfig2.png

zamadatix 4y ago

Taking some points from their side not because I necessarily agree with the conclusion but just because this comment comes off a little strong: Adoption hasn't been declining by any measure but the adoption rate isn't as high as it was 5 years ago. Of course eventually the rate has to slow down because there is less and less to change over so that doesn't mean much. Overall though adoption has continued to increase without any long term dips. Many devices don't support it is probably one I consider true though. It's getting way better as the years go on but it's fair to say the world isn't past IPv4 only devices in households by any measure. Typically embedded products are the worst. Home security stuff, point of sale gear, older or just crappy media devices, oddly some IoT type devices like a fridge. Plenty of gear also supports it but just very poorly. Of those that do not all understand NAT64 either so while they may support IPv6 but they don't necessarily work without IPv4 (this also getting better as more services move to supporting IPv6 too). SIP and WebSocket are examples of some protocols that can break services under NAT64, especially with so much of the web being v4 only. They should be fine if the world ever moves 100% to IPv6 though. The era of misconfigured AAAA records wreaking havoc thankfully seems to have come to an end. I don't have anything to add on the privacy discussion, I think you nailed it there.

winstonprivacy 4y ago
> Many devices don't support it is probably one I consider true though. It's getting way better as the years go on but it's fair to say the world isn't past IPv4 only devices in households by any measure. Typically embedded products are the worst. Home security stuff, point of sale gear, older or just crappy media devices, oddly some IoT type devices like a fridge. Plenty of gear also supports it but just very poorly. Of those that do not all understand NAT64 either so while they may support IPv6 but they don't necessarily work without IPv4 (this also getting better as more services move to supporting IPv6 too). This is very much the case. I used to compile statistics about various devices for our network gateway. ipv6 support was very hit or miss and was the root cause of many spurious support tickets.

winstonprivacy 4y ago

Here you go: https://www.potaroo.net/ispcol/2022-02/ipv6-fig4.png https://www.potaroo.net/ispcol/2022-02/ipv6-fig4.png also: https://www.potaroo.net/ispcol/2022-02/ipv6-fig5.png https://www.potaroo.net/ispcol/2022-02/ipv6-fig5.png You can answer the rest of your own questions. I am not your personal Google.

zamadatix 4y ago
Allocations describe how many new blocks are being assigned. For adoption you'd want something like this link https://bgp.potaroo.net/v6/as2.0/index.html https://bgp.potaroo.net/v6/as2.0/index.html which displays the number of IPv6 advertisements at a given time, including assignments that were made in previous years from prior allocations.
icehawk 4y ago
When you look at the same graph for IPv4, its pretty obvious that graph isn't showing data that supports the conclusions you're drawing from it: https://www.potaroo.net/ispcol/2022-01/addrfig2.png https://www.potaroo.net/ispcol/2022-01/addrfig2.png