Re: [quicwg/base-drafts] Error Code when SETTINGS exceeds maximum (#2498)

Kazuho Oku <> Thu, 07 March 2019 20:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 65D2C130F1E for <>; Thu, 7 Mar 2019 12:56:09 -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_PASS=-0.001, URIBL_BLOCKED=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 faqC9B3KsAzN for <>; Thu, 7 Mar 2019 12:56:07 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 922EA12AF7F for <>; Thu, 7 Mar 2019 12:56:07 -0800 (PST)
Date: Thu, 07 Mar 2019 12:56:06 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1551992166; bh=FQndPfrmL54HOLkm0OmhKm0si2RQ6scaXG8cyjhD2N0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=wwnSfzqqSjVFIaGaYfJnr4WClGbJ5M2SR9NZv38VKgoCiLYI+DBRCbXFrsDKfhYKT EoEWYIvDhTePguRkQTEbICns7GsdqhpLRp3Z7+29tUfMe26iYadWhGpbbmKq7V9+36 g83C7RDEofMXASPrHUgU5u6FYQ7ceQTuie+ChxxE=
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2498/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Error Code when SETTINGS exceeds maximum (#2498)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c81856657e80_212d3fc47f6d45c4157138"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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: Thu, 07 Mar 2019 20:56:09 -0000

To be precise, STOP_SENDING "_typically indicates that the receiving application is no longer reading data it receives from the stream_, but it is not a guarantee that incoming data will be ignored" ([transport daft section 3.5](

Because there is a chance of it indicating that the peer is no longer reading, STOP_SENDING received on a critical stream ought to trigger a HTTP_CLOSED_CRITICAL_STREAM error.

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