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

Christian Huitema <notifications@github.com> Mon, 25 September 2017 08:16 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 BAEDC1321DF for <quic-issues@ietfa.amsl.com>; Mon, 25 Sep 2017 01:16:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.616
X-Spam-Level:
X-Spam-Status: No, score=-0.616 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_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 Za5iEUVDzajU for <quic-issues@ietfa.amsl.com>; Mon, 25 Sep 2017 01:16:45 -0700 (PDT)
Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 4F58013304A for <quic-issues@ietf.org>; Mon, 25 Sep 2017 01:16:45 -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=rwU1DKindvSmkX4rGvHKqSPUgYo=; b=Zvi+PDB9cS48gIoK 6gzR1VtA3MlqZjJeyOX0nXQlMj3SeGVXxnutEy8CPIzhHjv4QGU9wfc9XtX28Rm0 gxHYrIIPVL4RNxqRusxMvwPM16RpbdRPnJ0fvpWdIDF8UHA//SPRuwrxcZFvTxfn QIiliRkVTec4FSAlZ32Wb/+6vyE=
Received: by filter0617p1mdw1.sendgrid.net with SMTP id filter0617p1mdw1-5628-59C8BB6C-E 2017-09-25 08:16:44.229138559 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0001p1iad2.sendgrid.net (SG) with ESMTP id hvA2JTb2SSOvav00t1XKEg for <quic-issues@ietf.org>; Mon, 25 Sep 2017 08:16:44.197 +0000 (UTC)
Date: Mon, 25 Sep 2017 08:16:44 +0000
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab856d9fdd7bfa47a13a30124ba347b3a1702d263d92cf0000000115e07d6c92a169ce0f7388f0@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/331809243@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_59c8bb6cbe57_24cb33fbcd2d1cf80690fc"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: huitema
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3m/U+LT42XofzgkncQ2eheRmcTTvfcMEKf39 n8zUactuCiQBGUpydF3bTS8ux+B6z5bWuQxiAiALANnZZ2RzBJsi7XGdMWwCYFIjq5hc+9WA1jGovH NDIbaK8+PQvsJvSjfqKbYXnYNA6lgFOHrzM/rlE7zoZdn3I3RdAA0IKlXVtN2ND3umXDs9m0X3PFpz 0=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/LhO2E1hiRlFoTj8jdpz_j1vivn0>
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: Mon, 25 Sep 2017 08:16:47 -0000

There are two different issues. One is a problem of efficiency, carrying Finished (or a copy) in the same UDP packet as the first application data frames. The other is an issue of DOS resilience, knowing when to start just ignoring any non encrypted packets.

We could probably solve the efficiency issue by creating a new packet type, "clear text followed by encrypted data". I am also interested with the issue of closing the DOS opening.

-- 
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-331809243