Some ancient protocols get replaced gradually though. Look at http3 not using TCP anymore. I mean at least it’s something.
Comment on It's not DNS
cm0002@lemmy.world 10 months ago
Does anyone else have the thought that maybe it’s time to just replace these 30+ year old ancient protocols? Seems like the entire networking stack is held together with string and duct tape and unnecessarily complicated.
A lot of the decisions made sense somewhat in the 80s and 90s, but seems ridiculous in this day and age lmao
words_number@programming.dev 10 months ago
elmicha@feddit.de 10 months ago
HTTP3 uses UDP, which is 6 years younger than TCP.
words_number@programming.dev 10 months ago
Nope, it uses a protocol on top of UDP called QUIC. If you count underlying protocols further down the stack, obviously all of them are really old.
Dangdoggo@kbin.social 10 months ago
I definitely would love to see a rework of the network stack at large but idk how you'd do it without an insane amount of cooperation among tech giants which seems sort of impossible
ryannathans@aussie.zone 10 months ago
Wait till you hear about when ipv6 was first introduced (90s) and how 50% of the internet still doesn’t work with it.
Businesses don’t want to change shit that “works” so you still have stuff like the original KAME project code floating around from the 90s.
hansl@lemmy.world 10 months ago
Data Link layer be pretty stable to be fair ^_^
Railing5132@lemmy.world 10 months ago
I may be waaaay off here, but the internet as it exists is pretty much built on DNS, isn’t it? I mean, the whole idea of DARPANet back in the 60s and 70s was to build a robust, redundant, and self-healing network to survive nuclear armageddon, and except when humans f it up (intentional or otherwise), it generally does what it says on the tin.
Now, there’s arguments to beade about securing the protocol, but to rip and replace the routing protocols, I think you’d have to call it something other than the Internet.
Inktvip@lemm.ee 10 months ago
Making a typo in the BGP config is the internet’s version of nuclear Armageddon
somnuz@lemm.ee 10 months ago
Same unfortunately goes for a big chunk of the law on a global scale… Constant progress, new possibilities and technologies, changes in general are really outpacing some dusted and constantly abused solutions. Every second goes by and any “somehow still holding” relic is under more pressure. As a species we can have some really great ideas but the long-term planning or future-proofing is still not our strongest suit.
NaibofTabr@infosec.pub 10 months ago
The more you learn about network technology the more you realize how cobbled together it all is. Old, temporary fixes become permanent standards as new fixes are written on top of them. Apache, which was the most widely used web server for a long time, is literally named that because it was “a patchy” server.
The open nature of IP is what allows such a varied conglomerate of devices to share information with each other, but it also allows for very haphazard connections. The internet is a functional example of building the airplane while you’re flying it. We try to revise the standards as we go, but we can’t shut the whole thing down and rebuild it from scratch. There are no green fields.
It has always been so. It must be so. It will continue to be so.
Yearly1845@reddthat.com 10 months ago
When 9/11 happened, it took out a major data center, and people were panicking that it was going to take down the internet. But the DNS network detected that and started routing traffic away from there. It may be cobbled together, but it’s robust and resilient.
wahming@monyet.cc 10 months ago
You can nuke the Internet, just don’t misconfigure a bgp router
geekworking@lemmy.world 10 months ago
Fat fingering BGP config has nuked the internet quite a few times already.
NaibofTabr@infosec.pub 10 months ago
I thought the internet was at Big Ben?
TheMadIrishman@sh.itjust.works 10 months ago
Nothing quite as permanent as a temporary fix!
xpinchx@lemmy.world 10 months ago
Very cool post, thanks for sharing