Re: [quicwg/base-drafts] Can Finished be sent as 1-RTT data? (#785)
Igor Lubashev <notifications@github.com> Tue, 26 September 2017 01:06 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 50073132705 for <quic-issues@ietfa.amsl.com>; Mon, 25 Sep 2017 18:06:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.298
X-Spam-Level:
X-Spam-Status: No, score=-9.298 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, 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 6WFaI9F4wVrC for <quic-issues@ietfa.amsl.com>; Mon, 25 Sep 2017 18:06:57 -0700 (PDT)
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext2.iad.github.net [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F00EE1321A4 for <quic-issues@ietf.org>; Mon, 25 Sep 2017 18:06:56 -0700 (PDT)
Date: Mon, 25 Sep 2017 18:06:56 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1506388016; bh=WGivUNT6rwUyNvYna3niVyf1TKl0qu2cbOOZbqSJ1/E=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=iq/ljg0Ec8FBXAmbAL1nrRA9eGDAC6MFi16Agzy6DriCB3oF7ZrBxWwp81fFkvhHj Y3XXCsQMDAP5QL/OnBVzHOgCnVw5bAVNbYjFIdH8XPdB3BBA76rjkyP6vBYM92EXB1 u7G09rXKd3lphlriD+fp0z22jCaDWiER2CN7keuQ=
From: Igor Lubashev <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab79200658292cc038ee761b9f4bc83e2f7f9f35e492cf0000000115e16a3092a169ce0f7388f0@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/332056187@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_59c9a830153d9_417a3f814fc46f84118c0"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: igorlord
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/vilyBfwhMsZE45QCIeFRwBMhg8Q>
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: Tue, 26 Sep 2017 01:06:58 -0000
@martinthomson, I think I get this concern. However, in the 3rd comment, @huitema suggests a scenario of a DoS that would not be a DoS, if the server were to ignore all Clear Text packets after receiving Client's valid Finished message. Until the server receives Client's valid Finished message, the usual DoS concerns regarding packet injection apply. There may be other reasons to make client's Finished encrypted after the receipt of server's Finished, but this DoS scenario is probably not it. -- 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-332056187
- Re: [quicwg/base-drafts] Can Finished be sent as … Martin Thomson
- Re: [quicwg/base-drafts] Can Finished be sent as … Christian Huitema
- Re: [quicwg/base-drafts] Can Finished be sent as … Christian Huitema
- [quicwg/base-drafts] Can Finished be sent as 1-RT… Christian Huitema
- Re: [quicwg/base-drafts] Can Finished be sent as … ekr
- Re: [quicwg/base-drafts] Can Finished be sent as … ekr
- Re: [quicwg/base-drafts] Can Finished be sent as … Martin Thomson
- Re: [quicwg/base-drafts] Can Finished be sent as … ekr
- Re: [quicwg/base-drafts] Can Finished be sent as … Martin Thomson
- Re: [quicwg/base-drafts] Can Finished be sent as … Christian Huitema
- Re: [quicwg/base-drafts] Can Finished be sent as … Martin Thomson
- Re: [quicwg/base-drafts] Can Finished be sent as … Igor Lubashev
- Re: [quicwg/base-drafts] Can Finished be sent as … Martin Thomson
- Re: [quicwg/base-drafts] Can Finished be sent as … Igor Lubashev
- Re: [quicwg/base-drafts] Can Finished be sent as … Martin Thomson
- Re: [quicwg/base-drafts] Can Finished be sent as … Martin Thomson
- Re: [quicwg/base-drafts] Can Finished be sent as … Martin Thomson
- Re: [quicwg/base-drafts] Can Finished be sent as … Martin Thomson