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

MikkelFJ <notifications@github.com> Fri, 14 December 2018 00:35 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 3092C130EC9 for <quic-issues@ietfa.amsl.com>; Thu, 13 Dec 2018 16:35:20 -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 hcTV1uyXa73K for <quic-issues@ietfa.amsl.com>; Thu, 13 Dec 2018 16:35:18 -0800 (PST)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43300130EC2 for <quic-issues@ietf.org>; Thu, 13 Dec 2018 16:35:18 -0800 (PST)
Date: Thu, 13 Dec 2018 16:35:17 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1544747717; bh=aG+bJga7f8ZSIKVzqaawO+7e4wc8rDam9n8W/NnitLs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=C5JD5igRFCSTuUJReaTAYaDNyHqOsWdRcFt5HXN748i2vT6s/W7WwygVFyc4tR+/F k0DkpdJ0yls3FWpayiz9BJcErRxEBv74ImajB7my+xpA5UiebrIBa/kJRt6KVbmRjY qckKb78Lv3cHDv1z2nlVhg1GsCH5dN1PLS8xAAl4=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab12312d52e0b56aa1b92b8f311510026992bfb91892cf00000001182abcc592a169ce174b9201@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/447171892@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_5c12fac53d25c_5b1a3fec8e6d45c411617"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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/ZDApklfBqFq2N-gGn5geGpvBUp0>
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: Fri, 14 Dec 2018 00:35:20 -0000

An endpoint could logically migrate to the next packet number space / encryption level for new transmissions while still keeping the previous level for retransmissions. If the connection dies before retransmission the peer might not be able to read latest crypto level even if this is where you normally send new data. It is easier and safer to send CLOSE on both channels rather than retransmitting the handshake history.

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