Re: [quicwg/base-drafts] HTTP/3 references QUIC Stream IDs directly, allowing illegal references (#3273)

Mike Bishop <> Wed, 04 December 2019 17:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 92915120937 for <>; Wed, 4 Dec 2019 09:50:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Status: No, score=-6.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 9BHSONaXozgl for <>; Wed, 4 Dec 2019 09:50:09 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1DD5A120907 for <>; Wed, 4 Dec 2019 09:50:09 -0800 (PST)
Date: Wed, 04 Dec 2019 09:50:08 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1575481808; bh=b4ctsgJVDMOfZwsA+Qqc4rphKviLG9k6iaA/o5Pj7a8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1sc9zBVTxKPjy1hVu3PcZnRDE8DHgrE9uzX5twvaT96dSPWVRj8H5wf2CnZTwJmDG yTYyYimRw6jiNiTdnlht+GFDOl3fnJls+XZ9bDHVuj4OsBe3MGgqSvVWYU8f5WyGNc HVIMCFWsMEAW7HnKSYquiRxDV8FbgDI2+0/m0IJ4=
From: Mike Bishop <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3273/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] HTTP/3 references QUIC Stream IDs directly, allowing illegal references (#3273)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5de7f1d017143_35fa3fe6ea8cd9601608ae"; 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
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 04 Dec 2019 17:50:15 -0000

> This seems a bit at odd with our design principles, since it requires the HTTP/3 implementation to understand the QUIC Stream ID numbering scheme.

While the issue is closed, I wanted to point out that it does not imply this requirement.  I've held very strictly to this mental model:

- HTTP/3 can ask QUIC for a stream of a given type
- HTTP/3 can query the newly-received stream for its ID
- HTTP/3 can thereafter use the ID to refer to the stream
- HTTP/3 can query QUIC for the type of a given Stream ID and/or retrieve a stream by ID and then query its type

If QUIC were to change how Stream IDs are allocated, the changes could be entirely within the transport.  Now, it's a fair critique to say that this model is not explicitly stated in the draft, and so it's not guaranteed that any given implementation would actually preserve this flexibility.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: