[quicwg/base-drafts] Why do control streams need to be typed? (#2224)

ekr <notifications@github.com> Thu, 20 December 2018 23:04 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 B8067131256 for <quic-issues@ietfa.amsl.com>; Thu, 20 Dec 2018 15:04:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.661
X-Spam-Status: No, score=-6.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, 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_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 HJVn4imhowsv for <quic-issues@ietfa.amsl.com>; Thu, 20 Dec 2018 15:04:15 -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 D6128130F21 for <quic-issues@ietf.org>; Thu, 20 Dec 2018 15:04:14 -0800 (PST)
Date: Thu, 20 Dec 2018 15:04:13 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1545347053; bh=3BG4lnkZxX2Y9++kfe+cdGjZ37oiG3bvZA3kJC+axQg=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=DNptp9KN6cjQF3fxal9L2acQPOtateWKtsqJBjOeWHajNHJShfgvCYAJ4SHCdfSc7 23Z6QTnzbbVK8HIC1uqKVL4DBLIf7Fy+5jTbVHw3cYqYvKtBdN+kbqIPCScjZPSPwX vgta95D2EBWjryQ4vs8cbkVGd4JSJ8gFy98goGao=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab2bfbaf0722aab8650f323d37a294e7e13ef173aa92cf000000011833e1ed92a169ce17706d7a@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2224@github.com>
Subject: [quicwg/base-drafts] Why do control streams need to be typed? (#2224)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c1c1fededd64_57403fc27dad45c41093ab"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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/XmSSjtRzdNvSg1_IYJWGGNoIU08>
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, 20 Dec 2018 23:04:17 -0000

S 3.2.1.

Each side MUST initiate a single control stream at the beginning of the
connection and send its SETTINGS frame as the first frame on this stream.  If
the first frame of the control stream is any other frame type, this MUST be
treated as a connection error of type HTTP_MISSING_SETTINGS. Only one control
stream per peer is permitted; receipt of a second stream which claims to be a
control stream MUST be treated as a connection error of type
HTTP_WRONG_STREAM_COUNT.  If the control stream is closed at any point, this
MUST be treated as a connection error of type HTTP_CLOSED_CRITICAL_STREAM.

Rather than having this rule, wouldn't it be easier to just require
a specific stream number for this stream? Then it would not be possible to have >1.

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