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

janaiyengar <> Fri, 30 November 2018 02:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A0DE0126BED for <>; Thu, 29 Nov 2018 18:56:09 -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 2y5lOciQNuvz for <>; Thu, 29 Nov 2018 18:56:08 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2736C12008A for <>; Thu, 29 Nov 2018 18:56:08 -0800 (PST)
Date: Thu, 29 Nov 2018 18:56:06 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1543546566; bh=anXvm6n11uYDDakYNRZOMoxBEZHOuHgGtZCyMWmiMKI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qRSAF7MbVqZion3UHh7irqTppM3HRkYFH7MWgZmsLJTPMUppSqhsNtPIrhG9ZW861 WG4WIiXB5NTK2PKOyvPto0uTnCZaQ0QB6qFOBS51NJ/77hG/VYmIlbJylJ3R860SAl y8H8VYPAGUdWQzN1i7fOy1E1fcFjWS4xy1MrtV/8=
From: janaiyengar <>
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_5c00a6c6e9ed6_53c73f9c74ad45bc3086fe"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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 02:56:10 -0000

It's quite a burden on server to ensure single use of tokens, and SHOULD seems too strong. I'm not sure how you enforce it... while a single server might be able to ensure single use at that server, you need some serious infrastructure to enforce it across the fleet.

Is it adequate to suggest that servers MUST include a timestamp in the token, and SHOULD expire the token within a short period of time (a few seconds)?

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