5 ms·
Am I the only one who thinks QUIC looks a bit crazy with all its variable length fields in the frame, separate short & long header format, and rather high limit
by clarry 7y ago
Am I the only one who thinks QUIC looks a bit crazy with all its variable length fields in the frame, separate short & long header format, and rather high limits for certain things? 160 bit connection ids and 64 bit stream ids sound like something you'd benefit from if you're Google scale and building big-ass load balancers on custom hardware but I feel like there's going to be a lot of overhead for everyone else. (Consider that a TCP header with no options is as large as a single maximum size connection id in QUIC).
At least the designers of IPv6 seemed to care more about efficiency, even if the protocol otherwise seems quite bloated and overengineered.
- the8472 7y agoI guess connection IDs are that large to allow the use of stateless cryptographic identifiers similar to tcp syn cookies. And stream IDs are assigned sequentially and variable length encoded, so they shouldn't take up much space most of the time.
- deleted 7y ago[deleted]
- ldng 7y agoGoogle trying to build a competitive advantage for themselves is not surprising. A lack of at least some level of pushback is slightly more worrying.