Re: Consensus on Deploying QUIC v1 with HTTP/3

[Lucas Pardue <[e-mail]>]

Hi Julian.

On Thu, May 6, 2021 at 3:24 PM Julian Reschke <[e-mail]> wrote:

> Am 06.05.2021 um 06:11 schrieb Matt Joras:
> > ...
> >         You may want to clarify what *exactly* you mean by "the QUIC
> RFCs".
> >
> >
> >     Lucas was referring to C430:
> >     https://www.rfc-editor.org/cluster_info.php?cid=C430
> >     <https://www.rfc-editor.org/cluster_info.php?cid=C430>
> >
> > ...Excepting the qpack and http documents. I hit the send button too
> > quickly.
>
> See? That's why I was asking.
>
> So we're discussing just -invariants, -transport, -tls, and -recovery,
> right?
>

Thanks for pointing this out. The email was written from a position
familiar with the current documents' status. I should have been more clear
and explicit.

Yes, the -invariants, -transport, -tls, and -recovery, are the QUIC
documents that are presently in AUTH48 and we expect to be published as
RFCs before -http and -qpack. Other documents adopted by the QUIC WG are
not in scope for this discussion (the applicability drafts, datagram
extension, etc.). So to restate the original position more clearly:

This email commences a formal consensus call for permitting the deployment
of QUIC "0x00000001" with HTTP/3 ALPN identifier "h3" *after* -invariants,
-transport, -tls, and -recovery have been published as RFCs but *before *-http
and -qpack are published as RFC. The call will end on May 13.

Cheers,
Lucas