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

MikkelFJ <notifications@github.com> Sat, 12 January 2019 12:33 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 6D65512D4ED for <quic-issues@ietfa.amsl.com>; Sat, 12 Jan 2019 04:33:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.553
X-Spam-Level:
X-Spam-Status: No, score=-12.553 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_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 gQ4jd6YHBlM5 for <quic-issues@ietfa.amsl.com>; Sat, 12 Jan 2019 04:33:47 -0800 (PST)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9FDDA128CF3 for <quic-issues@ietf.org>; Sat, 12 Jan 2019 04:33:47 -0800 (PST)
Date: Sat, 12 Jan 2019 04:33:45 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1547296425; bh=Gv0ZshcsEf4lX7Vd1XHw9/+m2QKgE8tWSX20hq4VOaY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=PJswT5VBsB+rcSZ/p9znnTzsjgiBevhXsa8elgTz1v2HOHYwXEJ3dz7Y82eDFH+22 sJRd8wq+ECtxnGOXg8CuezrbnrcT56TgmSLyBTbnR+R+TFKDocCgzOBRqiB1+nr+oA Di77KAp9K+0t+GXl79WX6TZyBRdoy4qHgp9ZRHS4=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab79aa24ee4e01ca32d87b54edcc48d6d783d547b592cf000000011851a0a992a169ce17c1011d@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/453743962@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_5c39dea95cc60_50c23fa52ead45b85261eb"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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/Zdiffe0qw1Q2q2b06-PabSSE124>
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 12:33:50 -0000

> If I understand what Mikkel said, the endpoint sends and empty stream frame and then closes the stream. What is advantage in that style of opening?

First, it is a matter of being robust against all possible ways of transmitting packets, even if done in an unlikely way.

Second, in my last analysis I have a case where you send valid data, but the later RESET races the earlier packets. There are several cases: the open is entirely missed and only the RESET survives, but it then effectively opens and closes the stream, or the open is sent with 0 length data, then a later packet sends the frame type, and a later packet again sends the RESET, and the middle packet gets lost or delayed. The latter case is of course contrived, but it is still valid and 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-453743962