Return-Path: 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 ; 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 ; 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 ; 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 Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.29 List-Id: Notification list for GitHub issues related to the QUIC WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Dec 2018 19:37:33 -0000 ----==_mimepart_5c0585fa21d58_798e3fc637cd45b42324d5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit (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 ----==_mimepart_5c0585fa21d58_798e3fc637cd45b42324d5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

(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 u= nidirectional or bidirectional. The conditions for opening a stream are s= lightly more complex for a bidirectional stream because the opening of ei= ther send or receive sides causes the stream to open in both directions.<= /p>

I think it's actually perfectly reasonable to consider a bidirectional= stream as consisting of two unidirectional streams with some limited way= s that one stream's state change can cause the other stream's state chang= e. However, it's probably worth making sure the terminology is consisten= t throughout.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5c0585fa21d58_798e3fc637cd45b42324d5--