Re: [quicwg/base-drafts] clarify that HANDSHAKE_DONE, NEW_TOKEN, PATH_RESPONSE, RCID frames MUST NOT appear in 0-RTT (#3431)

Christian Huitema <> Thu, 20 February 2020 20:26 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 29741120119 for <>; Thu, 20 Feb 2020 12:26:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Status: No, score=-6.454 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_20=1.546, 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 ZhsyMbm1BT7O for <>; Thu, 20 Feb 2020 12:26:42 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7ED2C120088 for <>; Thu, 20 Feb 2020 12:26:42 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 69AEF52041B for <>; Thu, 20 Feb 2020 12:26:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1582230401; bh=zh2smIodLqrgXdkNQ5WuKniRidMosl9D6wMMEt/8oik=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mRexpVy5suYDRObK8yuMiE9eQeAZGIO5N1s77iDNVnVCwyQoCYgCKDQC3ESEugX2E TXL7yYap7eBXuclrN0tk+lVRIBJ4ja72L4RXo0uugs1aFWcgqJAxz7TnYl9Ph6qLtJ OPW6ExO54a2W74BgahDQz1WO3iNllu5cK1B4tqP8=
Date: Thu, 20 Feb 2020 12:26:41 -0800
From: Christian Huitema <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3431/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] clarify that HANDSHAKE_DONE, NEW_TOKEN, PATH_RESPONSE, RCID frames MUST NOT appear in 0-RTT (#3431)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e4eeb815acca_406d3faf038cd95c32137c"; 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, 20 Feb 2020 20:26:44 -0000

I still think that we have an issue with Retire Connection ID. The current spec allows to send "Retire Connection ID 0" in a 0 RTT packet if the 0-RTT packet is sent to the Initial CID. It is different from CID #0, so that meets the text in 5.1.2 -- but that would cause the handshake to fail. I would like to treat any such RCID as a protocol violation.

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