Re: [quicwg/base-drafts] Mention every Transport Parameter in section on values for 0-RTT (#3756)

Nick Harper <notifications@github.com> Mon, 15 June 2020 21:21 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 D91F33A1173 for <quic-issues@ietfa.amsl.com>; Mon, 15 Jun 2020 14:21:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.483
X-Spam-Level:
X-Spam-Status: No, score=-1.483 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, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, 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 GIY68ruMIqUJ for <quic-issues@ietfa.amsl.com>; Mon, 15 Jun 2020 14:21:33 -0700 (PDT)
Received: from out-17.smtp.github.com (out-17.smtp.github.com [192.30.252.200]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A7213A1171 for <quic-issues@ietf.org>; Mon, 15 Jun 2020 14:21:33 -0700 (PDT)
Received: from github-lowworker-39b4a70.va3-iad.github.net (github-lowworker-39b4a70.va3-iad.github.net [10.48.16.66]) by smtp.github.com (Postfix) with ESMTP id 8DABB6E03AC for <quic-issues@ietf.org>; Mon, 15 Jun 2020 14:21:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1592256092; bh=qxqUw9FiY6WkgMdO6nyRotbf9MXqsAcm2J6Lzfetmeo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=d62397E77tWg3Hrlt33A2Fn/xMVNDqx0fSywXjw/VElvtjmk92qymVz1poest5WOA c+z4uszSeDLm6Yu9S/pDEhgPTbV+Z35u3Qqkw6BvT6M6993dNDnSn2UKrD7CblN+Jf er0Be/E2Q4pyVuB+C9UsmLNt/jH6/SeHtw6fb9+g=
Date: Mon, 15 Jun 2020 14:21:32 -0700
From: Nick Harper <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK73V3SKIR6EJAYW2MN46PDVZEVBNHHCL4HSQM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3756/review/431002501@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3756@github.com>
References: <quicwg/base-drafts/pull/3756@github.com>
Subject: Re: [quicwg/base-drafts] Mention every Transport Parameter in section on values for 0-RTT (#3756)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ee7e65c7ee45_3b983f9ba0ccd96069444"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nharper
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/eHVIWCiXfZMu0SBbPjvtrGlVaiw>
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: Mon, 15 Jun 2020 21:21:35 -0000

@nharper commented on this pull request.



> @@ -1749,6 +1749,16 @@ values for 0-RTT.  This includes initial_max_data and either
 initial_max_streams_bidi and initial_max_stream_data_bidi_remote, or
 initial_max_streams_uni and initial_max_stream_data_uni.
 
+When accepting 0-RTT data, a server may set values for the following parameters
+that are smaller than the values remembered by the client. Because the previous
+values set for these parameters do not affect what values can be set when
+accepting 0-RTT data, it is not necessary that the server be able to recover the
+values it previously sent.
+
+* max_idle_timeout
+* max_udp_payload_size

Something like that sounds reasonable. I'll work on wording to say something along those lines and "your implementation is not incorrect if it chooses not to remember those values, but there may be optimizations that could involve remembering them".

-- 
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/3756#discussion_r440454153