Re: [quicwg/base-drafts] Stream terminology (#2081)
Mike Bishop <notifications@github.com> Mon, 03 December 2018 19:37 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 53CEF128BCC for <quic-issues@ietfa.amsl.com>; Mon, 3 Dec 2018 11:37:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Level:
X-Spam-Status: No, score=-9.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, 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 5Ck_dn1M6dc4 for <quic-issues@ietfa.amsl.com>; Mon, 3 Dec 2018 11:37:31 -0800 (PST)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 605401241F6 for <quic-issues@ietf.org>; Mon, 3 Dec 2018 11:37:31 -0800 (PST)
Date: Mon, 03 Dec 2018 11:37:30 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1543865850; bh=lBA3PtIanRWuCUTZ/nYt5W4kg6llPeBOFDbwI5YMOIM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=KsNQrD78dkIExEhEQF0n+hNA9b6MyQYU3QQXgvOM/pkac3bN+beVCOE/nj7jIvpu/ f4IFNiWOyJJw5YVWeOdx54Cup6rj7eFv0ZDX/JYR/ElB4W3q1jRt8cK6gNjVPy9gSG zVa0Rq9/YzAv0goL9avWQ0CORJz3UchjaaynEMik=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abbfda4541642680087179e9d412a057ceb5a4887b92cf00000001181d47fa92a169ce1708263a@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2081/443841539@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2081@github.com>
References: <quicwg/base-drafts/issues/2081@github.com>
Subject: Re: [quicwg/base-drafts] Stream terminology (#2081)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c0585fa21d58_798e3fc637cd45b42324d5"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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/8eCZ-pen-WwvDuA-tKoh-8pLC_0>
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: Mon, 03 Dec 2018 19:37:33 -0000
(For those following along at home, this is the transport draft.) 3.0 states: > Unidirectional streams use the applicable state machine directly. **Bidirectional streams use both state machines.** For the most part, the use of these state machines is the same whether the stream is unidirectional or bidirectional. The conditions for opening a stream are slightly more complex for a bidirectional stream because the opening of either send or receive sides causes the stream to open in both directions. I think it's actually perfectly reasonable to consider a bidirectional stream as consisting of two unidirectional streams with some limited ways that one stream's state change can cause the other stream's state change. However, it's probably worth making sure the terminology is consistent throughout. -- 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/2081#issuecomment-443841539