Re: [quicwg/base-drafts] Grease HTTP error codes (#3360)

Jana Iyengar <> Tue, 21 January 2020 00:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1B246120835 for <>; Mon, 20 Jan 2020 16:48:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.596
X-Spam-Status: No, score=-1.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, 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 hSzXVGNT6vnk for <>; Mon, 20 Jan 2020 16:48:18 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 39A07120801 for <>; Mon, 20 Jan 2020 16:48:18 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 686EE28002B for <>; Mon, 20 Jan 2020 16:48:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1579567697; bh=MdvZeWO/SC4zSjMBuE+5TtlTCQ8kMxp4BqmGHP2+e20=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=YuwcwPwzYqcMNSa7lrRNqTLcC2rJnJrdfZq0LkmemawGFlXCC0Jxsc4xgteIOCvXc uslgzZVpQx0lsvBtOB64JWSBRYiolCra5P1Z6y/NbO9w7GD9zmaQLSwhKfzUKfUxa7 jx74l8u+kkctVEz9OAPDqI5i979bvmaQS8aJpkF4=
Date: Mon, 20 Jan 2020 16:48:17 -0800
From: Jana Iyengar <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3360/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Grease HTTP error codes (#3360)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e264a515865e_60db3f92832cd968289442"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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: Tue, 21 Jan 2020 00:48:20 -0000

janaiyengar commented on this pull request.

> @@ -925,7 +925,9 @@ transferred. Endpoints MUST NOT consider these streams to have any meaning upon
 The payload and length of the stream are selected in any manner the
-implementation chooses.
+implementation chooses.  Implementations MAY terminate these streams cleanly,
+or MAY abruptly terminate them with an error code of the implementation's
+choice, including reserved error codes ({{http-error-codes}}).

I agree, but this text allows for an implementation to use any error code. The peer could be wired to close the connection on some of these errors, irrespective of stream (H3_CLOSED_CRITICAL_STREAM perhaps). It might be worth stating that the endpoint MUST NOT close the connection on any error on these streams.

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