Re: [quicwg/base-drafts] Allow reuse of stateless reset tokens (#2733)

Martin Thomson <> Wed, 22 May 2019 15:45 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 214DA12015B for <>; Wed, 22 May 2019 08:45:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.606
X-Spam-Status: No, score=-1.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 kXsrPRgTw-Kb for <>; Wed, 22 May 2019 08:45:23 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 505BC120157 for <>; Wed, 22 May 2019 08:45:23 -0700 (PDT)
Date: Wed, 22 May 2019 08:45:22 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1558539922; bh=c2OHcuqVlO0ooUg9c5AQYNiRy+VjuYC7oqgHqU2ew30=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Khle+NsX6nQ5QmCp4GMzZDCoK7AhnpccQ2wBB47KBrwvgbrfapBbTiusa7TUToDZc stjj1nqypLIq9CsPM54HIPjywvnmFAersATYQn6tfi0a4viN46jBp8EJ6mAuVXQuke ghLeWH5X5l5YQVDuUNG7QCihM92WWv7EgDwXbsI0=
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2733/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Allow reuse of stateless reset tokens (#2733)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ce56e9266d1a_4a4c3fd0ad6cd96019836ba"; 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
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, 22 May 2019 15:45:25 -0000

martinthomson commented on this pull request.

> @@ -2476,6 +2476,14 @@ the same static key (see {{reset-oracle}}).  A connection ID from a connection
 that is reset by revealing the Stateless Reset Token MUST NOT be reused for new
 connections at nodes that share a static key.
+The same Stateless Reset Token MAY be used for multiple connection IDs on the
+same connection.  An endpoint that reuses a Stateless Reset Token MUST ensure
+that any connection ID used on the connection is matched to the active
+connection, including any routing performed at load balancers, even when a
+connection ID has been retired.  Otherwise, an attacker might be able to send a
+packet with a retired connection ID and cause the endpoint to produce a
+Stateless Reset.
 Note that Stateless Reset packets do not have any cryptographic protection.

That doesn't quite work because it is OK to forget a connection ID if the associated stateless reset token is no longer in use.  Maybe I need to try again.

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