Re: [quicwg/base-drafts] Identify streams unidirectional vs bidirectional based on stream ID (#872)

Martin Thomson <notifications@github.com> Tue, 17 October 2017 23: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 495B71330AD for <quic-issues@ietfa.amsl.com>; Tue, 17 Oct 2017 16:33:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.3
X-Spam-Level:
X-Spam-Status: No, score=-9.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.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 yntWRlMYP_h9 for <quic-issues@ietfa.amsl.com>; Tue, 17 Oct 2017 16:33:51 -0700 (PDT)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext5.iad.github.net [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 A1A24132811 for <quic-issues@ietf.org>; Tue, 17 Oct 2017 16:33:50 -0700 (PDT)
Date: Tue, 17 Oct 2017 16:33:49 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1508283229; bh=zK8DXsvybgEPLqU+lZTP7Jo0kYePP+NI7rk23ONSd04=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=eagsRClFMcefweb31E7hClnq7pRHEliVhJVBYtWskQPcZy7IJLzQtuwWyDWX3a4Rv xNegU8aTnBCYKvwIk09PrkEaUQLPXW4TmVgSOPX60nb8g3X/MDgLghtcRkgDzwdy1f 6+0qVUpjQuiEw2l2K/XfhRReXIP34oFUAvghEhcw=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab152bbc906c72d31b15610b6e92e49eb895e0310192cf0000000115fe555d92a169ce0fd14a5e@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/872/c337409206@github.com>
In-Reply-To: <quicwg/base-drafts/pull/872@github.com>
References: <quicwg/base-drafts/pull/872@github.com>
Subject: Re: [quicwg/base-drafts] Identify streams unidirectional vs bidirectional based on stream ID (#872)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59e6935dae2c5_17e33f9249ef0f2c184243"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/8OnRv-S3Pc2bfzYOs7lox4J97Ag>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 17 Oct 2017 23:33:52 -0000

So that I don't forget this... This PR omits two very important things:

1. It doesn't actually say what a unidirectional stream *is*.

2. It doesn't say anything about stream usage in HTTP.

As we discussed on the editor's call today, we are going to merge this, then fix it.  I'll prioritize fixing the first issue though.

Given the HTTP usage, I'm going to push harder for a separation of the type bits, because that will make the HTTP usage of the identifiers easier (it has implicit type identification).  That will have to wait until #877 resolves.  That also needs some HTTP text.

-- 
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/pull/872#issuecomment-337409206