4 ms·
> The first byte of the clear data was a flags field which, he said, was promptly ossified by a middlebox vendor, leading to packets being dropped when a new fl
by xg15 9y ago
> The first byte of the clear data was a flags field which, he said, was promptly ossified by a middlebox vendor, leading to packets being dropped when a new flag was set.
That was a classic example of why changing network protocols is hard and what needs to be done to improve the situation. Middleboxes are the control points for the Internet as we know it now. The only defense against ossification of network protocols by middleboxes, he said at the conclusion of the talk, is encryption.
So apparently we're now at a point where any middlebox trying to make any use of a protocol higher than IP counts as "ossification"? No matter if the middlebox is well-behaved or not.
And the only solution naturally is to make any stack parts higher than IP completely unusable by middleboxes by encrypting them. I guess this is make sense if you already fully control both clients and servers and get annoyed by middleboxes restricting your freedom to change the protocol on a whim.
However, this seems like a major change in the vision of the internet to me. So has the internet community at large now agreed that we want to get rid of middleboxes completely? What about middleboxes I want to employ myself, e.g. to watch my own traffic?
- vertex-four 9y agoThe problem here isn’t really middleboxes - it’s that people who build middleboxes tend to break protocols. The flags field is specifically designed so that you can add stuff to it - if the middleboxes were to be built properly, they would fall back to “don’t touch anything” rather than “break the connection” when they don’t understand what’s going on. Middlebox vendors brought this upon themselves.
- baby 9y ago> Middlebox vendors brought this upon themselves. Not really, I'm sure they don't care much, most of internet users will blame their browsers instead.
- ohazi 9y agoIt's not a problem if you can keep them updated, but that's not usually what happens. Network equipment often keeps running in the closet without updates for 10+ years. That's the part that isn't working well.
- baby 9y agoInterestingly, note that TLS 1.3 is not going to make things better as it is jumping through hoops and hoops just trying to conform to every little quirks middleboxes can have. I'm wondering if the IETF should have taken another route to force middleboxes to be more flexible in the future?
- Moodles 9y agoIndeed. It seems header encryption would be a good start. David Benjamin has proposed the GREASE protocol, but I think that is only for servers, not middleboxes.
- baby 9y agoGREASE only fuzzes some of the fields in TLS 1.3 handshake messages, to prevent middleboxes and TLS servers to incorrectly behave towards unknown values for extensions and other various fields. That doesn't help outside of TLS 1.3.
- Moodles 9y agoIndeed: it would be nice to see these techniques applied in more contexts.
- lmm 9y ago> However, this seems like a major change in the vision of the internet to me. So has the internet community at large now agreed that we want to get rid of middleboxes completely? What about middleboxes I want to employ myself, e.g. to watch my own traffic? The internet was built on the idea of having a dumb network with smart endpoints. Middleboxes are a good idea that just fundamentally doesn't work. Figure out how to do what you want on your edge nodes.
- xg15 9y agoExcept I don't have control about the edge nodes either, because the one edge is a remote server while the other edge is a locked-down smartphone or IoT device.
- cesarb 9y ago> What about middleboxes I want to employ myself, e.g. to watch my own traffic? > Except I don't have control about the edge nodes either, because the one edge is a remote server while the other edge is a locked-down smartphone or IoT device. If you don't have control over either of the endpoints, is it really your own traffic? Going a bit deeper: if you don't have control over your smartphone or IoT device, is it really your smartphone or IoT device?
- cesarb 9y ago> However, this seems like a major change in the vision of the internet to me. The vision of the Internet is that the network does little more than moving packets from point A to point B, with all the intelligence being in the endpoints. That way, the core network doesn't have to be upgraded for every little change in the protocols; protocol evolution happens on the edges of the network. Please read the classic "World of Ends" (http://www.worldofends.com/ http://www.worldofends.com/), and the technical article it links to, "End-to-end arguments in system design" (http://www.reed.com/dpr/locus/Papers/EndtoEnd.html http://www.reed.com/dpr/locus/Papers/EndtoEnd.html).
- 0xdeadbeefbabe 9y agoIs it middle boxes that do TTL-- as in ping?
- baby 9y ago> What about middleboxes I want to employ myself, e.g. to watch my own traffic? You'll need to do encryption termination. But then, you're subject to the same problem. If you reject packets you don't understand, or if you badly parse stuff, you'll compromise your traffic.
- fulafel 9y ago> However, this seems like a major change in the vision of the internet to me. So has the internet community at large now agreed that we want to get rid of middleboxes completely? Quite the opposite: Middleboxes are traditionally considered rule breakin kludges, they were never never part of the vision of the internet, or even allowed by the standards. The internet vision was end-to-end architecture, and global addressability, and a dumb network that does routing in a best-effort fashion in order enable host-to-host communication. IPv6 is an attempt to keep this all working. (And no, inspecting your own personal traffic on your own private network does not traditionally count as middleboxing)