• knower@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      18
      ·
      1 year ago

      I used to study networking, albeit at a pretty beginner level. IPv6 has been around for nearly 30 years at this point, so I’d be surprised if the hardware github uses doesn’t support it. The impression I got was that it’s pretty easy to extend an IPv4 address space so there isn’t any rush to make a large scale move to IPv6 everywhere.

    • chaospatterns@lemmy.world
      link
      fedilink
      English
      arrow-up
      11
      ·
      1 year ago

      It’s not generally a hardware problem. It’s a resourcing problem. Companies like GitHub will have complex software and architecture. IPv6 requires them to get a pool of IP addresses, come up with an IP address management strategy, make sure all hosts have IPv6 addresses meaning that now provisioning systems and tooling to management DNS has to plumb IPv6 addresses through too.

      Then the software stack has to support it. Maybe their fraud detection or auditing systems have to now support IPv6 which means changes to API schemas.

      None of this is a good reason why they shouldn’t do it, but I’ve had to make similar decisions at my job as a software engineer on what looks to be simple but actually requires changes across systems.