IETF Logo Mail Archive

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

ianswett <notifications@github.com> Thu, 24 October 2019 01:26 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 68681120114 for <quic-issues@ietfa.amsl.com>; Wed, 23 Oct 2019 18:26:47 -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 7bwioT1a5r3V for <quic-issues@ietfa.amsl.com>; Wed, 23 Oct 2019 18:26:46 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B63E12010D for <quic-issues@ietf.org>; Wed, 23 Oct 2019 18:26:46 -0700 (PDT)
Received: from github-lowworker-c53a806.ac4-iad.github.net (github-lowworker-c53a806.ac4-iad.github.net [10.52.23.45]) by smtp.github.com (Postfix) with ESMTP id 2A615C60635 for <quic-issues@ietf.org>; Wed, 23 Oct 2019 18:26:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1571880405; bh=AHHt6Xt3ki9omALWKppeN9H8cp+0pQ7kSnWBAy1auRs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=RGfBgZmIN+smAjahGnKjavJQc5WLn48mDAX9zyczt1dtPdXm3HB3Ur1nBHJEfxWIR N27zjh7gtODBeb3mCTdEI2w3DhpdReB31Byx2JM8za6eAD/Pa/lX8nkVtjpWOK4WTG Hz7GW1xW//zJa3RnNh8TVMWfregBaFHdyQpml5F8=
Date: Wed, 23 Oct 2019 18:26:45 -0700
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7JSKHGNXY3W6USYGF3XY7GLEVBNHHB47Q2W4@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/306274593@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_5db0fdd51aeeb_616b3f9d70ccd95c246863"; 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/f1FwEL6G9kQPklAHuPsR9Wrqpts>
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:26:47 -0000

ianswett commented on this pull request.

Some more comments

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

A client doesn't receive 0-RTT, so how would it reject it?

The way I think of it is:
"be informed when 0-RTT keys are available."
"be informed when 1-RTT keys are available."

I don't think the client application needs to know if 0-RTT is rejected or accepted, as long as the handshake succeeds?  And applications like HTTP/3 don't want to enable 0-RTT, but only send some data with 0-RTT keys.

-- 
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#pullrequestreview-306274593

v2.23.0 | Report a Bug | By Email