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

Mike Bishop <> Thu, 06 February 2020 10:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9EC44120233 for <>; Thu, 6 Feb 2020 02:33:01 -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 BKldKHJ3vkVm for <>; Thu, 6 Feb 2020 02:33:00 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CE3581200D6 for <>; Thu, 6 Feb 2020 02:32:59 -0800 (PST)
Date: Thu, 06 Feb 2020 02:32:58 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1580985179; bh=KBF5F912X64tPamuZ3YguH968nSa/aA6UoPCQ8DoOAc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OcIYmHhQvsAHsbqq2pW1OMGr6MeU5smDefGUbe4f54LGoDBP+g41ykiFwW4aPmceT ZpdXYfBM9Erxbd4m/2Ack99frqtrZTXcYwIDsHncfzUJJ9X5L4OlwSMtLaxlX10iy9 BU8QW0gQGOJEa+PMfWcpHTl5Jiq15Ut7DMG4gZ/A=
From: Mike Bishop <>
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_5e3beb5af0d06_50963fc30f4cd968189541"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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, 06 Feb 2020 10:33:02 -0000

After sending CONNECTION_CLOSE, the client is supposed to enter the draining state and stop sending other than to repeat the connection close.  However, the server might reject 0-RTT, in which case the server doesn't know the connection has been closed.  I see the principle for including it, but I agree with @kazuho that we should advise clients that it's kinder to send the CONNECTION_CLOSE at other encryption levels as well / instead to ensure the server can read it.

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