Re: [quicwg/base-drafts] Don't amplify 0-RTT (#1616)
ekr <notifications@github.com> Wed, 01 August 2018 02:43 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 B2144130F1F for <quic-issues@ietfa.amsl.com>; Tue, 31 Jul 2018 19:43:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.109
X-Spam-Level:
X-Spam-Status: No, score=-6.109 tagged_above=-999 required=5 tests=[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, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 uiWUkzhoy7ND for <quic-issues@ietfa.amsl.com>; Tue, 31 Jul 2018 19:43:29 -0700 (PDT)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02AA8130E23 for <quic-issues@ietf.org>; Tue, 31 Jul 2018 19:43:29 -0700 (PDT)
Date: Tue, 31 Jul 2018 19:43:28 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1533091408; bh=3bGX3yv94S5JV+O2TswJUzGpU2Gu9zUqNBcaZl0MxcY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=jpHtJhtjkkDBmI0Qmuiz5RHTfl5+eqeAHKhymmSvAYA9xHk3pWtRGWD5ctuh9mj2p d8xIMTnuAwQEQ937qXRkPVyskVVahqWuqwJAAOrJrCDKNiZZyf6aKPjLNi54UZeUvR 3DFVLItZ0pQQ5G014zZLxARrhzZpub406OUgBbj8=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab67a791c4266c0c58a76acf3949e5648678f5465792cf000000011778e05092a169ce14a01a2f@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1616/review/142211745@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1616@github.com>
References: <quicwg/base-drafts/pull/1616@github.com>
Subject: Re: [quicwg/base-drafts] Don't amplify 0-RTT (#1616)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b611e50d3b0_a483ff51d2d45b82371da"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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/3tRLgtJM01aXMhcxOI6LWprChlg>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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: Wed, 01 Aug 2018 02:43:31 -0000
ekr requested changes on this pull request. > @@ -1896,6 +1896,13 @@ dynamically calculate the expiration time. It is also unlikely that the client port number is the same on two different connections; validating the port is therefore unlikely to be successful. +Even when a token is valid, a server SHOULD limit the amount of data that it +sends toward a client in response to 0-RTT data. Spoofing of source addresses +and replays of 0-RTT handshake messages can cause tokens to appear to be valid +when they are not. No specific recommendation is made regarding the ratio of +data sent to received, though it is unlikely to be necessary to send more than +the initial congestion window. This text seems wrong. Tokens are either valid or they are not. What specific attack scenario are you concerned with? -- 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/pull/1616#pullrequestreview-142211745
- Re: [quicwg/base-drafts] Don't amplify 0-RTT (#16… ekr
- Re: [quicwg/base-drafts] Don't amplify 0-RTT (#16… Martin Thomson
- [quicwg/base-drafts] Don't amplify 0-RTT (#1616) Martin Thomson
- Re: [quicwg/base-drafts] Don't amplify 0-RTT (#16… ianswett
- Re: [quicwg/base-drafts] Don't amplify 0-RTT (#16… Martin Thomson
- Re: [quicwg/base-drafts] Don't amplify 0-RTT (#16… ianswett
- Re: [quicwg/base-drafts] Don't amplify 0-RTT (#16… Martin Thomson
- Re: [quicwg/base-drafts] Don't amplify 0-RTT (#16… ekr
- Re: [quicwg/base-drafts] Don't amplify 0-RTT (#16… Martin Thomson