this post was submitted on 29 May 2024
302 points (99.0% liked)

Programmer Humor

19817 readers
70 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
302
Happy 30th birthday to RFC 1631 ("NAT"), the "short term solution" we all rely on (datatracker.ietf.org)
submitted 6 months ago by [email protected] to c/[email protected]
39 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 10 points 6 months ago (3 children)

A few people need to get off their horses and come up with and agree to IPv4². It's exactly the same as IPv4 except there's 2 more octets of address space - 48bits for addresses*. Job done. You'd see wide spread adoption in under 2 years and then we can forget about it all and move on with our lives safe from the clutches of IPv6.

I don't give a crap that doesn't neatly fit into 32 or 64 bit architectures. It's more than doable at plenty fast speed and it keeps everything manageable.

[–] [email protected] 17 points 6 months ago

And what would be the advantage? It wouldn't be routable through legacy systems, and you'd run out of addresses in a couple of years again.

[–] [email protected] 9 points 6 months ago (4 children)

What's bad about IPv6?

[–] [email protected] 16 points 6 months ago

Nothing. It fixes the myriad of horrible hacks that are required for ipv4 to somehow still hang on.

Of course companies are sad because transition costs money, even though as usual the open source community did most of the work for them.

[–] [email protected] 5 points 6 months ago

I have no idea but they look complicated!

[–] [email protected] 2 points 6 months ago

It tried to fix everything wrong with IPv4, like shitty multicasting. This made it extra complicated.

If it had just been 128-bit addresses, it probably would have been widely deployed in the 90s. Don't need to bother at this point, though, just get it done.

[–] [email protected] 1 points 6 months ago (1 children)
[–] [email protected] 5 points 6 months ago (1 children)

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 points 6 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.

[–] [email protected] 4 points 6 months ago

If we rolled back the clock to 1998 or so, that'd probably be worthwhile. At this point, everything is set for IPv6, and we just need to do it.