RFC 1631: The IP Network Address Translator (NAT)
datatracker.ietf.org
This memo proposes another short-term solution, address reuse, that complements CIDR or even makes it unnecessary. The address reuse solution is to place Network Address Translators (NAT) at the borders of stub domains. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

From the conclusion:

NAT may be a good short term solution to the address depletion and scaling problems. This is because it requires very few changes and can be installed incrementally. NAT has several negative characteristics that make it inappropriate as a long term solution, and may make it inappropriate even as a short term solution. Only implementation and experimentation will determine its appropriateness.

  • @laughterlaughter
    5•7 months ago

    One hour video. Jesus. tl;dw (generated by AI - disclaimer):

    " The speaker in the YouTube video discusses why IPv6 adoption is slow due to technical complexities, high costs, and lack of immediate benefits for businesses. He talks about the challenges of maintaining both IPv4 and IPv6, why businesses are hesitant to adopt IPv6, its technical benefits, lack of backward compatibility with IPv4, and the importance of universal adoption for success. Some large companies have not adopted IPv6, and there are concerns about minimal performance gains and transition costs, leading to a prediction of IPv4 and IPv6 coexisting for the next 20 years. "

    • @[email protected]
      5•7 months ago

      Next 20 years? Dude, I was being taught IPv6 back in 1997, as part of my network course. It was supposed to be the future back then, and so we were trained, expecting to have to implement it wherever we’d go work.

      Yeah… I didn’t end up in networks, but I sure as shit did not see it used even once in my career so far. Not a single time. It’s kinda hilarious, really.