Git Issues: Reserved Stream-ID Bit

James M Snell <jasnell@gmail.com> Sat, 20 April 2013 19:44 UTC

Resent-Date: Sat, 20 Apr 2013 19:43:57 +0000
Resent-Message-Id: <E1UTdhV-0005Vv-4s@frink.w3.org>
MIME-Version: 1.0
From: James M Snell <jasnell@gmail.com>
Date: Sat, 20 Apr 2013 12:43:06 -0700
Message-ID: <CABP7RbeszchSvdintd2ivt+b9vzs04VFAj+BPpq5Gr6d3rWT6A@mail.gmail.com>
To: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Received-SPF: pass client-ip=209.85.214.169; envelope-from=jasnell@gmail.com; helo=mail-ob0-f169.google.com
Subject: Git Issues: Reserved Stream-ID Bit
Archived-At: <http://www.w3.org/mid/CABP7RbeszchSvdintd2ivt+b9vzs04VFAj+BPpq5Gr6d3rWT6A@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list

Per: https://github.com/http2/http2-spec/issues/67

The question is: "R: A reserved 1-bit field. The semantics of this bit
are not defined...What is the purpose for this field?...Why not just
have a 32-bit stream identifier?

Currently, the spec mandates that stream ID's originating from the
client must be odd, and stream ID's originating from the server must
be even. This makes for a much more restricted range of stream id's
and ensures that they'll be used up much faster. Personally, I'd
prefer that this extra reserved bit be used to indicate the
"directionality" of the stream. All streams originating from the
client would have this bit unset, all streams originating from the
server would have this bit set. This gives each side a total of
(2^32)-1 streams to work with. That ought to be more than enough.

Git Issues: Reserved Stream-ID Bit James M Snell
Re: Git Issues: Reserved Stream-ID Bit William Chan (陈智昌)