IETF Logo Mail Archive

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

Kazuho Oku <notifications@github.com> Thu, 07 March 2019 03:00 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 089F513114E for <quic-issues@ietfa.amsl.com>; Wed, 6 Mar 2019 19:00:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.384
X-Spam-Level:
X-Spam-Status: No, score=-6.384 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O6FTWNjdg0l3 for <quic-issues@ietfa.amsl.com>; Wed, 6 Mar 2019 19:00:32 -0800 (PST)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF96E13131F for <quic-issues@ietf.org>; Wed, 6 Mar 2019 19:00:31 -0800 (PST)
Date: Wed, 06 Mar 2019 19:00:30 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1551927630; bh=nZIcUatS/eZ02rul7ZJA2KyWI+BdeGbX/uJRwijJVh4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=LOaD5D+1MPW7FH/p6dR/VU9HfV4TP+EwlNc97+weiV0J/3gTzDfWCSZiOpMS3mU1a twRV0VnGHd2dA1RmKVT+Pls6xgGQ1ZozxzSkuBP5qJlmg8zJ8VEAZBdBnpqEO/dUIR eFAWOD47Mh5YBYuIaRqqZLQ+AXsFbu0i63OgVfPo=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab233600897a636223d4f7d0c9f0524e997bb8365392cf0000000118984b4e92a169ce18e306e0@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2498/470365248@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2498@github.com>
References: <quicwg/base-drafts/issues/2498@github.com>
Subject: Re: [quicwg/base-drafts] Error Code when SETTINGS exceeds maximum (#2498)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c80894eb0b29_728b3fac7b4d45c43794f7"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/y5mVf04p4lVJJ_Txnq95_8owFkg>
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, 07 Mar 2019 03:00:34 -0000

My understanding is that STOP_SENDING is an act of closing a stream rather than an advisory signal.
Based on that, I'd argue that receipt of STOP_SENDING on a critical stream should trigger a HTTP_CLOSED_CRITICAL_STREAM connection-level error.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/2498#issuecomment-470365248

v2.23.0 | Report a Bug | By Email