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

Lucas Pardue <notifications@github.com> Wed, 19 June 2019 14:46 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 3FA37120611 for <quic-issues@ietfa.amsl.com>; Wed, 19 Jun 2019 07:46:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.391
X-Spam-Level:
X-Spam-Status: No, score=-6.391 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_24=1.618, 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A9GlPetY0-fe for <quic-issues@ietfa.amsl.com>; Wed, 19 Jun 2019 07:46:42 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65EDD120686 for <quic-issues@ietf.org>; Wed, 19 Jun 2019 07:46:34 -0700 (PDT)
Date: Wed, 19 Jun 2019 07:46:33 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1560955593; bh=NEUBTqdgDDftKLBF5pktoIjyxfHLgcvK6uAWQT9vi4Y=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=e/JT0u5nOijNKIE/sSvrDcTmpmmVuUbs9IddPubXvY+3AP6ZHl716iAre9sMXyvaQ B0x5r8fskisbqP8eAgqIfEUhk2Lz1WAlOL2vj5EMNLGsZfLnxGpkrZ9DBDrDxqflqB zXcYK5XTxduRxm7h9WlnRGAI9cMZ7t6OBcDw5aVg=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7AFWKCX5OFCKAZCDN3C56UTEVBNHHBWTLI4U@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2816@github.com>
Subject: [quicwg/base-drafts] Handling RESET_STREAM and STOP_SENDING with invalid error codes (#2816)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d0a4ac932b99_46283f91ee2cd96c148649"; 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/Eyi_cmF6jrTgLzFS2hYBlYphpF4>
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: Wed, 19 Jun 2019 14:46:44 -0000

The HTTP/3 spec is a little light on detail about processing an error code that should have never been sent. At @MikeBishop's suggestion, this issue is scoped to discussion of HTTP/3 stream errors:

> If a stream sees a RESET/STOP_SENDING with an error code that a) should only have originated from your side, or b) can only be a connection error, what do you do?

Example a) a client receives a STOP_SENDING with HTTP_REQUEST_CANCELLED
Example b) a server receives a RESET_STREAM with HTTP_LIMIT_EXCEEDED

-- 
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/2816