IETF Logo Mail Archive

Re: Questions about stream state transitions

Shigeki Ohtsu <ohtsu@iij.ad.jp> Thu, 18 July 2013 08:34 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 5469D21E808A for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 18 Jul 2013 01:34:49 -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 Jm+hkttimwcG for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 18 Jul 2013 01:34:44 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 575A721E8095 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 18 Jul 2013 01:34:41 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UzjeY-0000NP-F6 for ietf-http-wg-dist@listhub.w3.org; Thu, 18 Jul 2013 08:33:34 +0000
Resent-Date: Thu, 18 Jul 2013 08:33:34 +0000
Resent-Message-Id: <E1UzjeY-0000NP-F6@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <ohtsu@iij.ad.jp>) id 1UzjeQ-0000MU-Lw for ietf-http-wg@listhub.w3.org; Thu, 18 Jul 2013 08:33:26 +0000
Received: from mo30.iij.ad.jp ([202.232.30.71] helo=omgo.iij.ad.jp) by maggie.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <ohtsu@iij.ad.jp>) id 1UzjeO-0008JJ-JK for ietf-http-wg@w3.org; Thu, 18 Jul 2013 08:33:26 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iij.ad.jp; h=Message-ID: Date:From:MIME-Version:To:Subject:References:In-Reply-To:Content-Type: Content-Transfer-Encoding; i=ohtsu@iij.ad.jp; s=omgo1; t=1374136381; x= 1375345981; bh=xN9hoAnl40gzxIpBYpCPh2DqHmHAIiW//aCapYV/Cug=; b=F+gLS7Kf6njxSDHK 2RCJ0CBUq7hOh5YOw7/lgpF9dzT8SFmcolvUDfKdaHTpLWZ7/tenOzx+rdgr9JLXCqZ/wAUEN2Vv3 5yoeWmG05W52XS7QdkStsaeJU0Z1EbNFEJm3m6Rd5jq6EmfeLRwuTEk/nwg4Jr9jlfgdMQglZAST2 s=;
Received: by omgo.iij.ad.jp (mo30) id r6I8X1TP003076; Thu, 18 Jul 2013 17:33:01 +0900
Message-ID: <51E7A83A.2050209@iij.ad.jp>
Date: Thu, 18 Jul 2013 17:32:58 +0900
From: Shigeki Ohtsu <ohtsu@iij.ad.jp>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf-http-wg@w3.org
References: <51E6908F.2010602@iij.ad.jp> <CABkgnnVRuSRwr+3RQd=5+nMcz5Mhy3mavSXc15wi_0ZFd5yo8g@mail.gmail.com> <51E78D77.7060000@iij.ad.jp> <20130718080838.GA880@LK-Perkele-VII>
In-Reply-To: <20130718080838.GA880@LK-Perkele-VII>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass client-ip=202.232.30.71; envelope-from=ohtsu@iij.ad.jp; helo=omgo.iij.ad.jp
X-W3C-Hub-Spam-Status: No, score=-3.7
X-W3C-Hub-Spam-Report: AWL=-3.288, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.322, SPF_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1UzjeO-0008JJ-JK 2e9e7b106f16bc8abe56a906674da649
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Questions about stream state transitions
Archived-At: <http://www.w3.org/mid/51E7A83A.2050209@iij.ad.jp>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18840
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>

(2013/07/18 17:08), Ilari Liusvaara wrote:
> On Thu, Jul 18, 2013 at 03:38:47PM +0900, Shigeki Ohtsu wrote:
>> Thanks for answers, they are very helpful for me.
>>
>> Following comments, I've update the table in
>>
>> http://html5.ohtsu.org/HTTP2_Stream_State.pdf
>>
>> Please review this if it is correct and I've also submitted a new PR of
>
> Eh, HEADERS in Reserved (remote) transitions to half closed (local)
> regardless of END_STREAM? That looks bit suspicious.

Yes, it can be an option that it is UNCHANGED to still remain in the reserved(remote)
when HEADERS without END_STREAM is received.

> Also, I think that anytime DATA can be successfully received,
> WINDOW_UPDATE can be sent (half closed (local) seems to violate
> that).

PRIORITY can also be received in reserved(local/remote) accrding to the above model.

I'm not sure that there are pros and cons about this model. If not, I think it would be a design choice.

v2.23.0 | Report a Bug | By Email