Re: [quicwg/base-drafts] Immediately close with INVALID_TOKEN (#3107)

Martin Thomson <> Tue, 22 October 2019 04:29 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B6529120058 for <>; Mon, 21 Oct 2019 21:29:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.596
X-Spam-Status: No, score=-1.596 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_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 2ArTVpDucgRA for <>; Mon, 21 Oct 2019 21:29:51 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C248A12004F for <>; Mon, 21 Oct 2019 21:29:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=TCGGGUX+ToV6gO/cCLcAyuDb0g0=; b=bZ5GU3lx8cce/KcA XSEvi1g64Vm4ZBpEBGyQE8xJHmz3GaEzSfBe9ZY70YOmFMeDPFATsCi1L8lgUTT4 xWlbQVqvIrWE+Ca22JLYcEtJmJlHu/Ed8IPRfDl78lTFiEdKTHjs3iVZFrfRstC7 Ceo47tW12ogiUJCXySIDdjrO3ak=
Received: by with SMTP id filter1913p1mdw1-18808-5DAE7628-16 2019-10-22 03:23:20.884383371 +0000 UTC m=+354614.726225955
Received: from ( []) by (SG) with ESMTP id 4Z0Ny3g-T4mvVgxoJZFBkQ for <>; Tue, 22 Oct 2019 03:23:20.729 +0000 (UTC)
Date: Tue, 22 Oct 2019 03:23:20 +0000
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3107/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Immediately close with INVALID_TOKEN (#3107)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dae76239359_340a3fc6512cd95c1044b7"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1eyTek7088YADyYNY6pd1Ghf23w3bmy2OiUX vnzX7Il6dUNyLhIKfJV1ovRfuktHywaybiDi4T9YbtsPvuZpkx6KiYb2jIKdSRvUI1SZeQZggMbbty tTuEqdty8wsZLmSgBXHjHASbwr4XvWMw9pV4I2TFtUf+2ILkd8x1ruTfKt/hqDJbPIMrz240JIspk6 w=
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, 22 Oct 2019 04:29:54 -0000

martinthomson commented on this pull request.

> @@ -1641,6 +1641,14 @@ of connection establishment.  By giving the client a different connection ID to
 use, a server can cause the connection to be routed to a server instance with
 more resources available for new connections.
+If a server receives a client Initial with a unverifiable Retry token,
+it knows the client will not accept another Retry token.  It can either
+proceed with the handshake without verifying the token or immediately close

I'm persuaded by Marten's comment here (which I missed at first, I think because we commented at almost the same time).

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