3 ms·

[Cue 32-bit IP snark] blah

• dboreham 4y ago
  The transition to IPv6 basically spanned my entire career (in networking, I had a previous career as a hardware engineer). My first task was to participate in the IPNg mailing list because the company I had just joined had an OSI stack, and one of the NG proposals was to bolt TCP on top of OSI's lower layers (TUBA). And this morning I spent some time on the phone to my ISP asking when/if they will roll out IPv6 in my area. 30 year span.
  • dsr_ 4y ago
    In 1994 I was talking to my colleagues about IPv6 and they asked how soon we would need to start transitioning. "Not this year," I said. "Maybe think about it next year in the budgeting process."
    • bombcar 4y ago
      IPv6 will roll out finally in 2049 or something, and immediately be replaced with IPv10.
      • xvilka 4y ago
        Why not IPv8?
        • bombcar 4y ago
          IPv7-9 will meet the same fate (or worse!) as IPv5 did.
    • Bluecobra 4y ago
      I believe that was around the time BGP migrated from v3 to v4 (CIDR support). It's pretty neat that change got pushed through so quickly. Granted the Internet was much smaller then (< 1500 AS's and 20K routes). Makes you think if work on IPv6 started earlier everyone could have migrated over in one swoop.
  • dekhn 4y ago
    My latest internet provider (AT&T GigE) definitely supports IPv6. I also noticed that every device in my house that I care about (IE, all the laptops, phones, TV streamers, desktops, and servers) supported it. AT&T gives me something like a /64. So i decided to finally do IPv6 at home. Even turn IPv4 off. Shortly after, I turned IPv4 back on and disabled the extra IPv6 support in my router. What I found was that everything in my house worked more or less fine, but that IPv6 to the outside was a problem because few websites support IPv4. So you need to be dual stack or run a proxy.