IETF Logo Mail Archive

Re: [quicwg/base-drafts] Can Finished be sent as 1-RTT data? (#785)

ekr <notifications@github.com> Wed, 20 September 2017 20:09 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 AB583134303 for <quic-issues@ietfa.amsl.com>; Wed, 20 Sep 2017 13:09:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.02
X-Spam-Level:
X-Spam-Status: No, score=-2.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 bb9tAK1IZi4M for <quic-issues@ietfa.amsl.com>; Wed, 20 Sep 2017 13:08:59 -0700 (PDT)
Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B6DC132C32 for <quic-issues@ietf.org>; Wed, 20 Sep 2017 13:08:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=w7srsgJZRnpfJZix337sKRh7n+k=; b=Ah545C6ZJyFazrtg bs1lKZ/xbU3SZ9uMj9xmxWiCWG1WWfQ5RUAJ2s8oEKvdqtudjNPqQYBms4tCYM4T lcx9M6DhMxMPQFSlGm+0dAIbdwUFMrKlrAQJQo7/eeoUIZWdFjlEcEhfNLaDLdF6 hajhrm2BUA1jSCElm71/TueGdAQ=
Received: by filter0361p1las1.sendgrid.net with SMTP id filter0361p1las1-28411-59C2CAD9-A8 2017-09-20 20:08:57.94233314 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0007p1iad1.sendgrid.net (SG) with ESMTP id DEZl4DI_QaSxTRmXMv-ryw for <quic-issues@ietf.org>; Wed, 20 Sep 2017 20:08:57.863 +0000 (UTC)
Date: Wed, 20 Sep 2017 20:08:58 +0000
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abcc016c2ed9fbebecdec51d0ccf13600906b8955792cf0000000115da8cd992a169ce0f7388f0@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/785/330966063@github.com>
In-Reply-To: <quicwg/base-drafts/issues/785@github.com>
References: <quicwg/base-drafts/issues/785@github.com>
Subject: Re: [quicwg/base-drafts] Can Finished be sent as 1-RTT data? (#785)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59c2cad987c42_176a43fa3ebd84f7c99585"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak11lTpvLF2/anCZwQqu0UgeQLGXYoBO8zE4UV oD+ENnJu7Z7sGOSyerrSiAhM/Avi71bubNzlwgCQ+ZREtr6+zzLwGFt+yuddegx5voiarK9FZIa91J 3muzvyAgWLJo6FY2gXiV7VUWNLkTEgpyDD4Bq+cw5wXgSu/3cL/v3mBeUg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/hXA9w3hYuBnOtobQgEL7t8mEDNg>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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, 20 Sep 2017 20:09:01 -0000

"Sure. But the look at the transport. Client packet #3 is Client Clear Text. Client packet #4 is 1RTT. Then #5 is Client clear text, repeat. #6 is 1 RTT. #7 is a fake Client Clear Text. #7 is real 1 RTT Data, but gets ignore because of duplicate SN. Etc."

This just seems like another DoS injection attack, which is properly solved by having a connection ID authentication tag on the cleartext packets.

The draft text you cite is just wrong.


-- 
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/785#issuecomment-330966063

v2.39.1 | Report a Bug | By Email | System Status