IETF Logo Mail Archive

Re: [quicwg/base-drafts] How should an HQ server respond to RST_STREAM? (#1596)

Lucas Pardue <notifications@github.com> Mon, 23 July 2018 17:15 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 5A694130E20 for <quic-issues@ietfa.amsl.com>; Mon, 23 Jul 2018 10:15:35 -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 caRi_v5OGDNl for <quic-issues@ietfa.amsl.com>; Mon, 23 Jul 2018 10:15:33 -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 4DAF6130DEA for <quic-issues@ietf.org>; Mon, 23 Jul 2018 10:15:33 -0700 (PDT)
Date: Mon, 23 Jul 2018 10:15:32 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1532366132; bh=ll1pmepT5iOObNPHBtupcwAExmnjmVOOjtx461b9mtc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gS5+DmG14ETD+bTFkr+zbXbeJ5JI9aDoApPQT5zJNdHidMZ6pAwEqGJf50a5kcURs /iui3TJyQfEDf43TABcTylltq4foYOd+BVRkzuPe8ew3MX9k4oT/hjyXkjotpb93fd Vu0HZRlD84At/1hu/sMnekJcZLSlc0uEOiJrboxI=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab84f62f6ad12aa910d316f64bfa53b605aaeca0dd92cf00000001176dcf3492a169ce147cbcb8@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/407133510@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1596@github.com>
References: <quicwg/base-drafts/issues/1596@github.com>
Subject: Re: [quicwg/base-drafts] How should an HQ server respond to RST_STREAM? (#1596)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b560d341eadc_68933fdd084d45c0273c2"; 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/OWyuXQTG4ihEBEuFEi5tP-kVMJ0>
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:15:36 -0000

Some random thoughts:

* use HTTP_NO_ERROR
* Can't you just FIN the stream?
  * Section 3.1 says "Servers MUST NOT abort a response in progress as a result of receiving a solicited RST_STREAM." - which might rule this out...

-- 
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#issuecomment-407133510

v2.39.1 | Report a Bug | By Email | System Status