3 ms·
Note that even the previous draft specification (https://datatracker.ietf.org/doc/draft-ietf-quic-http/34/ https://datatracker.ietf.org/doc/draft-ietf-quic-http
by Matthias247 4y ago
Note that even the previous draft specification (https://datatracker.ietf.org/doc/draft-ietf-quic-http/34/ https://datatracker.ietf.org/doc/draft-ietf-quic-http/34/) was a mapping of HTTP semantics on top of QUIC. It didn't carry too many transport specific concerns - which e.g. HTTP/2 did, since it cared about flow control and other things.
I have yet to read RFC 9114, but I guess it's refinded to fit better on top of the new HTTP semantics spec (RFC 9110).
- rektide 4y agoI'd be aghast to see a significant rewrite of a specification as it moves from draft to rfc. The draft, at it's end, should closely mirror the final spec.