IETF Logo Mail Archive

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

Christian Huitema <notifications@github.com> Mon, 03 September 2018 01:48 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 9F27D130E0A for <quic-issues@ietfa.amsl.com>; Sun, 2 Sep 2018 18:48:56 -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 87pZmW2DFACe for <quic-issues@ietfa.amsl.com>; Sun, 2 Sep 2018 18:48:54 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC140128CB7 for <quic-issues@ietf.org>; Sun, 2 Sep 2018 18:48:54 -0700 (PDT)
Date: Sun, 02 Sep 2018 18:48:53 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1535939333; bh=89Js3xuFsnv5vfTTCGewMZ98Q8UiyNFtlmRN1jpN3t8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=IO/AeYvYDPV2yGYy8BMfDu8TR7pdIapM0wfXrjrXpVCILFzZidEFj5CWLPXDLW4hR sAXILJhu9dpTWqhJQK1cWylpHb0hU9C0zYafN4PkSINMPDDE7hCIlEBnD1wUu1WeIN DVB+CZg0wtI9IWjWUJHrVKWcfOFcykW+b5R+jdGo=
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab020b6fab8beb287b967675a57bc89432a14bd24c92cf0000000117a4550592a169ce1427404b@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/417979035@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_5b8c9305c1550_1ea03fd2550d45b44500ef"; 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
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/O_2g2ut6z_w-2KT6CqOztNW5CJA>
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: Mon, 03 Sep 2018 01:48:57 -0000

There is no explicit signal, but it is very much assumed that if the TLS stack provides the transport with the write key for epoch 3, then application data will be sent that way. I read again the QUIC/TLS draft, and I could not find a statement saying that application data MUST NOT be sent as 0-RTT if the 1-RTT key is available. But in fact, that's the whole point of this thread. If it were not for the transmission of EOED over 0-RTT, the transport could simply just discard the 0-RTT write keys when the 1-RTT write keys become available. I would very much like to be able to do that.

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

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