Re: [quicwg/base-drafts] HTTP/QUIC: "Streams SHOULD be used sequentially, with no gaps." ambiguity. (#1417)
Lucas Pardue <notifications@github.com> Mon, 11 June 2018 11:24 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 3841B130F78 for <quic-issues@ietfa.amsl.com>; Mon, 11 Jun 2018 04:24:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 odAsICB62ZMk for <quic-issues@ietfa.amsl.com>; Mon, 11 Jun 2018 04:23:58 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [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 76AD912777C for <quic-issues@ietf.org>; Mon, 11 Jun 2018 04:23:58 -0700 (PDT)
Date: Mon, 11 Jun 2018 04:23:57 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528716237; bh=O+s94KtPyNOaZdBXWmk+lVIAaxmd3wzLk0OPBc41oe8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=FWjK/MhH1rXa+lzSqETPqgcbc48WF9a6sEZ68SUjYADEA3nI09yhcqfym+YJW1edz 5NIlfOQSR+f9x132LhpNg/Pfgm19OP0c3Fpfj4QSnNIH3auJWiecax9nvIp4tP6Uo/ VCXasnAP5+xMtmmAjFRi55iG6QLjOvQ22p0vMtXM=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab3693dc97d19d8350e7f3534cb34cbba16119570292cf0000000117361dcd92a169ce13a33b10@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1417/396210365@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1417@github.com>
References: <quicwg/base-drafts/issues/1417@github.com>
Subject: Re: [quicwg/base-drafts] HTTP/QUIC: "Streams SHOULD be used sequentially, with no gaps." ambiguity. (#1417)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b1e5bcd9d092_2f492ab61eef6f6056518d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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/rZ-gi2Pw-fM5RGmnA_XVd7aL-bg>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.26
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, 11 Jun 2018 11:24:01 -0000
One idea (discussed in-person) is to simply remove the offending statement. However, that seems to lose some of context. Perhaps we could join this sentance with earlier paragraph > When HTTP headers and data are sent over QUIC, the QUIC layer handles most of the stream management. and some fluffier text might 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/1417#issuecomment-396210365
- Re: [quicwg/base-drafts] HTTP/QUIC: "Streams SHOU… Mike Bishop
- Re: [quicwg/base-drafts] HTTP/QUIC: "Streams SHOU… Mike Bishop
- Re: [quicwg/base-drafts] HTTP/QUIC: "Streams SHOU… Mike Bishop
- Re: [quicwg/base-drafts] HTTP/QUIC: "Streams SHOU… Lucas Pardue
- [quicwg/base-drafts] HTTP/QUIC: "Streams SHOULD b… Lucas Pardue