W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2013

Re: initial stream id from a client

From: Shigeki Ohtsu <ohtsu@iij.ad.jp>
Date: Wed, 14 Aug 2013 09:17:50 +0900
Message-ID: <520ACCAE.4040000@iij.ad.jp>
To: ietf-http-wg@w3.org
Yes, I agree this.
It's already in the half-closed state and no need to define an absolute prohibition.

> So, to turn this into something actionable, let me propose:
>
> OLD:
>    A stream identifier of one (0x1) is used to respond to the HTTP/1.1
> request which was specified during Upgrade (see <xref
> target="discover-http"/>); stream identifier 0x1 MUST NOT be used by a
> client to establish a new stream.
> NEW:
>    A stream identifier of one (0x1) is used to respond to the HTTP/1.1
> request which was specified during Upgrade (see <xref
> target="discover-http"/>).  After the upgrade completes, stream 0x1 is
> "half closed (local)" to the client.  Therefore, stream 0x1 cannot be
> selected as a new stream identifier by a client that upgrades from
> HTTP/1.1.
>
> There are plenty of existing MUST/MUST NOT statements around sending
> different packets in this state.  No need to repeat them (and risk
> messing something up).
>
Received on Wednesday, 14 August 2013 00:18:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:14 UTC