Re: [quicwg/base-drafts] Where can you send CONNECTION_CLOSE (#2151)

Martin Thomson <notifications@github.com> Thu, 13 December 2018 23: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 05B8D130ED7 for <quic-issues@ietfa.amsl.com>; Thu, 13 Dec 2018 15:58:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.056
X-Spam-Level:
X-Spam-Status: No, score=-8.056 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 j5bqk0ACTh-O for <quic-issues@ietfa.amsl.com>; Thu, 13 Dec 2018 15:58:36 -0800 (PST)
Received: from out-10.smtp.github.com (out-10.smtp.github.com [192.30.254.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6064A130E26 for <quic-issues@ietf.org>; Thu, 13 Dec 2018 15:58:36 -0800 (PST)
Date: Thu, 13 Dec 2018 15:58:35 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1544745515; bh=Od6buXvTSF4Y/xDrDxIrMg43tx2rtg8Ahu0Q3Ee0iJw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=IC0gKmsNHKMFM/ItET5HeLrQZFCxmSJOPpD4P5izQGB4BByHFAwzhJKbS2beSupPj Tuswo1Vlu1+7gOBCOfQZOJvHWJE/Wj9SPTtntesXddwsV8ZXw+34ksN8pVvJgKWOWU g7OblLCskDCjo9w5LW35W7CVE2FgX581uwDMjZq0=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abc50618fc17f3f990cdf6a32df18d4308aba9d92192cf00000001182ab42b92a169ce174b9201@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2151/447164678@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2151@github.com>
References: <quicwg/base-drafts/issues/2151@github.com>
Subject: Re: [quicwg/base-drafts] Where can you send CONNECTION_CLOSE (#2151)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c12f22b6e1a9_410d3fe1670d45c01749a8"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/ZJA7PZkBdp7iN-9dUop87YJ-gnU>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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, 13 Dec 2018 23:58:39 -0000

The intent is for the peer to be able to read the packet, thus the recommendation to use a lower level if you aren't sure that they have the right keys.  If they have the right keys, then they will ignore the Initial packet, if they don't then it's better to signal the error than have them keep trying.

I think that this is OK.  Do you have a specific concern with this design? Or the specific text?

-- 
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/2151#issuecomment-447164678