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

ianswett <notifications@github.com> Sat, 23 November 2019 19:25 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 []) by ietfa.amsl.com (Postfix) with ESMTP id E3F5F12004F for <quic-issues@ietfa.amsl.com>; Sat, 23 Nov 2019 11:25:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id thrONW_TltS0 for <quic-issues@ietfa.amsl.com>; Sat, 23 Nov 2019 11:25:26 -0800 (PST)
Received: from out-4.smtp.github.com (out-4.smtp.github.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DBA2120024 for <quic-issues@ietf.org>; Sat, 23 Nov 2019 11:25:26 -0800 (PST)
Received: from github-lowworker-6349a71.ac4-iad.github.net (github-lowworker-6349a71.ac4-iad.github.net []) by smtp.github.com (Postfix) with ESMTP id 5221BC600AF for <quic-issues@ietf.org>; Sat, 23 Nov 2019 11:25:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1574537125; bh=m4b4RTkuy9prmV/utpnKTecm24WtCj+AVcpMCMcthMQ=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=dkRZGAj8+oz/aLvPXu3etxaODsZ7YjiIuQK4h9ddmuDppGN3okpl6GGTWuofwo4ud FpIIocFiuTA6flL5ePSMZWKqmZNGj6+wfcYkQJ/v1CD5K/KUFL69dBr5CaqhfOeJ90 snsViiHaDK+IgeLMWsIx2A+zKznwLzQzT+PPBErU=
Date: Sat, 23 Nov 2019 11:25:25 -0800
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYN3KEBXNL3VUFDJKN3425CLEVBNHHB64UA7U@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3273@github.com>
Subject: [quicwg/base-drafts] HTTP/3 references QUIC Stream IDs directly, allowing illegal references (#3273)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dd987a5423d6_19f83fcc89acd95c29882d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/11dqi5a4ZMWzInZ-8dYqOodM1gc>
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: Sat, 23 Nov 2019 19:25:28 -0000

Currently, HTTP/3 references QUIC Stream IDs directly in the case of requests.  However, requests are only 1 of the 4 stream types, so 3/4 of the values in GOAWAY are currently invalid, though we don't specify what happens if you receive one of those invalid values in the current draft(or I missed it).

QUIC transport has moved to a design for MAX_STREAMS(https://tools.ietf.org/html/draft-ietf-quic-transport-24#section-19.11) that specifies the allowed number of streams of a given type, rather than the Stream ID.

Currently, this is a very minor point, since it's only the GOAWAY frame that references Stream ID, but future frames, such as the PRIORITY_UPDATE frame from the HTTP priorities draft will also want to reference the Stream ID, as will future extension frames I expect.

So I suggest we call this a Request ID and it's the Stream ID of a client bidi stream right shifted 2 bits or however else we'd like to describe it.

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