W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2019

RE: Interoping draft 20 HTTP/3

From: <dtikhonov@litespeedtech.com>
Date: Wed, 27 Mar 2019 06:03:06 -0400
To: "'Lucas Pardue'" <lucaspardue.24.7@gmail.com>, "'QUIC WG'" <quic@ietf.org>, "'HTTP Working Group'" <ietf-http-wg@w3.org>
Message-ID: <04ac01d4e484$469171e0$d3b455a0$@litespeedtech.com>
What are the QPACK issues that need addressing?  To the best of my knowledge, there are no outstanding QPACK issues whose resolution would effect changes in implementation.

 

  - Dmitri.

 

From: QUIC <quic-bounces@ietf.org> On Behalf Of Lucas Pardue
Sent: Wednesday, March 27, 2019 05:55
To: QUIC WG <quic@ietf.org>; HTTP Working Group <ietf-http-wg@w3.org>
Subject: Interoping draft 20 HTTP/3

 

In the IETF 104 session today we discussed the next interop target. I agree that aiming for draft 20 is a good target and anecdotally there is strong interest from HTTP/3 implementations to do so.

 

Some comments were made that the changes to 20 were minimal. However, IMO the changes to HTTP/3 are pretty big - the change to variable length integers affects most types. It was discussed at length (relatively speaking for HTTP/3), agreed and landed soon after. Unfortunately there are some issues that gained consensus in Tokyo but have yet to be addressed; either no PR or unmerged PR.

 

Therefore, I encourage us to close out some of the remaining issues on HTTP/3 and QPACK before cutting new releases of those documents. 

 

Lucas 
Received on Wednesday, 27 March 2019 10:03:39 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 27 March 2019 10:03:40 UTC