Re: [quicwg/base-drafts] Need to clarify QUIC stream usage in HTTP/2 mapping (#1882)
Mike Bishop <notifications@github.com> Thu, 18 October 2018 16:23 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 1730A130DE8 for <quic-issues@ietfa.amsl.com>; Thu, 18 Oct 2018 09:23:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.064
X-Spam-Level:
X-Spam-Status: No, score=-8.064 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.064, 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 S6dRIGbL1qzw for <quic-issues@ietfa.amsl.com>; Thu, 18 Oct 2018 09:23:19 -0700 (PDT)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54D38130E35 for <quic-issues@ietf.org>; Thu, 18 Oct 2018 09:23:19 -0700 (PDT)
Date: Thu, 18 Oct 2018 09:23:18 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1539879798; bh=8pHuB4rBCkLd2uGlG2v4K60f0FvDfExoGtDsClWEVzw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=m6ffFXx8FVjHx9AUEEkU4VWCnS5AcygzQFHmCoO115dQIzb1M07f/CcbpXt+tEThu p63h9aWOVIUQMyftHeuCMg0Y3j9wrdwV0YiGEKqbXAqKzjFe5Y/uxxYz7zy3yuc1uk 7FDCkKdNmY4FZ4Cy39OxWv/cu4CVI34tS8DVLtUM=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab32731944234b5cf642de473a40106782f59db8a092cf0000000117e0757692a169ce1623af22@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/431073596@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_5bc8b376631f1_5e9c3fa5c8ed45c4133192"; 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/4--SwWIaN4L5JtNrFI-CEaa2HwE>
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, 18 Oct 2018 16:23:32 -0000
Can you take a look at the [reorganized version](https://quicwg.org/base-drafts/reorganize/draft-ietf-quic-http.html#rfc.section.3)? I'm sure there's still room to improve, but I think the use of different stream types should be clearer. I'm explicitly trying to avoid assuming which Stream IDs will be which stream types in the HTTP spec, because that could change in a future version of QUIC. The place where I do, I should probably caveat it with "In version 1 of QUIC...." -- 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-431073596
- [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