5 ms·
Man. Modern internet standards are some serious turd-polishing. First you have HTTP2, which goes from a plaintext protocol to a binary protocol. But it's backw
by 0xbadcafebee 6y ago
Man. Modern internet standards are some serious turd-polishing.
First you have HTTP2, which goes from a plaintext protocol to a binary protocol. But it's backwards compatible with HTTP/1.1, because... nobody in the entire world will consider adding a new internet service port (81, 442, etc). In 100 years, we will still be using ports 80 and 443 - not because it's a good idea, but because literally every business in the world just refuses to update their software.
Then you have HTTP3. Where we do the above, but with a transport protocol. Literally nobody in the world wants to update their protocol stack, hardware, middleware, software, etc to add a new internet protocol. So we clamber on top of another protocol (UDP)'s back, to create a new protocol (QUIC), and then clamp yet another protocol (HTTP3) on that. So we have IP->UDP->QUIC->HTTP3. Which is backwards compatible with HTTP/1.1, because, you guessed it.... nobody wants to add ports 82 and 440.
The next step is going to be nobody wanting to update to IPv6. So they will probably implement IPv7, and stick it on top of whatever replaces UDP on top of IPv7. Then add on QUIC, and HTTP4. So it will be Ethernet->Arp->IPv4->UDPv4->IPv7->UDPv?->QUIC->HTTP4. All because nobody wants to update their software to use an existing, widely supported, network layer protocol. Or transport protocol. Or application protocol. Meanwhile, anything that wants to use the new features of the new protocols needs to implement 4 new protocols.
It's going to keep going like this until we have some new Apple-ish company come along with brand new everything, and everyone will flock to it, and the only way anyone will be able to use it will be to implement the new snowflake protocols. To even connect to the devices you'll need to have a license agreement with them and establish a secure connection that only that company has the keys for (because "privacy", because the internet standards are so ancient they never adapt fast enough and hackers basically compromise all web security). And those new things will become a de-facto standard. So we'll never have, say, a new TCP, but we'll have an AppleTCP.
- 40four 6y agoThat was an amazing rant. I really respect the level of detail and dedication to the rant.
- perryizgr8 6y ago> The next step is going to be nobody wanting to update to IPv6. I hate that IPv6 has such low usage, and it is exactly the same problem you describe. We have a protocol meant to replace IPv4 and eliminate several kludges (NAT) in the process. But guess what? People would rather keep on hacking the previous protocol to the extremes than learn and implement a newer better system. IPv6 is better than IPv4 in literally every sense, but your sysadmin can't be bothered to deviate even slightly from her decade old knowledge. So now we have all sorts of v4 in v6 tunneling, someone even talked about NAT for IPv6 (WTF?!). The end result is that v6 is incredibly complex due to these backward stuff. We need Apple to deprecate IPv4 like they did 32 bit. Otherwise companies will keep us locked into old technology for eternity.
- donatj 6y ago> IPv6 is better than IPv4 in literally every sense The addresses are harder to type, harder to yell across an office while setting up equipment, and impossible to remember. I honestly think this is it’s major failing that has prevented wider adoption. Aesthetics make a big difference, like it or mot, and IPv6 is far less accessible than IPv4. Beyond that, IPv4 is arguably generally simpler for someone not well versed in networking to get a baseline understanding of.
- njsubedi 6y agoI thought domain names were created so we don’t have to yell IP Addresses.
- deleted 6y ago[deleted]
- rswail 6y agoAnd yet if you set it up right, you don't need to type them or yell them or remember them. > Beyond that, IPv4 is arguably generally simpler for someone not well versed in networking to get a baseline understanding of. And BASIC is easier to program in than Rust if you're not well versed in programming. IPv6 addresses come in 3 flavors, unicast, anycast, multicast. Unicast addresses are for a single host, like a unique telephone number Anycast addresses go to the nearest receiver, like 911 Multicast addresses go to a group of hosts that are listening to the address for that group, like everyone streaming the same show on Netflix at the same time. Unicast addresses are either local to an interface/LAN/site, or global. Anycast addresses are global. Multicast addresses can be very local or across a wider area like a company or can be global. You can tell what sort of address it is by the start: * Multicast addresses start with "ff". * LAN addresses start with "fe". * Site (multiple LAN) addresses start with "fd" * Anything else other than "00" is global, but some have special meanings, like "2001" is used for documentation. There's a protocol called NDP that all the hosts use to give themselves addresses and find out how to connect to other hosts. That's a start. The fiddly bit twiddling details can come later.
- neurostimulant 6y agoFaster computers and network speed will encourage higher level of abstraction. We can't just leave all those extra performance on the table! Unused cpu cycles is wasted cycles, unused ram is wasted ram, and unsaturated bandwidth link capacity is wasted capacity! \s
- chrismorgan 6y ago> So we have IP->UDP->QUIC->HTTP3. Which is backwards compatible with HTTP/1.1, because, you guessed it.... nobody wants to add ports 82 and 440. I’m not sure what you mean by backwards-compatible here. HTTP/3 is not running over TCP port 80. It conveys the same semantics as older TCP HTTP, but that’s so applications can transparently use one or the other. I’m afraid your rant only goes downhill from there. Your IPv7 and UDPv4 are quite implausible, especially where you’ve put them in the stack. Look, we’re dealing with people here. You can’t just say “we’re dropping this thing you’ve been using for years, effective immediately”. We’re also dealing with capital investments: half the world is built upon stuff that only supports TCP and UDP at the layer on top of IP and can never support alternatives like SCTP. So replacing things takes a great deal of time. Therefore, sitting on top of existing protocols lets you do something rather than nothing. All progress in all fields is developed on top of existing things.
- 0xbadcafebee 6y ago> HTTP/3 is not running over TCP port 80 Yes, obviously it's not TCP, and obviously not that port. I explicitly stated "UDP->QUIC->HTTP3", which is only inaccurate because HTTP3 is an implementation of QUICv1. But it is still running over port 443. So my point is exactly the same. They refuse to change the port so that nobody has to agree to implement something crazy, like a new L4 protocol, or worse. (HTTP/3 does supports the ability advertise additional ports besides 443, but so does HTTP/1.1, in "Location: https://someurl:442/ https://someurl:442/" redirects, and still nobody has ever used anything but 443 for production) > Look, we’re dealing with people here. You can’t just say “we’re dropping this thing you’ve been using for years, effective immediately”. But we are saying "All the clients [that effectively 2 companies control] will be using this new thing, so unless you want to be left behind, grandpa, get on the bandwagon." There is plenty of muscle to start the process of upgrading legacy crap. Over 5-10 years we could get 90% adoption of an entirely new network stack. But we have to actually start going there by writing the standards with that intent. QUIC is a good start, but from the protocol stack's perspective it's a hack. 10-15 years ago, it simply would have been a new revision of SCTP. But the design is being pushed by an advertising company that just wants an 8% reduction in traffic so they can increase their shareholder dividend. They don't give a crap about evolving the stack to actually improve computing as a whole, which is what the standards are really intended for.