Re: 3.3.1 Frame Header: Purpose of 1-bit reserved field?
Mark Nottingham <mnot@mnot.net> Sat, 13 April 2013 06:50 UTC
Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CB2B21F8FD7 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 12 Apr 2013 23:50:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ld3ywGO8IBVc for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 12 Apr 2013 23:50:20 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 1DCD821F8FBE for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 12 Apr 2013 23:50:19 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UQuGv-0004FA-Js for ietf-http-wg-dist@listhub.w3.org; Sat, 13 Apr 2013 06:49:15 +0000
Resent-Date: Sat, 13 Apr 2013 06:49:13 +0000
Resent-Message-Id: <E1UQuGv-0004FA-Js@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <mnot@mnot.net>) id 1UQuGt-0004Dw-NF for ietf-http-wg@listhub.w3.org; Sat, 13 Apr 2013 06:49:11 +0000
Received: from mxout-07.mxes.net ([216.86.168.182]) by lisa.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <mnot@mnot.net>) id 1UQuGt-0001WW-2T for ietf-http-wg@w3.org; Sat, 13 Apr 2013 06:49:11 +0000
Received: from hostc82a14571b19.mnot.net (unknown [118.209.210.200]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id C20FC22E1FA; Sat, 13 Apr 2013 02:48:27 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <em510058b6-8c4a-4e11-9597-f756ef5ed08d@bombed>
Date: Sat, 13 Apr 2013 16:48:22 +1000
Cc: "Brian Raymor (MS OPEN TECH)" <Brian.Raymor@microsoft.com>, "'ietf-http-wg@w3.org'" <ietf-http-wg@w3.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <9A2814A1-C78E-4C27-ADBF-F97F652B2E60@mnot.net>
References: <em510058b6-8c4a-4e11-9597-f756ef5ed08d@bombed>
To: "Adrien W. de Croy" <adrien@qbik.com>
X-Mailer: Apple Mail (2.1503)
Received-SPF: pass client-ip=216.86.168.182; envelope-from=mnot@mnot.net; helo=mxout-07.mxes.net
X-W3C-Hub-Spam-Status: No, score=-3.4
X-W3C-Hub-Spam-Report: AWL=-3.368, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1UQuGt-0001WW-2T d0f42eba9114aadd6f53e7c114dbbd6a
X-Original-To: ietf-http-wg@w3.org
Subject: Re: 3.3.1 Frame Header: Purpose of 1-bit reserved field?
Archived-At: <http://www.w3.org/mid/9A2814A1-C78E-4C27-ADBF-F97F652B2E60@mnot.net>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/17218
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
Looking at the minutes from Tokyo, this was originally for control vs. data (as in SPDY). I think there's been some discussion about discarding the control bit; OTOH, if people are going to define extension frames, it'd be nice for intermediaries to know whether they count against flow control without having to understand their semantics... Cheers, On 13/04/2013, at 3:43 PM, Adrien W. de Croy <adrien@qbik.com> wrote: > > future proofing? E.g. if we need to move to another format or size for stream ID? > > > ------ Original Message ------ > From: "Brian Raymor (MS OPEN TECH)" <Brian.Raymor@microsoft.com> > To: "'ietf-http-wg@w3.org'" <ietf-http-wg@w3.org> > Sent: 13/04/2013 12:48:46 p.m. > Subject: 3.3.1 Frame Header: Purpose of 1-bit reserved field? >> 3.3.1. Frame Header >> >> |R| Stream Identifier (31) | >> >> >> R: A reserved 1-bit field. The semantics of this bit are not defined. >> >> I was curious about the purpose for the 1-bit reserved field. Can it be deleted and the Stream Identifier increased to 32 bits? >> >> https://github.com/http2/http2-spec/issues/67 >> >> >> Brian Raymor >> Senior Program Manager >> Microsoft Open Technologies, Inc. >> A subsidiary of Microsoft Corporation >> >> >> > > -- Mark Nottingham http://www.mnot.net/
- 3.3.1 Frame Header: Purpose of 1-bit reserved fie… Brian Raymor (MS OPEN TECH)
- Re: 3.3.1 Frame Header: Purpose of 1-bit reserved… Adrien W. de Croy
- Re: 3.3.1 Frame Header: Purpose of 1-bit reserved… Mark Nottingham
- Re: 3.3.1 Frame Header: Purpose of 1-bit reserved… Roberto Peon
- Re: 3.3.1 Frame Header: Purpose of 1-bit reserved… Brian Pane
- RE: 3.3.1 Frame Header: Purpose of 1-bit reserved… Brian Raymor (MS OPEN TECH)
- Re: 3.3.1 Frame Header: Purpose of 1-bit reserved… Roberto Peon