[quicwg/base-drafts] Rationalize HTTP/3 stream creation errors (#2821)

Lucas Pardue <notifications@github.com> Thu, 20 June 2019 16:03 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 7CEF91200B2 for <quic-issues@ietfa.amsl.com>; Thu, 20 Jun 2019 09:03:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.008
X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id l2sSWCwC8UaE for <quic-issues@ietfa.amsl.com>; Thu, 20 Jun 2019 09:03:23 -0700 (PDT)
Received: from out-1.smtp.github.com (out-1.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 5DB3F120019 for <quic-issues@ietf.org>; Thu, 20 Jun 2019 09:03:23 -0700 (PDT)
Date: Thu, 20 Jun 2019 09:03:22 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1561046602; bh=x8HLe361NRxyejT7+d90F24ogiKwDle4nceWeHdc4T8=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=1FMOFY0c0CBydN4zXyAS31sLUnUiADmJQv/buLxa4G/GZlF5oopo2qVbOxKLVRDrw Ste517/mLXWmiDjhzggLi06g0Fh9usAZM6k4g4NQ8e964PeTjfFd3aoxok5tP/nsTB XRz2Esn8em6hZyvlQ2h0ihVI9EJdDlKcfTY3t0Oo=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK54GOOQQTBCK5ILPVN3DDQMVEVBNHHBWV7AZQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2821@github.com>
Subject: [quicwg/base-drafts] Rationalize HTTP/3 stream creation errors (#2821)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d0bae4a3b3da_75033fbc0b0cd968984bc"; 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/OsrcwbCRu2k0Y9o5Eg-I-l3ykVY>
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 Jun 2019 16:03:26 -0000

There are presently several kinds of very similar error when creating streams:

1. HTTP_UNKNOWN_STREAM_TYPE MAY be used to tell a peer to STOP_SENDING on a stream type that is unknown by the local peer. It is **not** a connection error.
2. HTTP_WRONG_STREAM_COUNT MUST be used if a peer tries to open more than one critical stream (control, QPACK). Connection error.
3. HTTP_WRONG_STREAM_DIRECTION MUST be used if a client tries to open a push stream. More generally this could be used if a peer attempts to open a stream type that is not allowed to, but push is the only example today. Connection error.
4. HTTP_DUPLICATE_PUSH MUST be used if you open multiple push streams. 

The suggestion is to rationalize these into a single error code - HTTP_STREAM_CREATION_ERROR - that can be used in STOP_SENDING or CLOSE_CONNECTION.

The impact of merging _COUNT and _DIRECTION is minimal because implementations fundamentally have to open streams correctly in order to interop.

PS. The eagle eyes will notice I omitted the HTTP_DUPLICATE_PUSH creation error. This is on the chopping block in #2818. I class it differently because it is about parsing information **after** the stream type.

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