To summarize, I think there are three options: 1) Don't publish any RFCs until httpbis-semantics and httpbis-cache are in the RFC Ed queue 2) Publish QUIC ASAP without HTTP/3, and suggest that deployed endpoints run QUICv1 with ALPN h3-29/32/34 or whatever 3) Publish QUIC and HTTP/3 ASAP with a downref, allow ALPN h3 to deploy, and hope nothing important changes in the httpbis docs.
The second sounds cleanest to me, but I can certainly be persuaded of the others. On Wed, Jan 13, 2021 at 2:41 AM Magnus Westerlund < [email protected]> wrote: > Hi, > > My current judgment is also that this will result in that the HTTP/3 and > QPACK > specs will end up in missref due to these references. I don't think there > is an > good option. The new HTTP specs are substantial rewrites so going back to > RFC > 723x doesn't make sense here, and likely include substantial amount of > work. > > I do think the WG do need to be clear if the message is to stay with the > the > prelimenary versions, if that is h-29 or declare a h-34 based on the > forthcoming > -34 versions and what to do with salts and keys. > > Cheers > > Magnus > >
