Re: Fwd: WG Review: QUIC (quic)

[Spencer Dawkins at IETF <[e-mail]>]

Hi, Magnus,

Thanks for the clues. Inline (and deleting stuff that makes sense to me
now).

On Wed, Feb 12, 2020 at 4:03 AM Magnus Westerlund <
[e-mail]> wrote:

> Hi Spencer,
>
>
> Thanks for the comments. Please see inline.
> > > The third focus area describes the mapping between the HTTP application
> > > protocol and the transport facilities of QUIC. This mapping will have
> > > performance characteristics comparable with HTTP/2, and provide
> extension
> > > mechanisms similar to HTTP/2. Upon completion of this mapping, work to
> > > define
> > > additional mappings may be included by updates to this charter, or may
> be
> > > worked on by other working groups.
> >
> > When QUIC was chartered, my hope (and I don't think I was the only one)
> was
> > that we would end up with HTTP/2 over QUIC. For good reasons, we ended
> up with
> > HTTP/3 over QUIC, and it seems odd that there's no mention of HTTP/3 in
> the
> > 2020 QUIC charter, but it IS mentioned in
> > https://datatracker.ietf.org/doc/charter-ietf-httpbis/.
>
> As you might have noticed there have been some changes to not be specific
> saying
> HTTP/2 which is no longer correct with the choice to go on to define
> HTTP/3. The
> easier fix rather than trying to define what HTTP/3 is in detail, instead
> we
> have chosen to describe it simply as a mapping of the HTTP semantics onto
> the
> QUIC protocol. This makes the ongoing work to be in charter.
>
> So are you primarily concerned that we are not explicitly saying that the
> HTTP
> sematinc mapping on QUIC is called HTTP/3? Or is it that we don't define
> what
> HTTP/3 is from a work scope perspective more detailed?
>

I'm primarily concerned that it's unnecessarily obscure, who's working on
HTTP/3. You might think that you'd know that from looking at the QUIC
charter :-)

But let me try this thinking on - it's only unnecessarily obscure for as
long as QUIC is operating on this charter. So, if (making this up) the next
charter happens in six months, well, that's not so bad ... and with the
next charter, HTTP/3 moves off to HTTPbis anyway.

Does that sound about right to you?

Best,

Spencer