Re: [quicwg/base-drafts] Refine Discussion of 0-RTT Transport Parameters (#2467)

martinduke <> Wed, 20 March 2019 19:55 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3127D1311A4 for <>; Wed, 20 Mar 2019 12:55:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3
X-Spam-Status: No, score=-3 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_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 h17qjeZwGa-U for <>; Wed, 20 Mar 2019 12:55:05 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0C73D131167 for <>; Wed, 20 Mar 2019 12:55:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=HOcEIMyXbFAVav+dmuOzAjSlBno=; b=IeWz+Rihf+8k+ZEO OlsuHjg9v0+1zWkoUuS+k4PB9BetXP0cknjK++hlFi7dmJ75400rhuv8s517nnH0 pFmvgdOkSakHV97IwL9t7uP8AVOjmfzwiAKN/luyGiGGARaOLMcD5hFGDdALYdAH lgT0j2+TN3fKTPvSJrxUFe3wCvQ=
Received: by with SMTP id filter1704p1mdw1-4986-5C929A98-2 2019-03-20 19:55:04.0614348 +0000 UTC m=+434276.393380947
Received: from (unknown []) by (SG) with ESMTP id MlutrsYlS1qxoGDC_Knjzw for <>; Wed, 20 Mar 2019 19:55:04.021 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id 021422C0074 for <>; Wed, 20 Mar 2019 12:55:04 -0700 (PDT)
Date: Wed, 20 Mar 2019 19:55:04 +0000
From: martinduke <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2467/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Refine Discussion of 0-RTT Transport Parameters (#2467)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c929a984b2_64ba3f92faad45b811027d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinduke
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0xieqcBoWEAhOQGA7VWRXdlPVfHuhw60z8ZB sbIId4/IeQdJecNjW8chsxg5iIG3RfvbucfObhn96dhmHFaM0Zy2HtNa8PsQsY1zC7DYV+ceaOqOPx 4tt4MEAdA4syfQWXJQ4onA0WxxA87G+VeyxnWNTyQekhls5Q99/lQ6aST48pZchAeMp57edBvumwRU M=
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: Wed, 20 Mar 2019 19:55:07 -0000

martinduke commented on this pull request.

> -when accepting 0-RTT data.  A server uses the transport parameters in
-determining whether to accept 0-RTT data.
-A server MAY accept 0-RTT and subsequently provide different values for
-transport parameters for use in the new connection.  If 0-RTT data is accepted
-by the server, the server MUST NOT reduce any limits or alter any values that
-might be violated by the client with its 0-RTT data.  In particular, a server
-that accepts 0-RTT data MUST NOT set values for the following parameters
-({{transport-parameter-definitions}}) that are smaller
-than the remembered value of those parameters.
+The value of the server's previous original_connection_id, preferred_address,
+stateless_reset_token, and ack_delay_exponent MUST NOT be used when
+establishing a new connection; rather, the client should wait to observe the
+server's new values in the handshake.
+The client MAY store the server's original max_ack_delay and max_packet_size

OK, I'll make it a MUST

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