Unrelated but a ton of work is being put into HTTP/3 while ESNI has been lingering in draft spec for years. As far as protocol work, I think their priorities are wrong.
Most wireless protocols hide packet loss from upper layers anyways using retry/FEC. I can't think of a common situation where wireless packet loss is even visible to layer 4, so efforts to build tolerance to it are usually pointless
Sure, but would the people working on http/3 be otherwise working on ESNI? Its a different problem space requiring different skills.
> Most wireless protocols hide packet loss from upper layers anyways using retry/FEC. I can't think of a common situation where wireless packet loss is even visible to layer 4, so efforts to build tolerance to it are usually pointless
Its attempting to build tolerance to sudden transient latency spikes interacting badly with congestion control algorithms. You can hide packet loss, you can't hide some random packet taking a lot longer to be delivered due to having to be retried.
> Its attempting to build tolerance to sudden transient latency spikes interacting badly with congestion control algorithms. You can hide packet loss, you can't hide some random packet taking a lot longer to be delivered due to having to be retried.
Good point. By using UDP you can get around head-of-line blocking. I didn't consider that
Most wireless protocols hide packet loss from upper layers anyways using retry/FEC. I can't think of a common situation where wireless packet loss is even visible to layer 4, so efforts to build tolerance to it are usually pointless