Re: [quicwg/base-drafts] Server cannot proceed after invalid Retry token (#3396)

Kazuho Oku <> Wed, 29 January 2020 01:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DF0DA1200EF for <>; Tue, 28 Jan 2020 17:20:17 -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 Wwwppmlyv2By for <>; Tue, 28 Jan 2020 17:20:16 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 26AC5120105 for <>; Tue, 28 Jan 2020 17:20:16 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 4CB9A660079 for <>; Tue, 28 Jan 2020 17:20:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1580260814; bh=joInCOFRZuB3DB9L43pfwsJmJlzeixzNebILSm8/+nY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=TnnQUgkPXsFesWNx4ydgwXyO3cnZTQ+bX1yuOoroRY/oWLwQn4Jm/ii9tMAjHkJpK XpouAds1Govd+Xrz/kbZXKgR2HhYa6XeczwIemWqu+XaCO38c7ftUdfdxcQcW9QLyA j8vxkFoE7TFbp/sA1j8jGvr03Jrvfw3HHnrqQ7bs=
Date: Tue, 28 Jan 2020 17:20:14 -0800
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3396/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Server cannot proceed after invalid Retry token (#3396)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e30ddce4406d_64d13fb9e46cd968117032"; 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: Wed, 29 Jan 2020 01:20:18 -0000

As pointed out by @marten-seemann and @dtikhonov, the client would reject the handshake even if the server ignores the token and proceeds with the handshake. This is because TP.original_connection_id would not contain the expected value.

I now agree that this MAY is awkward and that we can strike the sentence.

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