Re: [quicwg/base-drafts] Replace CONNECTION_CLOSE with Public Reset (#353)
martinduke <notifications@github.com> Thu, 02 March 2017 17:58 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 6246A1294F7 for <quic-issues@ietfa.amsl.com>; Thu, 2 Mar 2017 09:58:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level:
X-Spam-Status: No, score=-7 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_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7OSODlQIOZiL for <quic-issues@ietfa.amsl.com>; Thu, 2 Mar 2017 09:58:55 -0800 (PST)
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext6.iad.github.net [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AA471294C9 for <quic-issues@ietf.org>; Thu, 2 Mar 2017 09:58:55 -0800 (PST)
Date: Thu, 02 Mar 2017 09:58:54 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1488477534; bh=WECpBn9uIXoKBJ6uog/JShy+0oZaYh6Cw3pMco+19tE=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=SzSh7N35BtXhQkRw1BbrZBH2gBvUS5ZbsTEFkWAu9RDYBLPN0WCxWD+9lydg3cvID e3JW7Nurgxv1h8/4LaNRKALza7biGjKRdWWCQL/ngBd/wlwPNqY+FtYxeQSsFJvDq8 NI0GGVL4wudkOtSn3gF/ni6KyGjuTJjpd69aF0hU=
From: martinduke <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/353/283729446@github.com>
In-Reply-To: <quicwg/base-drafts/issues/353@github.com>
References: <quicwg/base-drafts/issues/353@github.com>
Subject: Re: [quicwg/base-drafts] Replace CONNECTION_CLOSE with Public Reset (#353)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_58b85d5e71b1d_73253fac1e151c381686b9"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinduke
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/Sclb0s2dZ8lI6eBkVIgCuLlB7ew>
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: Thu, 02 Mar 2017 17:58:56 -0000
(1) and (2): If we decide to eliminate PUBLIC_RESET, then that obviously has implications here. I had detected any sentiment for this to date. (3) I agree that network signaling is the other use case, but in the opposite direction you described. It is a signal from an endpoint to a stateful middlebox that there are no further packets coming on this connection ID. As for your use case, this is the first I've heard of the response to a PUBLIC_RESET being "I'll try the same connection ID on a different path". That is an entirely different purpose than what has been described to date. In fact, I believe the consensus is to _not_ allow middleboxes to generate authentic resets. -- 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/353#issuecomment-283729446
- Re: [quicwg/base-drafts] Replace CONNECTION_CLOSE… MikkelFJ
- [quicwg/base-drafts] Replace CONNECTION_CLOSE wit… Martin Thomson
- Re: [quicwg/base-drafts] Replace CONNECTION_CLOSE… ianswett
- Re: [quicwg/base-drafts] Replace CONNECTION_CLOSE… Martin Thomson
- Re: [quicwg/base-drafts] Replace CONNECTION_CLOSE… mirjak
- Re: [quicwg/base-drafts] Replace CONNECTION_CLOSE… Patrick McManus
- Re: [quicwg/base-drafts] Replace CONNECTION_CLOSE… martinduke
- Re: [quicwg/base-drafts] Replace CONNECTION_CLOSE… Patrick McManus
- Re: [quicwg/base-drafts] Replace CONNECTION_CLOSE… martinduke
- Re: [quicwg/base-drafts] Replace CONNECTION_CLOSE… Patrick McManus
- Re: [quicwg/base-drafts] Replace CONNECTION_CLOSE… Martin Thomson
- Re: [quicwg/base-drafts] Replace CONNECTION_CLOSE… martinduke
- Re: [quicwg/base-drafts] Replace CONNECTION_CLOSE… Mark Nottingham
- Re: [quicwg/base-drafts] Replace CONNECTION_CLOSE… Mark Nottingham