Re: [quicwg/base-drafts] STOP_SENDING in Ready state (#1797)

MikkelFJ <notifications@github.com> Thu, 15 November 2018 19:54 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 7CEF7128D09 for <quic-issues@ietfa.amsl.com>; Thu, 15 Nov 2018 11:54:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.47
X-Spam-Level:
X-Spam-Status: No, score=-8.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, 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 EhoWvdjSDL91 for <quic-issues@ietfa.amsl.com>; Thu, 15 Nov 2018 11:54:21 -0800 (PST)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93B6B127333 for <quic-issues@ietf.org>; Thu, 15 Nov 2018 11:54:21 -0800 (PST)
Date: Thu, 15 Nov 2018 11:54:20 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1542311660; bh=36RBfjrBga/2IYUrRPMwUj5Q+I+gyv/WyAn5WleQvAo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=k+ja3csbE8iQcaXFS6ZPlWqkfMRt9FErjtpjST1sJpeYtzIGCQAuXZAYYOfPcq+7F 50tfLKtHwHd+FBRWynLeJfrGYYVqI37tCKfj0vQ0TPzGH6XZR/dktPAHwWWvmRIJBB gG/npBVy5kUBpgHY0Dq6usltJQ9y2vQstv/oeW7U=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab4f0fb49a91e09fcdf424b9b07b4187b8e995442592cf00000001180590ec92a169ce15ad130f@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1797/439169198@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1797@github.com>
References: <quicwg/base-drafts/issues/1797@github.com>
Subject: Re: [quicwg/base-drafts] STOP_SENDING in Ready state (#1797)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bedceec85868_65163f8b9a6d45c444293e"; 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/PPUPbvEUCpoUj8JNJFMnkc7ATrU>
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: Thu, 15 Nov 2018 19:54:23 -0000

> This says that the send side of a bidi stream is opened when a bidi stream is opened on the receive side. Or perhaps I'm misreading that?

I don't think that is wrong, but you cannot know the state at both ends at the same time. So the question is how you know that the other end opened the stream. It can happen by receiving data, or via implicit open in some cases.

I start to dislike implicit open even more now.

-- 
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/1797#issuecomment-439169198