Re: [quicwg/base-drafts] RESET_STREAM should be allowed in 0-RTT packets (#2344)

Kazuho Oku <notifications@github.com> Tue, 22 January 2019 23:42 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 324701311A1 for <quic-issues@ietfa.amsl.com>; Tue, 22 Jan 2019 15:42:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.553
X-Spam-Level:
X-Spam-Status: No, score=-12.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, 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: 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 EZactEwEv25I for <quic-issues@ietfa.amsl.com>; Tue, 22 Jan 2019 15:42:03 -0800 (PST)
Received: from out-12.smtp.github.com (out-12.smtp.github.com [192.30.254.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19068129C6A for <quic-issues@ietf.org>; Tue, 22 Jan 2019 15:42:03 -0800 (PST)
Date: Tue, 22 Jan 2019 15:42:02 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1548200522; bh=oL08RLEyjRGAKx43JnJVyeaiEd/TQfFUrdG1tVCzxhY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=BqXnICDti1yrbPfFk51rNtUfT9qdTSuJhm/JEijngA/evWCIHQNIBceORJEuk80IK Qf7dPgJcyImLe/u2NEGrt4AmgClJQF26nyT3FG8tC0LYJIWaQiWPZ6Gh/5Oo7TYFP2 5gAvz49QW+yTxUYinzUTMAff9tEBT6CDPhV4YGP4=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abf63be48c6f46585289556ba9ce2ca63fc433d56592cf00000001185f6c4a92a169ce17e00219@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2344/456608801@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2344@github.com>
References: <quicwg/base-drafts/issues/2344@github.com>
Subject: Re: [quicwg/base-drafts] RESET_STREAM should be allowed in 0-RTT packets (#2344)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c47aa4a400d5_29de3fbd742d45bc110016"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/-wiZPP7AjevY_Fx1aHxAc9A_K4g>
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: Tue, 22 Jan 2019 23:42:05 -0000

@MikeBishop 
> Because the client here is an attacker. However, I'm not seeing as much threat related to this specific change -- this is something the client can do regardless (generating many connections and causing state to be allocated for each).

The difference between a DoS using 1-RTT packets and 0-RTT packets is that the latter requires far less CPU cost on the attacker-side. This is because an attacker can just retransmit the same packets from different source tuples, whereas in 1-RTT case, an attacker needs to do expensive crypto operations (especially DH) for each connection it establishes.

Therefore my preference goes to limiting the capability of 0-RTT.

I like #2360 (maybe more than the approach I described in 
https://github.com/quicwg/base-drafts/pull/2355#pullrequestreview-194800021), because it clearly limits what a client can do using 0-RTT _for streams_.

The remaining question is what we should do for non-stream-related frames.

I still think that it makes sense to disallow the use of any non-stream-related frame in 0-RTT packets, considering the fact that:
* the frames allowed by 0-RTT and 1-RTT packets are nevertheless going to be different (CRYPTO, ACK)
* in practice there's no reason to send non-stream-related frames in 0-RTT packets
* potential security issues related to replay

-- 
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/2344#issuecomment-456608801