Re: [quicwg/base-drafts] Need to clarify QUIC stream usage in HTTP/2 mapping (#1882)
Mike Bishop <notifications@github.com> Thu, 29 November 2018 00:22 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 6F5A9130FB1 for <quic-issues@ietfa.amsl.com>; Wed, 28 Nov 2018 16:22:07 -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 SioNqyrYhiTx for <quic-issues@ietfa.amsl.com>; Wed, 28 Nov 2018 16:22:05 -0800 (PST)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1EE512426E for <quic-issues@ietf.org>; Wed, 28 Nov 2018 16:22:05 -0800 (PST)
Date: Wed, 28 Nov 2018 16:22:05 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1543450925; bh=eedbl9rmK4CJz6FExn8mhS/PsFyF/pVxIy/IsQklHjk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=icEz19ks6gr7PVU832U1yIywMZZgVeP5iYmwz7HfO0gZTmCtCrCRBvJh+yKX8cWeN LSJtn0tcJcsxO5nuB+kS3Q8eunIsxYrUdsqTwhlihui9h0F9c2l4c5OYkeSvHx+Xgq W8THOht/kHWHZSQWq8mL2IdLo6AAHjqQXW3ESP4E=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abac3a2a86bef3d09fff6413bbc361fd4841003f5992cf000000011816f32d92a169ce1623af22@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1882/442657498@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1882@github.com>
References: <quicwg/base-drafts/issues/1882@github.com>
Subject: Re: [quicwg/base-drafts] Need to clarify QUIC stream usage in HTTP/2 mapping (#1882)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bff312d1920c_23fd3fc2706d45bc10654f"; 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/tQKhfBJgqFYgpSUGOXyoRvUrre0>
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, 29 Nov 2018 00:22:07 -0000
Unidirectional / bidirectional is much older than -16 -- looks like transport-08 added the uni/bidi stream types. Regardless, I'm inclined to believe the existing HTTP text sufficiently covers this and points to the right place:
> QUIC streams can be either unidirectional, carrying data only from initiator to receiver, or bidirectional. Streams can be initiated by either the client or the server. For more detail on QUIC streams, see Section 2 of {{QUIC-TRANSPORT}}.
Feel free to re-open if you disagree, preferably with specific items you feel are still missing.
--
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/1882#issuecomment-442657498
- [quicwg/base-drafts] Need to clarify QUIC stream … Magnus Westerlund
- Re: [quicwg/base-drafts] Need to clarify QUIC str… Mike Bishop
- Re: [quicwg/base-drafts] Need to clarify QUIC str… Magnus Westerlund
- Re: [quicwg/base-drafts] Need to clarify QUIC str… Lucas Pardue
- Re: [quicwg/base-drafts] Need to clarify QUIC str… Mike Bishop
- Re: [quicwg/base-drafts] Need to clarify QUIC str… Magnus Westerlund
- Re: [quicwg/base-drafts] Need to clarify QUIC str… Mike Bishop
- Re: [quicwg/base-drafts] Need to clarify QUIC str… Mike Bishop