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

Re: Murray Kucherawy's No Objection on draft-ietf-httpbis-origin-h3-03: (with COMMENT)

From: Murray S. Kucherawy <superuser@gmail.com>
Date: Thu, 23 Feb 2023 05:44:19 -0800
Message-ID: <CAL0qLwbBbfQvmmBNKC2j=AbneWOL+9oNwTATAzrF77MxWvhxtA@mail.gmail.com>
To: Mike Bishop <mbishop@evequefou.be>
Cc: The IESG <iesg@ietf.org>, "draft-ietf-httpbis-origin-h3@ietf.org" <draft-ietf-httpbis-origin-h3@ietf.org>, "httpbis-chairs@ietf.org" <httpbis-chairs@ietf.org>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>, "mnot@mnot.net" <mnot@mnot.net>
On Tue, Feb 21, 2023 at 1:32 PM Mike Bishop <mbishop@evequefou.be> wrote:

> Since the BCP14 reference was added (in PR 2373
> <https://github.com/httpwg/http-extensions/pull/2373>) at Francesca’s
> request, I will let the two of you confer and tell me whether the reference
> is needed.  I don’t think the difference between OPTIONAL and optional is
> particularly compelling here, so I’m content either way.  It would be
> somewhat surprising to publish a Proposed Standard document that doesn’t
> use normative language, but all the actual protocol machinery is in the
> existing document, so I can see how it would work here.
>

Francesa is the sponsoring AD, so it's her call.  No need for us to
coordinate unless she wants to discuss it.  It was just a suggestion.


>  Proposed Standard is the intended status here because RFC 8336 is
> Proposed Standard, and this defines a means to exercise that mechanism in
> HTTP/3.
>

Thanks for that; it's just a detail that I think should be in the writeup,
but is glossed over with increasing frequency.

-MSK
Received on Thursday, 23 February 2023 13:45:43 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 23 February 2023 13:45:44 UTC