IETF Logo Mail Archive

Re: [quicwg/base-drafts] What should the receiver do when the peer closes a unidirectional stream before providing the stream type? (#2331)

Subodh Iyengar <notifications@github.com> Sat, 12 January 2019 23:46 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E674131169 for <quic-issues@ietfa.amsl.com>; Sat, 12 Jan 2019 15:46:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.149
X-Spam-Level:
X-Spam-Status: No, score=-11.149 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y0q-F7MtaMZ0 for <quic-issues@ietfa.amsl.com>; Sat, 12 Jan 2019 15:46:13 -0800 (PST)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F98713115B for <quic-issues@ietf.org>; Sat, 12 Jan 2019 15:46:13 -0800 (PST)
Date: Sat, 12 Jan 2019 15:46:12 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1547336772; bh=jgx5pG13iEtyuS4o8js1h7MQry6Ye/uf2Ipa56L5iSw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=XitBxjjP1YCuAOEbb/pg2omClyUJNYkmKnFWa/OtSz3wwq69S6vA+J/XCrOBfqGTM 3ciNIIGdHsNIWW/OLNyTNfI4JXcfvrG4Uf/EU/NnXqVwRWbZY79PrsUXG/+IWdikvN VyM4rC3WWY2qff9jrCRxxA4DR+3v4bbml72LfF6o=
From: Subodh Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4aba13c7643fcd0a3a784c71aaefcc66750d6f076e592cf0000000118523e4492a169ce17c1011d@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2331/453789857@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2331@github.com>
References: <quicwg/base-drafts/issues/2331@github.com>
Subject: Re: [quicwg/base-drafts] What should the receiver do when the peer closes a unidirectional stream before providing the stream type? (#2331)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c3a7c4484d89_45013fa3344d45c41059b7"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: siyengar
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/R9bOzFojQibHG8Bdiw5qnmsUzcU>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Jan 2019 23:46:15 -0000

We encountered this as well, however we implicitly chose to go with the second option. I think it is the right option because the stream can be opened as a result or not just receiving the a type byte but also by a BLOCKED frame type or some other frames associated with a stream. For example a receiver of a unidirectional stream could choose to have an initial flow window of 0 bytes (weird but possible).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/2331#issuecomment-453789857

v2.23.0 | Report a Bug | By Email