[quicwg/base-drafts] How should an HQ server respond to RST_STREAM? (#1596)
afrind <notifications@github.com> Mon, 23 July 2018 17:10 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 005E6130F37 for <quic-issues@ietfa.amsl.com>; Mon, 23 Jul 2018 10:10:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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_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 toaYJCNurVOQ for <quic-issues@ietfa.amsl.com>; Mon, 23 Jul 2018 10:10:15 -0700 (PDT)
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 498DB130F74 for <quic-issues@ietf.org>; Mon, 23 Jul 2018 10:10:15 -0700 (PDT)
Date: Mon, 23 Jul 2018 10:10:13 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1532365813; bh=hLAg3lQSYFl1J7mDl3b+ML8zYj0Dgu/VE7/rXYyumnc=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=ikVlI3BHAK55J0RDvwXesg/vJTNsqpnIr+f9YL+cDnoYjGL9f9HjISZEcuyE9XcYN ddLiI/sRpupj0Bv2AjLlu2CFCKyr4CDJ38h4rio5X+TY1XofagiS9nrwEN3TbFu5UH KglxiLRVGrIk565cHDNUxnwrQHrErUTy6U9h18vk=
From: afrind <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab402f224dfe81c8ef28b755a38bcc6d8fa48ccb0f92cf00000001176dcdf592a169ce147cbcb8@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1596@github.com>
Subject: [quicwg/base-drafts] How should an HQ server respond to RST_STREAM? (#1596)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b560bf56ceb0_68e3fa25d2d45bc613a5"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: afrind
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/CId01fCAoZaEyAXmjW2EZoH5KP0>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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: Mon, 23 Jul 2018 17:10:24 -0000
If a client sends a RST_STREAM with code HTTP_REQUEST_CANCELLED, the server also needs to reset its end of the stream. As I read the spec, I'm unsure what error code best suits this purpose. 1. STOPPING says it is reserved by the transport in response to STOP_SENDING, so that's not it. 2. HTTP_REQUEST_CANCELLED is allowed S->C, but only if no processing of the request has occurred. What if part of the request has been processed? A corollary question is, if a server cancels a request with a reset_stream, and does not send a STOP_SENDING, is the client expected to reply with HTTP_REQUEST_CANCELLED, a different error code, or continue sending until told to stop? CANCELLED seems ok here, but I dislike the asymmetry. -- 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/1596
- [quicwg/base-drafts] How should an HQ server resp… afrind
- Re: [quicwg/base-drafts] How should an HQ server … Lucas Pardue
- Re: [quicwg/base-drafts] How should an HQ server … afrind
- Re: [quicwg/base-drafts] How should an HQ server … Lucas Pardue
- Re: [quicwg/base-drafts] How should an HQ server … afrind
- Re: [quicwg/base-drafts] How should an HQ server … Mike Bishop