Re: [quicwg/base-drafts] Applications need to disable or selectively reject 0-RTT (#3138)

Martin Thomson <notifications@github.com> Thu, 24 October 2019 01:34 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 D66F612011A for <quic-issues@ietfa.amsl.com>; Wed, 23 Oct 2019 18:34:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Level:
X-Spam-Status: No, score=-6.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 z6e4gM0BMw6f for <quic-issues@ietfa.amsl.com>; Wed, 23 Oct 2019 18:34:31 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [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 854DE12010D for <quic-issues@ietf.org>; Wed, 23 Oct 2019 18:34:31 -0700 (PDT)
Received: from github-lowworker-fb56993.ac4-iad.github.net (github-lowworker-fb56993.ac4-iad.github.net [10.52.19.31]) by smtp.github.com (Postfix) with ESMTP id DFB841C2E09 for <quic-issues@ietf.org>; Wed, 23 Oct 2019 18:34:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1571880870; bh=cqG2O2Wi6P25pbj8IkLZywHrpWhaiM597vrk0U30oEQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=SdiZl5yiuxM/fe8s9RxfJhdoJqNwlpXEb1lwfSV+pxNFMfUW5+AieYXcI2teRJfXA etonxPLje3dGKINeL4lT0EAaLsF48udjBp4F6ucvlXGCHoy3vFHFvTXVtFUiUOtyq0 cmm+JvNoDqKbC5gpcZ8hsuTbo1amjapxScrSsWWg=
Date: Wed, 23 Oct 2019 18:34:30 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK34GALGMHZ2DZQTXKV3XZADNEVBNHHB47Q2W4@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3138/review/306276639@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3138@github.com>
References: <quicwg/base-drafts/pull/3138@github.com>
Subject: Re: [quicwg/base-drafts] Applications need to disable or selectively reject 0-RTT (#3138)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5db0ffa6d0a4e_658e3feda5ccd9681166d0"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/tVR-dlgpmuWhNKWR8ahxzd3nvHw>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 24 Oct 2019 01:34:33 -0000

martinthomson commented on this pull request.



> @@ -1159,7 +1159,7 @@ the operations described in this section on a QUIC connection.
 When implementing the client role, applications need to be able to:
 
 - open a connection, which begins the exchange described in {{handshake}};
-- enable 0-RTT; and
+- disable or selectively reject 0-RTT; and

That was silly.  I think that "enable 0-RTT *when available*" suffices.  We don't need to go into detail about 0-RTT keys or any of that mess, that's an internal concern of the transport.

For our stack, we enable 0-RTT always (you can't turn it off), and rely on applications using the handshake state to determine whether what is being sent is 0-RTT (or 0.5-RTT) or not.  If there is no 0-RTT, then attempts to create streams will fail.

-- 
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/pull/3138#discussion_r338347580