IETF Logo Mail Archive

Re: [quicwg/base-drafts] Make EOED transmission optional in QUIC, please (#1518)

ianswett <notifications@github.com> Sun, 02 September 2018 20: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 3A297130DDC for <quic-issues@ietfa.amsl.com>; Sun, 2 Sep 2018 13:42:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 b6G-Qzl5IgqN for <quic-issues@ietfa.amsl.com>; Sun, 2 Sep 2018 13:42:29 -0700 (PDT)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83213130DD8 for <quic-issues@ietf.org>; Sun, 2 Sep 2018 13:42:29 -0700 (PDT)
Date: Sun, 02 Sep 2018 13:42:27 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1535920947; bh=Li+m+BZM4aPorV95RH04Y3GIaNzlmgAu/uuuZDQ4Zr4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Nipif3IZNmAaY7UEMDsiizLM3ny5dEHFkcNe52bDyvtPskiYg7WMStN5elFbTwB8N G7X1sICLHAy4q1PZmorf8LQUY+nlr1VpFMg9PzSXdYpHeItOZbsZwVNCXKykuuMxu1 dzh33EWWAYxTTlNOQ7jrkyO+9Pfi8OJ54jCbLFlw=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab88a7f7451773f494ce528d649599b4853bbb745d92cf0000000117a40d3392a169ce1427404b@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1518/417958405@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1518@github.com>
References: <quicwg/base-drafts/issues/1518@github.com>
Subject: Re: [quicwg/base-drafts] Make EOED transmission optional in QUIC, please (#1518)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b8c4b339639a_50e63fdae98d45c41227053"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/hogO2vH5_V06bAH4kqwMF0PQHQk>
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: Sun, 02 Sep 2018 20:42:31 -0000

@ekr: I don't think "EOED tells you that you will not receive messages with 0-RTT keys but with greater PNs." is providing much, since if EOED is lost, the receiver will continue to process 0RTT packets with higher packet numbers.

Also, you have to continue processing these 0RTT packets long after EOED has been initially received, because the sender of EOED may not know EOED has been received.

I'd argue in QUIC EOED is actually telling you very little, and I tend to think it's inclusion is more harmful than helpful.  It requires keeping 0RTT keys around and continue processing them for longer.  Without EOED, you can stop processing 0RTT packets once a single packet is received with 1RTT encryption, which seems like a much stronger signal.

-- 
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/1518#issuecomment-417958405

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