Re: [quicwg/base-drafts] Need to clarify QUIC stream usage in HTTP/2 mapping (#1882)
Magnus Westerlund <notifications@github.com> Wed, 31 October 2018 07:55 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 8C32A128C65 for <quic-issues@ietfa.amsl.com>; Wed, 31 Oct 2018 00:55:17 -0700 (PDT)
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 1e9NxcbRG2Qx for <quic-issues@ietfa.amsl.com>; Wed, 31 Oct 2018 00:55:16 -0700 (PDT)
Received: from out-12.smtp.github.com (out-12.smtp.github.com [192.30.254.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A945130DD9 for <quic-issues@ietf.org>; Wed, 31 Oct 2018 00:55:14 -0700 (PDT)
Date: Wed, 31 Oct 2018 00:55:13 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1540972513; bh=EJzfS7BFtxF4XLO8sbZerCDoc/IAU2nch2xk/lVxES4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=MfGa8h0+/qd6n+IXUtgWItgv0APPJ1tIX0P9PdgqvaPeqpq+wSa32XsB1rAZDgznI gqwn3b11ogWBMIYJQ3JdIC0Avniz098JmmwsGPOuNZ0HGcQ18N+zXAkZ+FfC3JG+V5 pzHpwUCtEDCcoH5nh/3EUU1JJ+2oY9Wa+wKegx9o=
From: Magnus Westerlund <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab5e34200341761d9c25e5c73837ad538affc15ddf92cf0000000117f121e192a169ce1623af22@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/434593243@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_5bd95fe1a5da3_1ac23fcb6d2d45c4580f6"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: gloinul
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/Va3s4zi3wH9RVjRsgo6mFp1kia4>
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: Wed, 31 Oct 2018 07:55:18 -0000
Okay, I had missed that this was added in -16. I am actually not thrilled that this went into QUIC, I might have missinterpreted the discussion as being all in the context of HTTP. Anyway, can you please adjust the text in Section 3, so that it clearer states that QUIC transport defines the terms and meaning of bidirectional and unidirectional streams and that there are two stream versions depending on who that initiates it. And please with a correct section reference into the transport draft. Pointing at section 9 when it is section 2 does not help. -- 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-434593243
- [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