[quicwg/base-drafts] Does it matter if the the STOP_SENDING error code is something other than EARLY RESPONSE? (#3130)

Mike Bishop <notifications@github.com> Tue, 22 October 2019 22:38 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 []) by ietfa.amsl.com (Postfix) with ESMTP id DBCBB120122 for <quic-issues@ietfa.amsl.com>; Tue, 22 Oct 2019 15:38:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Status: No, score=-8 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_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 7-v8oucsZu7g for <quic-issues@ietfa.amsl.com>; Tue, 22 Oct 2019 15:38:40 -0700 (PDT)
Received: from out-19.smtp.github.com (out-19.smtp.github.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E66912012C for <quic-issues@ietf.org>; Tue, 22 Oct 2019 15:38:40 -0700 (PDT)
Received: from github-lowworker-3a0df0f.ac4-iad.github.net (github-lowworker-3a0df0f.ac4-iad.github.net []) by smtp.github.com (Postfix) with ESMTP id CE40B5210C2 for <quic-issues@ietf.org>; Tue, 22 Oct 2019 15:38:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1571783918; bh=o8nkJRp1+m43snQymZByMHktSzaxIoArTuOaKZgIVpY=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=kABkJNwDlMg5bAMhmaEhsP2CdNoAkvtBwYOQMLBTaZUUQldnfY4beVqPZyD2nRTJN 1cq428af/ACIm0r/WXWN8XjTsgUDuaukm808kZm64IwcULvZYT0c3yc429WK9w+XKg DW8WuBVVuUYMiFMPbMPxzYzQazGuu1da2xc79wko=
Date: Tue, 22 Oct 2019 15:38:38 -0700
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKY6EBQE2GIPRR3WPNF3XTCX5EVBNHHB45F65Y@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3130@github.com>
Subject: [quicwg/base-drafts] Does it matter if the the STOP_SENDING error code is something other than EARLY RESPONSE? (#3130)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5daf84eebf830_2f753fddf12cd96811047b4"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/efbSENT-Ik2nLdMMBS8zWdyRFoo>
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: Tue, 22 Oct 2019 22:38:42 -0000

Does it matter if the the STOP_SENDING error code is something other than EARLY RESPONSE?

_Originally posted by @RyanAtGoogle in https://github.com/quicwg/base-drafts/issues/2963#issuecomment-543883212_

Moving this out to a separate issue to avoid complicating #3123; my inclination is to propose the following rules:

- When a STOP_SENDING is received, if the error code has semantics in the context in which you received it, follow the semantics.
- If the error code has no semantics in that context (or at all), then take no action (other than resetting the stream, as required by the frame)
- If resetting your request stream causes the server to be unable to generate a response, it will reset its stream.  If it sends a complete response, the server clearly got everything it needed; the response is usable.
- If a response stream is reset after all bytes have been received, the response remains usable; no takebacks.

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