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

MikkelFJ <> Fri, 30 November 2018 20:14 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A1A8F130FA3 for <>; Fri, 30 Nov 2018 12:14:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Status: No, score=-9.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_HI=-5, 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 TcvcE_SM5Jys for <>; Fri, 30 Nov 2018 12:14:55 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1F80D130F78 for <>; Fri, 30 Nov 2018 12:14:55 -0800 (PST)
Date: Fri, 30 Nov 2018 12:14:54 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1543608894; bh=CNro1u6HWn/bX62lEswVKo2nFwSEKnalMrZGTTapvns=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pxyNxFB5bnbC+86sNi+zaKdrr5PaG+175h3yetLZxxeX/gsrD3cYgjI4jEOnSQyZ6 ONquJXHegAslQ/uaPniRrdTE5rhsBHvUxeL5NkgogCTqOravsre03Ahmxj2YC74WPe wB+HxCz9ZycCyF0whATIZk68Cse6b0jf9/QQvK3g=
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_5c019a3e20185_ae43f8cc0ad45bc18327f"; 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
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: Fri, 30 Nov 2018 20:14:57 -0000

I think @huitema's suggestion makes sense.

But ... if a token is tied to a client IP it can't really be used as general amplification attack since the attacker would need to spoof the original client IP. This can direct traffic to a specific client, but I'm not sure this is an effective attack. So we could require tokens to encode the client IP and servers to verify it, or am I missing something?

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