Re: [quicwg/base-drafts] Allow application CONNECTION_CLOSE everywhere (#3446)

Kazuho Oku <> Thu, 13 February 2020 06:07 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1FB071200A3 for <>; Wed, 12 Feb 2020 22:07:57 -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 3QiAlNbWTQ0h for <>; Wed, 12 Feb 2020 22:07:52 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EAFA912007A for <>; Wed, 12 Feb 2020 22:07:51 -0800 (PST)
Date: Wed, 12 Feb 2020 22:07:50 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1581574070; bh=lSn2Eq/kMUgTSwAuevOACtObaifWMnGCMSqUDbzSRw0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=As+obM+ry42Q/1uZvUdgw7nPwInzT24KxNE7OmV/ZmzSMG8ufYuzL0YRuZL2JfM8z QANwxLkyqvwXj16DaG54JkE/Ez9b/pEvYGCw1y4OJeAGdCfEsVKOJkTyJni885BE8f fYkO64VM1u2/LG6G56sjLx2xFmgi2gy5DSWnGyi4=
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3446/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Allow application CONNECTION_CLOSE everywhere (#3446)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e44e7b6c815b_46383fd70e8cd96095747"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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: Thu, 13 Feb 2020 06:07:57 -0000

> I suspect that the right answer is to switch to a transport-level CONNECTION_CLOSE with a different error code in that case.

Agreed. FWIW, we state the following, which I think is the right advice.
_When an application wishes to abandon a connection during the handshake, an endpoint can send a CONNECTION_CLOSE frame (type 0x1c) with an error code of 0x15a ("user_canceled" alert; see [TLS13]) in an Initial or a Handshake packet. ([section 19.19](

> Allowing application CONNECTION_CLOSE in 0-RTT would still make sense then, if only to keep the API surface consistent.

No objection from me.

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