Re: [quicwg/base-drafts] Why are stateless reset tokens 16 bytes long? (#2018)
Martin Thomson <notifications@github.com> Mon, 26 November 2018 04:14 UTC
Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E53EF130EFE for <quic-issues@ietfa.amsl.com>; Sun, 25 Nov 2018 20:14:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.367
X-Spam-Level:
X-Spam-Status: No, score=-9.367 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, HTML_OBFUSCATE_10_20=0.093, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vjQ6DEMvOQq2 for <quic-issues@ietfa.amsl.com>; Sun, 25 Nov 2018 20:14:26 -0800 (PST)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 521E3130EF9 for <quic-issues@ietf.org>; Sun, 25 Nov 2018 20:14:26 -0800 (PST)
Date: Sun, 25 Nov 2018 20:14:25 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1543205665; bh=mBICQ7FYDN0lJIFzlebFPzNP785uxewIQ7SxPQQLvrs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Aac4xXkJnmhW/8gSv4yqB+TEMVl3ZPVA/OMfTDapOY01PsOeZLHKHZVTaBWSUcniX 8QGdY/VYM42m1ZeHK/rntIWL4bw1pxzhJrmfisHJv+n7zhG5LV1DsWHr8R+2N8a6ZJ WFcNxWhCidUp/wo3fn8iAFgHXE8Vqk+63rvfe36A=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abc38cc658a4cbd6981a0652b008060abb1cb3e71092cf000000011813352192a169ce16c2396c@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2018/441514212@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2018@github.com>
References: <quicwg/base-drafts/issues/2018@github.com>
Subject: Re: [quicwg/base-drafts] Why are stateless reset tokens 16 bytes long? (#2018)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bfb73214c82d_76583fcb81ad45bc34884b"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/5_lzgtfrCMRsKRytJgioM9eFCa8>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Nov 2018 04:14:28 -0000
It is intentional. Even if 2<sup>64</sup> was insufficient, I don't think that it's that bad. Birthday bounds only come into play when you want to kill one connection from many. That is, you are willing to send 2<sup>64</sup> packets and there are 2<sup>64</sup> connection IDs live. Standard DoS mitigation techniques probably start to apply before the birthday bound is threatened. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/quicwg/base-drafts/issues/2018#issuecomment-441514212
- [quicwg/base-drafts] Why are stateless reset toke… Marten Seemann
- Re: [quicwg/base-drafts] Why are stateless reset … MikkelFJ
- Re: [quicwg/base-drafts] Why are stateless reset … Kazuho Oku
- Re: [quicwg/base-drafts] Why are stateless reset … Marten Seemann
- Re: [quicwg/base-drafts] Why are stateless reset … Kazuho Oku
- Re: [quicwg/base-drafts] Why are stateless reset … Martin Thomson
- Re: [quicwg/base-drafts] Why are stateless reset … ekr
- Re: [quicwg/base-drafts] Why are stateless reset … Martin Thomson
- Re: [quicwg/base-drafts] Why are stateless reset … Kazuho Oku
- Re: [quicwg/base-drafts] Why are stateless reset … Martin Thomson
- Re: [quicwg/base-drafts] Why are stateless reset … Kazuho Oku
- Re: [quicwg/base-drafts] Why are stateless reset … ekr
- Re: [quicwg/base-drafts] Why are stateless reset … Dmitri Tikhonov
- Re: [quicwg/base-drafts] Why are stateless reset … Martin Thomson
- Re: [quicwg/base-drafts] Why are stateless reset … Martin Thomson