Re: [quicwg/base-drafts] Allow CONNECTION_CLOSE in 0-RTT (#3435)

Christian Huitema <> Thu, 13 February 2020 04:39 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 75C391200A1 for <>; Wed, 12 Feb 2020 20:39:37 -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 wjL9Qt-mukvv for <>; Wed, 12 Feb 2020 20:39:36 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DDDEC12008A for <>; Wed, 12 Feb 2020 20:39:35 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id B77B82C0ECF for <>; Wed, 12 Feb 2020 20:39:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1581568774; bh=XeZGBHkbWLwvr/z9/p1/tUHxnfKEmYrJOAMsl5x7g5I=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ecX7IxD0ZBolIywGTpGkJ86t/RPysxHxX868weTbVWe+JkFhwOTcMMS0ICCxvF1Mn keTIODHt818iMzJnXUnFWSx/zCUF7DspXXKIgU08LiM9MPfrXsl84hHkXRXznaDyMw XZ647HMTZPEUuCfIlEAN+1bmD5oXdOAPj7cnLyI0=
Date: Wed, 12 Feb 2020 20:39:34 -0800
From: Christian Huitema <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3435/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Allow CONNECTION_CLOSE in 0-RTT (#3435)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e44d306a738d_65f53fc9e4ccd95c119193"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: huitema
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 04:39:38 -0000

The testing of that feature is going to be interesting. Besides the case of servers that just don't negotiate 0-RTT because they don't feel like it today, there is also the case of 0-RTT packets being lost. The loss is not guaranteed to be detected before the TLS handshake complete. A bad faith server could just ignore any 0-RTT packet that carries a connection close request, and do as if it was not received. I get the desire of treating 0-RTT just like 1-RTT, but the number of corner cases is going to be fun.

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