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

Kazuho Oku <> Wed, 12 June 2019 21:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 79EDB1200D7 for <>; Wed, 12 Jun 2019 14:48:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id IDvMqpUoG1bi for <>; Wed, 12 Jun 2019 14:48:54 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id AB67312019C for <>; Wed, 12 Jun 2019 14:39:40 -0700 (PDT)
Date: Wed, 12 Jun 2019 14:39:39 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1560375579; bh=sr8xqFCe9Uwka32ZjDFRWYuyXQikDJKp51JuCdZRFAQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Gtg3OGbGiM5okKDtouXBm4gZi86WCPopI4Ox9bgF6TibWG4+g8OwpTNCwHoW/1dAr d5eAI3Qu1VhWlmO4RsZmBLGiiw9YZfRxESNRBERvFxCI4WFTThW1jwfph6CBJx068k IpAZlwdY1tBuWLTEGlNgZ2CWWsZNhZ1Wb/Y67YmY=
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2785/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Disallow reuse of stateless reset tokens (#2785)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d01711bd9b9c_125c3f95b16cd96019540"; 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, 12 Jun 2019 21:48:56 -0000

> Apologies for not raising this on #2732, I had not thought about the problem at that time.

It's my understanding that #2769 _is_ introducing this issue. There is no problem in the current design, because receiving a packet with an outdated CID is not expected to cause a stateless reset.

Regarding why you'd want to reuse a SRT, the simple reason is because you do not need to create different SRTs for every Connection ID.

A QUIC stack that generates a CID by a construction like `AES_ECB(cid_key, conn_id || path_index)`<sup>1</sup> can use `HMAC(srt_key, conn_id)` as a construction for generating SRT. 

For QUIC stacks that aren't interested in retiring CIDs (which seems to be the majority for me), this construction makes sense. I think my preference would be to retain the design; it's just about adding a warning when you want to retire a CID.

1: path_index is a sequence number of path for each connection

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