Re: [quicwg/base-drafts] RST_STREAM and connection-level flow control (#163)
Mike Bishop <notifications@github.com> Tue, 17 January 2017 17:31 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 D9F8A128874 for <quic-issues@ietfa.amsl.com>; Tue, 17 Jan 2017 09:31:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.951
X-Spam-Level:
X-Spam-Status: No, score=-4.951 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_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-1.156, RP_MATCHES_RCVD=-3.199, 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ajIF7_vu-Z1l for <quic-issues@ietfa.amsl.com>; Tue, 17 Jan 2017 09:31:03 -0800 (PST)
Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 36680120725 for <quic-issues@ietf.org>; Tue, 17 Jan 2017 09:31:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=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=h7eP82XNOJiDsSjEL4J4TpWAFX4=; b=bwQ54IkzE5n6wrle wLCyneE0ZOi19v08a28LFlq8go3t4YDOIHmArX+YUoWrNHnW9Ip/JyImD2y7TA5c EFvgWiGaw2RgaxchlWwqsjqa/L3K2I64gxO6vo5MKJi+GGYY0htDIL9LTVYBwhYe MoFkF53RS5PMGBew2OYiIZv3RKU=
Received: by filter1120p1mdw1.sendgrid.net with SMTP id filter1120p1mdw1-29154-587E54CD-61 2017-01-17 17:30:53.567470583 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id 6p1dYJ9zTdmGt7UGwKe7Dw for <quic-issues@ietf.org>; Tue, 17 Jan 2017 17:30:53.496 +0000 (UTC)
Date: Tue, 17 Jan 2017 09:30:53 -0800
From: Mike Bishop <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/163/273238775@github.com>
In-Reply-To: <quicwg/base-drafts/issues/163@github.com>
References: <quicwg/base-drafts/issues/163@github.com>
Subject: Re: [quicwg/base-drafts] RST_STREAM and connection-level flow control (#163)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_587e54cd5da30_38393fd0bfa85140122957"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3t+deok/yWUNbN+131l2Wf+r/6qZXHNww++7 McZL/3R31kYiGMehrrvaZwabCVsy0NfVGp7iCgx2qs2+dnSNy624zSEC6XV2Yk6SolLjiEYQK2YWE2 mN8WddkJrDixdnVx2jYesebEhO4bYxaG1qYHDdK/9GBkCFyJDmpYdZGKsO3bDlterm6oyWp3QP+Rbs M=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/oVBm9X2b7hYnZxYGi7s7MolBxlU>
Cc: Subscribed <subscribed@noreply.github.com>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: quic@ietf.org
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, 17 Jan 2017 17:31:05 -0000
Yes, I think RST_STREAM in response to a RST_STREAM is probably the best solution here. And I think the set of error codes that are in Chrome's code but not in the spec includes an error code for "received RST_STREAM." If you receive a RST_STREAM with any error code other than that one, you MUST generate a RST_STREAM with that error code. -- 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/163#issuecomment-273238775
- Re: [quicwg/base-drafts] RST_STREAM and connectio… Mike Bishop
- [quicwg/base-drafts] RST_STREAM and connection-le… Martin Thomson
- Re: [quicwg/base-drafts] RST_STREAM and connectio… Mark Nottingham
- Re: [quicwg/base-drafts] RST_STREAM and connectio… Mark Nottingham