Re: [quicwg/base-drafts] Remove duplicated CONNECTION_CLOSE rules (#3295)

Martin Thomson <> Wed, 11 December 2019 03:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8B8F412006B for <>; Tue, 10 Dec 2019 19:58:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Status: No, score=-6.382 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id L6NvJzcNEmUt for <>; Tue, 10 Dec 2019 19:58:26 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 21E12120044 for <>; Tue, 10 Dec 2019 19:58:26 -0800 (PST)
Date: Tue, 10 Dec 2019 19:58:25 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1576036705; bh=OTh/dzW9cRTQwepRda8C95oeuaa4hpWJYa1FCDT2yiE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zEBdoia7VKyLH3dp6HFpt1dNtFJM3oTn6Nt2jOyu+e7dnrFwRkmI8G6MJCg1Xuz/a 5uXumCrV1P5jlK2rGeVrMz3gZNs4PSeNK3Xpb5DTq4u8O4BZ73SsjBTlvjD5DTHIre U+hlObhIqeY4qZNIX2pn1AevGvb8l17WIsqEjpAY=
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3295/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Remove duplicated CONNECTION_CLOSE rules (#3295)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5df0696119094_3e603facdeecd96492143"; 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
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 11 Dec 2019 03:58:28 -0000

martinthomson commented on this pull request.

> @@ -2489,7 +2483,8 @@ least one of them is processable by the client.  Similarly, a peer might be
 unable to read 1-RTT packets, so an endpoint SHOULD send CONNECTION_CLOSE in
 Handshake and 1-RTT packets prior to confirming the handshake; see Section 4.1.2
 of {{QUIC-TLS}}.  These packets can be coalesced into a single UDP datagram; see
+{{packet-coalesce}}.  After the handshake is confirmed, an endpoint MUST send

Yep, that makes more sense.  Thanks.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: