Re: 3.3.1 Frame Header: Purpose of 1-bit reserved field?
Roberto Peon <grmocg@gmail.com> Sat, 13 April 2013 18:15 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 E8B8521F8B3A for
<ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>;
Sat, 13 Apr 2013 11:15:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.298
X-Spam-Level:
X-Spam-Status: No, score=-10.298 tagged_above=-999 required=5 tests=[AWL=0.300,
BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 14Ii5e1op1Bj for
<ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>;
Sat, 13 Apr 2013 11:15:20 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com
(Postfix) with ESMTP id 0EC3221F8B15 for
<httpbisa-archive-bis2Juki@lists.ietf.org>;
Sat, 13 Apr 2013 11:15: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 1UR4xT-0007tM-F3 for
ietf-http-wg-dist@listhub.w3.org; Sat, 13 Apr 2013 18:13:51 +0000
Resent-Date: Sat, 13 Apr 2013 18:13:51 +0000
Resent-Message-Id: <E1UR4xT-0007tM-F3@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim
4.72) (envelope-from <grmocg@gmail.com>) id 1UR4xR-0007sg-1W for
ietf-http-wg@listhub.w3.org; Sat, 13 Apr 2013 18:13:49 +0000
Received: from mail-ob0-f169.google.com ([209.85.214.169]) by maggie.w3.org
with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from
<grmocg@gmail.com>) id 1UR4xQ-0007Kt-5S for ietf-http-wg@w3.org;
Sat, 13 Apr 2013 18:13:48 +0000
Received: by mail-ob0-f169.google.com with SMTP id wp18so3237329obc.14 for
<ietf-http-wg@w3.org>; Sat, 13 Apr 2013 11:13:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:x-received:in-reply-to:references:date:message-id
:subject:from:to:cc:content-type;
bh=Ipl43PWDepAR7C++dIEAAjQBDvy31tSDEJHZ+bwaWBw=;
b=pbPzETsxxk+6C7Hx1C7fI+V8rtkah4oCAcc1r1KES5EMQUEWFRzOBzUC6K4KJph/WY
/OrauTPK+uLu+RFNugOc9uoErMn4K6aEO0iEqd+Z80YcbnNpHboqB7d2CMalCOpF3q72
TGr+teHRcO4BfsZJx03L7H11jcBstVHf/2SRM1zTDlcJ/Bl6jqbwZkHmZfFqEMx78XKw
vu9JuNmruyWCa5lKZINwMf5FAuOgtbG7iypicrF2mo0UHqOaOGPOcutSeRerFAdo0tJk
Jl6N2qwUajHAw3mNyYKk0qIeltMsojm4POegYxdP1OJJohUU8t0XNyqf4PLzohTHea6J 8kHw==
MIME-Version: 1.0
X-Received: by 10.60.16.164 with SMTP id h4mr5364416oed.23.1365876802118;
Sat, 13 Apr 2013 11:13:22 -0700 (PDT)
Received: by 10.76.141.83 with HTTP; Sat, 13 Apr 2013 11:13:21 -0700 (PDT)
Received: by 10.76.141.83 with HTTP; Sat, 13 Apr 2013 11:13:21 -0700 (PDT)
In-Reply-To: <9A2814A1-C78E-4C27-ADBF-F97F652B2E60@mnot.net>
References: <em510058b6-8c4a-4e11-9597-f756ef5ed08d@bombed>
<9A2814A1-C78E-4C27-ADBF-F97F652B2E60@mnot.net>
Date: Sat, 13 Apr 2013 11:13:21 -0700
Message-ID: <CAP+FsNf1jds77oFP=KK+QL5ZU0af9OOJFL=pFsdnmPHaZ2jbnA@mail.gmail.com>
From: Roberto Peon <grmocg@gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: "Adrien W. de Croy" <adrien@qbik.com>,
"Brian Raymor (MS OPEN TECH)" <Brian.Raymor@microsoft.com>,
"ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary=089e013a125a98ea6204da41f90a
Received-SPF: pass client-ip=209.85.214.169; envelope-from=grmocg@gmail.com;
helo=mail-ob0-f169.google.com
X-W3C-Hub-Spam-Status: No, score=-3.5
X-W3C-Hub-Spam-Report: AWL=-2.682, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001,
RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1UR4xQ-0007Kt-5S 14fe15c222dc5fe6575578d3273c7050
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/CAP+FsNf1jds77oFP=KK+QL5ZU0af9OOJFL=pFsdnmPHaZ2jbnA@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/17219
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>
This is for prioritization experimentation in the future. The bit allows for priority level vs resource ordering without bloating the payload of a reprint frame. It was originally for control vs data. -=R On Apr 12, 2013 11:50 PM, "Mark Nottingham" <mnot@mnot.net> wrote: > 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