Re: [quicwg/base-drafts] Handling RESET_STREAM and STOP_SENDING with invalid error codes (#2816)

Mike Bishop <> Wed, 19 June 2019 18:17 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BCF4C12083C for <>; Wed, 19 Jun 2019 11:17:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.463
X-Spam-Status: No, score=-6.463 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_20=1.546, 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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id By4HbEI-eVrr for <>; Wed, 19 Jun 2019 11:17:58 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D920B1208A8 for <>; Wed, 19 Jun 2019 11:17:35 -0700 (PDT)
Date: Wed, 19 Jun 2019 11:17:34 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1560968254; bh=FVFX0I1620/lVL8wKgugJ6bWGV30ox8i9Oe1RRoJYJM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=vgHLF6tPmtZzDyjU5YyPZnUw84UKYH2gGGifchzbGsELwSTSbOgFjxNNdKDrm3Zo8 Mwo26rbzMljUj6Hm0sgVka846bC2NMDRfvp2bQElQTrvZd7GAkdy6hhQ/eKWBQnTZR yvgG5heRBJI6Xrdqdf1mEmJI44q8JGYwI2D36EbE=
From: Mike Bishop <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2816/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Handling RESET_STREAM and STOP_SENDING with invalid error codes (#2816)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d0a7c3e99a8b_770c3fba8accd95c34959c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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: Wed, 19 Jun 2019 18:18:04 -0000

I'm mostly inclined to treat this with the same fatalism as an invalid code in an APPLICATION_CLOSE code that makes no sense.  The stream is gone, regardless of the error code.  If it was a critical stream, then CLOSED_CRITICAL_STREAM; otherwise, perhaps a MAY GENERAL_PROTOCOL_ERROR?

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