Re: Questions about stream state transitions

Shigeki Ohtsu <ohtsu@iij.ad.jp> Fri, 19 July 2013 10:53 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 850A121F9D39 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 19 Jul 2013 03:53:17 -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 QZVXNq8k-VKe for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 19 Jul 2013 03:53:08 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 6419511E8104 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 19 Jul 2013 03:52:32 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1V08HD-0000ab-Eb for ietf-http-wg-dist@listhub.w3.org; Fri, 19 Jul 2013 10:51:07 +0000
Resent-Date: Fri, 19 Jul 2013 10:51:07 +0000
Resent-Message-Id: <E1V08HD-0000ab-Eb@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 1V08H2-0000Zq-8j for ietf-http-wg@listhub.w3.org; Fri, 19 Jul 2013 10:50:56 +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 1V08H1-0002N6-5Y for ietf-http-wg@w3.org; Fri, 19 Jul 2013 10:50:56 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iij.ad.jp; h=Message-ID: Date:From:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type: Content-Transfer-Encoding; i=ohtsu@iij.ad.jp; s=omgo1; t=1374231029; x= 1375440629; bh=ViFis6neNcPkQl86gDhyRlL+5GWahMYZVYSn7g5Dgxw=; b=vVQeIJP3h/gK6Yrm CUrNd9o0IWwDJRiavrQ1N1IoC7nauk/jvbfUa10PNpEWEwbAfjL3NBmd3amj2+iCMW65EplODQgSi hWXfh1riwG3b8xLygMXRJnwP3nILBRNrGqBys0ll/3l+TGdDegDUCaeHp/jz5j0JsFeF1rtkqde3K w=;
Received: by omgo.iij.ad.jp (mo30) id r6JAoTbF024787; Fri, 19 Jul 2013 19:50:29 +0900
Message-ID: <51E919EF.3000903@iij.ad.jp>
Date: Fri, 19 Jul 2013 19:50:23 +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: Martin Thomson <martin.thomson@gmail.com>
CC: HTTP Working Group <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> <51E7A83A.2050209@iij.ad.jp> <CABkgnnUfM-U1UZ9FV99ZLzhc3D8F652wsBE5Ctcw+rOmaH0iFg@mail.gmail.com>
In-Reply-To: <CABkgnnUfM-U1UZ9FV99ZLzhc3D8F652wsBE5Ctcw+rOmaH0iFg@mail.gmail.com>
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.252, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.394, SPF_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1V08H1-0002N6-5Y 3b615330d599fa1af23daafe19d0da02
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Questions about stream state transitions
Archived-At: <http://www.w3.org/mid/51E919EF.3000903@iij.ad.jp>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18846
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>

Thanks Martin,

You're right. HEADER+END_STREAM goes like two step transitions and
PUSH_PRMISE can be sent in hald closed(remote).

The table was fixed and updated.

The transition flow of PUSH_PROMISE confused me much. I hope no more fix is needed.

(2013/07/19 1:37), Martin Thomson wrote:
> On 18 July 2013 01:32, Shigeki Ohtsu <ohtsu@iij.ad.jp> wrote:
>>> 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.
>
> No this is also incorrect in the table.  If you can receive DATA, then
> the protocol requires that you be able to send WINDOW_UPDATE.
>
> Another bug I noticed is that it should be possible to send
> PUSH_PROMISE in half closed (remote) and to receive it in half closed
> (local).
>