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

martinduke <notifications@github.com> Fri, 15 February 2019 00:32 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 2F4B9128B36 for <quic-issues@ietfa.amsl.com>; Thu, 14 Feb 2019 16:32:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level:
X-Spam-Status: No, score=-8 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_HI=-5, 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 tWZOkMMmPW54 for <quic-issues@ietfa.amsl.com>; Thu, 14 Feb 2019 16:32:20 -0800 (PST)
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 7B4DD130DCB for <quic-issues@ietf.org>; Thu, 14 Feb 2019 16:32:16 -0800 (PST)
Date: Thu, 14 Feb 2019 16:32:15 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1550190735; bh=VQvRSZglrbIa6ENWx2KY4Szsyd345gfTbmEpsFjdHCc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gW7h28d6ssBPEfE1lBQCVNFxUWZNtmOE59Nwdc5sxklYslmgqshJ2y5ye+n85cB8S VGg3Y0ynflnci/k7w+GAKf7Uzwqf89VP9t7fBwwwDx/DBdCdbKC8ryVbWQtH8pfxrS Rl4Jm6mU04abD0o+NFh5mtU/42Mlw1VwltNdScWs=
From: martinduke <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab5b72f201126f10b57ee543ad9fbee884a350ab5c92cf00000001187dca8f92a169ce187830aa@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2467/review/204037715@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2467@github.com>
References: <quicwg/base-drafts/pull/2467@github.com>
Subject: Re: [quicwg/base-drafts] Refine Discussion of 0-RTT Transport Parameters (#2467)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c66088f8474b_7b4c3ffd05ed45bc52845e"; 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-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/_H5t7hB8ir_taWL-Bw96Uu5usdo>
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: Fri, 15 Feb 2019 00:32:22 -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

The client may find it useful to retain this information to set its 0-RTT loss timer properly, rather than having to wait for the handshake and reset it properly. Am I not thinking clearly on how this is done?

-- 
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/2467#discussion_r257067314