13 ms·
> One of the great things about IP is that it's extensible, there's still room for protocols other than UDP/TCP, you can still write something new and better, o
by jeroenhd 5y ago
> One of the great things about IP is that it's extensible, there's still room for protocols other than UDP/TCP, you can still write something new and better, or a fixed TCP, and install it along side the existing protocols - of course getting everyone to accept it and use it will be difficult
Sadly, this isn't the case anymore since shitty middleboxes have taken over the internet. Using extensibility features in all kinds of protocols (be it TCP, TLS, UDP, or any other three letter protocol, really) causes middleboxes to drop traffic. Since we've all decided that shitty middleboxes are the protocol's problem to solve (because end users usually can't decide whether or not they're behind shitty middleboxes) all attempts at a new protocol are big puzzle pieces now.
Even existing protocols like MTCP and SCTP are dropped in favour of UDP because shitty firewalls can't deal with anything that's not TCP or UDP anymore. TLS 1.3 looks like TLS 1.2 packets because shitty middleboxes will just terminate your connection if they see TLS with an unknown version number.
It's quite depressing, really. I'm sort of hoping that at some point some weird proprietary or open source product with a fancy protocol comes out and becomes a hit, forcing shitty middlebox manufacturers to get their shit together (or tell the end user that the product won't work right because of shitty middleboxes and that they should complain to their service provider about it).
I'm all for backwards compatibility, but I'm sick and tired of MitM protocol parsers that refuse to follow spec being respected and worked around when it comes to new protocols. If you can't read the RFC, get out of the network protocol space.
- dharmab 5y agoRelated reading on why HTTP/3 uses UDP rather than a new protocol: https://lwn.net/Articles/745590/ https://lwn.net/Articles/745590/
- tialaramex 5y agoAs a silver lining to that particular cloud the shitty middleboxes made the case for work resulting from BCP #188 (Pervasive Monitoring Is An Attack) very easy. It wouldn't be difficult to find engineers at an IETF meeting who aren't very interested in whether Fatemah can send messages to her mother without them being read by her husband - that's a policy problem, not their business. But once they realise the shitty middleboxes to prevent Fatemah from evading her husband's surveillance make their beautiful new protocol design undeployable they're on board with encrypting absolutely everything everywhere all the time.
- babagabooj 5y ago
- sho_hn 5y agoI read this differently, as intentional effort not to just use Bob/Alice, being English-centric names. In Korean you sometimes see Chulsoo and Yonghee used as generic names, going back to school textbook characters. Maybe Fatemah is similar?
- enneff 5y agoI’m not familiar with the background of the poster you replied to, but your assumption that they are not simply choosing a common name from their culture is telling.
- koprulusector 5y agoI also assumed commenter picked a familiar name, rather than the cynical version.
- mdoms 5y agoI honestly cannot imagine what it's like to think like you do. It must be hell.
- babagabooj 5y agoThis comment is telling of how self-centered you are, referencing your imagined or un-imagine-able experience right out of the gate.
- zamadatix 5y agoEncrypting at the protocol layer absolutely everything everywhere all the time doesn't solve that policy problem in any way. It does solve the protocol ossification problem though.
- dotancohen 5y ago
- colordrops 5y agoI've had it with these mother fucking gates on this mother fucking backplane.