Re: [quicwg/base-drafts] Amplification attack using retry tokens and spoofed addresses (#2064)

MikkelFJ <> Tue, 04 December 2018 11:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E4348130EC2 for <>; Tue, 4 Dec 2018 03:24:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.46
X-Spam-Status: No, score=-4.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 QdNZlKoXDJpd for <>; Tue, 4 Dec 2018 03:24:26 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 26BAA12875B for <>; Tue, 4 Dec 2018 03:24:26 -0800 (PST)
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=wQesgjzfvOpfnLU8jPsNz+IzYuw=; b=xWLtXSdbqYGcgLrd fkcX1NfpbNVRrZkA2L27ikP7rZEbEtZz99QLemooF0V3XjQA2y/nD5BFZ4pRpd3n CorkaJDA6oJp/jC58ZGfhbgHT0W5fUW1NHehoUEqukhNjpF5KjbAdoPLFHwWhUsu vcE/BFj4chW+vYYtyQBEd0rffbs=
Received: by with SMTP id filter1037p1las1-435-5C0663E9-2 2018-12-04 11:24:25.093022751 +0000 UTC m=+39467.712836675
Received: from (unknown []) by (SG) with ESMTP id g8euikL3QxCepNa1p1jlkQ for <>; Tue, 04 Dec 2018 11:24:25.024 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id F06B04C031F for <>; Tue, 4 Dec 2018 03:24:24 -0800 (PST)
Date: Tue, 04 Dec 2018 11:24:25 +0000
From: MikkelFJ <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2064/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Amplification attack using retry tokens and spoofed addresses (#2064)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c0663e8ee7a3_6b5f3f81a80d45bc2225aa"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3ZjX0qlwOpNgHYUzAZv53d3bV/rhMulBuEUq 7g44AOpt91Q7/bHd2EjI2UdCrVx4gKmvxqxr3oMkOCAy0CsDktcWyZ2TdFnWtoBdcNtTPBBZM9auR1 gqEBuwGcqjd2jQapqK3Ni1pMobxR73Lo4Ln3yXlD8f85eNF4yJjDn/J8RQ==
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, 04 Dec 2018 11:24:28 -0000

We may need some sort of linearisation if "once" is ever going to be practical, such as the client only using last received token, but I don't see how that could be accomplished in praxis. So in effect a server would need to explicitly track all outstanding tokens which may be too much even for a single server deployment.

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