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

Mike Bishop <> Tue, 28 January 2020 18:51 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7FCDC12003E for <>; Tue, 28 Jan 2020 10:51:52 -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 uApgXnxLIIfA for <>; Tue, 28 Jan 2020 10:51:51 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D8C40120033 for <>; Tue, 28 Jan 2020 10:51:50 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id B3812C61754 for <>; Tue, 28 Jan 2020 10:51:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1580237509; bh=chuEsbEDdRYqfsEX8VJfJoGGvc86lPk9d7zwvsBKuMU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Z6KH89epx56PVGNRhQW0ZxrNDI2b+Aht4neRirDeYc762JCGGGhuCbh7koW7LpPMw 0yT9CFthaq9/Jvz3iv4hWhvDO+2rM+6whnLZeQKPs++xGPFkS7KGgvjmLrbxzA6RZv K73wmN4NoeYbhQ/9wweWFoA2YzKnx8FdK98cBeuM=
Date: Tue, 28 Jan 2020 10:51:49 -0800
From: Mike Bishop <>
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_5e3082c5abab2_6a8f3fd75dacd9642157dd"; 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: Tue, 28 Jan 2020 18:51:52 -0000

The only case in which the server can proceed is when the server sees a junk token, but knows that the client does not consider it a Retry token.  There's no mechanism for the client to tell the server what it thinks the token it has presented is, so the server doesn't know when it's in this state.  I agree -- axe it.

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