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

Mark Nottingham <> Wed, 22 May 2019 15:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 34765120182 for <>; Wed, 22 May 2019 08:00:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Status: No, score=-8.01 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_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, 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 gV7UYt5k6AAa for <>; Wed, 22 May 2019 08:00: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 0A5A912019F for <>; Wed, 22 May 2019 08:00:23 -0700 (PDT)
Date: Wed, 22 May 2019 08:00:22 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1558537222; bh=dm0QVh90mm7BB2eqSl/SGkWWLCFETsqIBBFSOkrdbks=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=2bvSrWtOdZwz3NatW5U3NslG1v2N6kneTBl8JICCo/RoML4UrKmXL4+POv6BMMMH9 govnSXMvgugUSXmSNDZccrkm5BQe0RzA0R+rP0VsGya4ToiZMLDf54vNla0z7BtaiB YXhkV+IwSxBus6az3ujby0y2rxFvy2xmm1JyL4zo=
From: Mark Nottingham <>
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_5ce5640612765_3cd3fb1812cd9641485679"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mnot
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:00:26 -0000

mnot 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.

@mikkelfj can you clarify what this comment is in relation to?

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