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 21:51 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 DC5FD130DF9 for <quic-issues@ietfa.amsl.com>; Mon, 23 Jul 2018 14:51:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.01
X-Spam-Level:
X-Spam-Status: No, score=-3.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_NONE=-0.0001, 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 OqTb3wehMnwc for <quic-issues@ietfa.amsl.com>; Mon, 23 Jul 2018 14:51:19 -0700 (PDT)
Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85C11130934 for <quic-issues@ietf.org>; Mon, 23 Jul 2018 14:51:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=4u9h1TmUWLw4WylegYbCOyDZ5+w=; b=RwOYHapM2/t1nQOU u1jJrfbRcm04KKqI1h2zs8Kaxng1ZshIXFICqfiRorZqCkC2cyh6PuHCL8QR660a mOuZ4u21qmQTh9JDknSrvjvjgkQUx7uSfxCb0GuSpwkY8XGeMMrEuQdzCbZjebZS A4ObKqE9ccNrkLSJx37EXsLIF8o=
Received: by filter1700p1mdw1.sendgrid.net with SMTP id filter1700p1mdw1-21336-5B564DD5-E 2018-07-23 21:51:17.419161693 +0000 UTC m=+515796.634084596
Received: from github-lowworker-dc5ea3e.cp1-iad.github.net (unknown [192.30.252.45]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id IZ7JxUi9RDmHh1OsIKRzmw for <quic-issues@ietf.org>; Mon, 23 Jul 2018 21:51:17.395 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-dc5ea3e.cp1-iad.github.net (Postfix) with ESMTP id 5E9EF261922 for <quic-issues@ietf.org>; Mon, 23 Jul 2018 14:51:17 -0700 (PDT)
Date: Mon, 23 Jul 2018 21:51:17 +0000
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abc933e43ff8414e6aabb853143dafdd28833d81b292cf00000001176e0fd592a169ce147cbcb8@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/407212814@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_5b564dd55c98c_51bd3fb44e2d45b4114352"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak02TIMnKFrE9DJhXOeoNjZAdmz3/bHyAlOzWz YG5kx5m/x5TLFSbNyCWt1exITUMUJXda9vqZgEA2YNhcVkpas2nDibrtIXW2ktKbi3zgzUrs5i5JBa 68MBrksA9BkRkw9a8pRYn40XDgtsGGB590Tj/pbL7vi63ES7vz+w0eswXMFMrqrORpEV/is4BASFh0 s=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/K9q4NKKpp_VHAnQ1qXyhYdP3uzw>
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 21:51:22 -0000

I understand your points and don't have a strong preference. 

The HTTP mapping has previously been accused of too many, too specific errors. So the question to ask would be, would your implementation do anything different if it received RST_STREAM with different application error codes?

-- 
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-407212814

v2.23.0 | Report a Bug | By Email