There's lots of things that could theoretically be done. They all add complexity. Any form of feature advertisement or negotiation would also need to extend to HTTP/3 for parity. Few clients are going to wait to see what the server claims to support (and support is a very weird definition here, because servers can just ignore all client signals even if they are understood). What we have in the document now has gained IETF consensus and is due to be imminently published by the RFC Editor. It does not exclude new additional work being done as a follow up activity, if we discover some new information and agree to spend effort to solve a problem. Cheers, Lucas
Received on Thursday, 31 March 2022 18:03:58 UTC