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

ianswett <> Thu, 24 October 2019 01:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6194912011E for <>; Wed, 23 Oct 2019 18:46:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.596
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ja0K_LZ7rQUR for <>; Wed, 23 Oct 2019 18:45:59 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B90EA1200E7 for <>; Wed, 23 Oct 2019 18:45:59 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 214756A000A for <>; Wed, 23 Oct 2019 18:45:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1571881558; bh=h4tRzRtoWU3Nl7FOQoNsj66zrIfKJMOYb9VUIZTHysw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=e8S88kE/bYqTJ57pqXhL91LhBzBoDETvekEfHVLPjXcYCCr34juLPx5zFG4ThP8Ud rC4WcgomHH3PX+YuRxxlpPfqblfcaqKHOP1zzXUU5oqGLMpGSRp63wwdELJYAXQZ09 KD7cH12QvjwPoBdGV8EZ76+N5/x4+3SQ6P0pvFjE=
Date: Wed, 23 Oct 2019 18:45:58 -0700
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3138/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
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_5db1025611b01_30c43ff8078cd96441167a"; 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
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 24 Oct 2019 01:46:01 -0000

ianswett 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

Your implementation sound similar to ours.  But in both cases, it seems like the application doesn't care of 0-RTT succeeds or fails.  It only cares to know when 1-RTT keys are available.  But the existing text indicates the application needs to know about 0-RTT success/failure.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: