5 ms·

I first learned ipv6 22 years ago when I did my CCNP. Since then we've been two years away from migration every year.

by woleium 5y ago

betaby 5y ago
Close to 90% mobile phones in USA/Canada have IPv6 connectivity for about 5 years.
- bikingbismuth 5y ago
  My home ISP gives me an IPv6 address as well. Much of the internal infra that I use at work has AAAA records in our local DNS. I feel comfortable saying IPv6 is here.
  - thecybernerd 5y ago
    I wish Verizon would start offering IPV6 across their wireline footprint.
    - tomschlick 5y ago
      They are. I was part of the test rollout of IPv6 when I lived in Richmond, VA last year. It worked flawlessly so I'd assume they should be set for a greater rollout sooner rather than later.
      - deathanatos 5y ago
        When was that? It's been "coming soon" on Verizon's own FAQ[1] for almost half a decade now. I'm in one of the major MSAs along the eastern megalopolis, and there's no IPv6 here. [1]: https://web.archive.org/web/20171220092540/https://www.verizon.com/support/residential/internet/getting-started/learn-about-ipv6 https://web.archive.org/web/20171220092540/https://www.veriz...
        tomschlick 5y ago
        Last year. I got it at the beginning of 2020 IIRC and I moved from VA to another state in sept 2020.
bushbaba 5y ago
I’ve often wondered if ipv6s less human readable addresses is the primary cause. I dread using and interacting with ipv6, compared to ipv4. Sure ipv6 solves a lot of scaling challenges, but it is so much harder to grock at first glance.
- ashton314 5y ago
  Address abbreviation helps a bunch. IPv6 (not an expert, but I’m in a class right now!) suffers from severe 2nd system syndrome: it overhauls DHCP in a totally convoluted way, overhauls so much of how the IP layer works, etc. It really is a mess.
  - 1ncorrect 5y ago
    I think it would have been better to label everything that DHCPv6 covers with an entirely new name. Its functionality is fine for what it’s tasked to do, and much of the confusion I’d argue stems from those who (think they) know IPv4 trying to map their understanding to IPv6 unmodified.
- ospray 5y ago
  For all of it's faults Port Address Translation (NAT) sure has a way of making the address size more manageable.
  - hansel_der 5y ago
    we managed to connect a few billion devices using about 200mio addresses and a protocol that was designed for a few thousand hosts. successfull technology indeed.
- jml7c5 5y ago
  It's a silly bikeshed, but I wish they'd gone for hyphens as separators rather than colons. There's something about [abcd-ef12-3456-7890-abcd-ef12-3456-7890] that's nicer to read than [abcd:ef12:3456:7890:abcd:ef12:3456:7890]
TrumpRapedWomen 5y ago
The fundamental mistake was not making IPv6 backwards compatible with IPv4. You can't just migrate to IPv6, you need to run dual stack which means twice as much work a lot more complexity. I'm 40 and don't expect to ever be able to not need an IPv4 IP to browse the Internet.
rjsw 5y ago
I have had native IPv6 from my ISP for 11 years now.
- pvtmert 5y ago
  Meanwhile, entire countries missing it today...
  - hansel_der 5y ago
    and there are those having ipv6 access from the isp but disabling it in the router because it caused some (badly timed) fuckups in the past.
harshreality 5y ago
Over 30% global adoption for google users, to the extent of having a public ipv6 address and using ipv6 preferentially: https://www.google.com/intl/en/ipv6/statistics.html https://www.google.com/intl/en/ipv6/statistics.html
- usr1106 5y ago
  If you watch the graph in smaller time scale you see adoption is higher on weekends than on weekdays. I guess that means consumers using Google and similar from their mobile phones have a high rate of adoption. They did not do it themselves. While the average medium (and why not big) company IT department has not started to do anything and is IPv4 only. Seen in the graph when people work Monday to Friday and especially around Christmas.

I first learned ipv6 22 years ago when I did my CCNP. Since then we've been two years away from migration every year.

betaby 5y ago

Close to 90% mobile phones in USA/Canada have IPv6 connectivity for about 5 years.

bikingbismuth 5y ago
My home ISP gives me an IPv6 address as well. Much of the internal infra that I use at work has AAAA records in our local DNS. I feel comfortable saying IPv6 is here.
- thecybernerd 5y ago
  I wish Verizon would start offering IPV6 across their wireline footprint.
  - tomschlick 5y ago
    They are. I was part of the test rollout of IPv6 when I lived in Richmond, VA last year. It worked flawlessly so I'd assume they should be set for a greater rollout sooner rather than later.
    - deathanatos 5y ago
      When was that? It's been "coming soon" on Verizon's own FAQ[1] for almost half a decade now. I'm in one of the major MSAs along the eastern megalopolis, and there's no IPv6 here. [1]: https://web.archive.org/web/20171220092540/https://www.verizon.com/support/residential/internet/getting-started/learn-about-ipv6 https://web.archive.org/web/20171220092540/https://www.veriz...
      - tomschlick 5y ago
        Last year. I got it at the beginning of 2020 IIRC and I moved from VA to another state in sept 2020.

bushbaba 5y ago

I’ve often wondered if ipv6s less human readable addresses is the primary cause. I dread using and interacting with ipv6, compared to ipv4. Sure ipv6 solves a lot of scaling challenges, but it is so much harder to grock at first glance.

ashton314 5y ago
Address abbreviation helps a bunch. IPv6 (not an expert, but I’m in a class right now!) suffers from severe 2nd system syndrome: it overhauls DHCP in a totally convoluted way, overhauls so much of how the IP layer works, etc. It really is a mess.
- 1ncorrect 5y ago
  I think it would have been better to label everything that DHCPv6 covers with an entirely new name. Its functionality is fine for what it’s tasked to do, and much of the confusion I’d argue stems from those who (think they) know IPv4 trying to map their understanding to IPv6 unmodified.
ospray 5y ago
For all of it's faults Port Address Translation (NAT) sure has a way of making the address size more manageable.
- hansel_der 5y ago
  we managed to connect a few billion devices using about 200mio addresses and a protocol that was designed for a few thousand hosts. successfull technology indeed.
jml7c5 5y ago
It's a silly bikeshed, but I wish they'd gone for hyphens as separators rather than colons. There's something about [abcd-ef12-3456-7890-abcd-ef12-3456-7890] that's nicer to read than [abcd:ef12:3456:7890:abcd:ef12:3456:7890]

TrumpRapedWomen 5y ago

The fundamental mistake was not making IPv6 backwards compatible with IPv4. You can't just migrate to IPv6, you need to run dual stack which means twice as much work a lot more complexity. I'm 40 and don't expect to ever be able to not need an IPv4 IP to browse the Internet.

rjsw 5y ago

I have had native IPv6 from my ISP for 11 years now.

pvtmert 5y ago
Meanwhile, entire countries missing it today...
- hansel_der 5y ago
  and there are those having ipv6 access from the isp but disabling it in the router because it caused some (badly timed) fuckups in the past.

harshreality 5y ago

Over 30% global adoption for google users, to the extent of having a public ipv6 address and using ipv6 preferentially: https://www.google.com/intl/en/ipv6/statistics.html https://www.google.com/intl/en/ipv6/statistics.html

usr1106 5y ago
If you watch the graph in smaller time scale you see adoption is higher on weekends than on weekdays. I guess that means consumers using Google and similar from their mobile phones have a high rate of adoption. They did not do it themselves. While the average medium (and why not big) company IT department has not started to do anything and is IPv4 only. Seen in the graph when people work Monday to Friday and especially around Christmas.