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

David Schinazi <notifications@github.com> Tue, 16 June 2020 16:52 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 2CE103A040F for <quic-issues@ietfa.amsl.com>; Tue, 16 Jun 2020 09:52:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.482
X-Spam-Level:
X-Spam-Status: No, score=-1.482 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_DNSWL_BLOCKED=0.001, 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 Hau7JMcNDYcJ for <quic-issues@ietfa.amsl.com>; Tue, 16 Jun 2020 09:52:35 -0700 (PDT)
Received: from out-28.smtp.github.com (out-28.smtp.github.com [192.30.252.211]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8AD33A03FF for <quic-issues@ietf.org>; Tue, 16 Jun 2020 09:52:34 -0700 (PDT)
Received: from github-lowworker-b19c547.va3-iad.github.net (github-lowworker-b19c547.va3-iad.github.net [10.48.17.66]) by smtp.github.com (Postfix) with ESMTP id 036178C003E for <quic-issues@ietf.org>; Tue, 16 Jun 2020 09:52:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1592326354; bh=95qpxRuckkpeBxqIGoH6VysN72krCpAZQcdOftOmTKw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=SPy3WcZCi3WzPU8W2Tw3U6G9e+rhB3p+/KxQSrMfsGEJfA6afWuuYEdOOhckPJA3N mz9KghkeOc2682EIdiiMtN0JBxQPGwtVOTdSz39fONSd5eInX0uDu2sttadgtWSq+Q KVlaKijjSiz21JbBnq1Emo7gBaSs+lv1vUnI8vsk=
Date: Tue, 16 Jun 2020 09:52:33 -0700
From: David Schinazi <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5ZKA5GT52UOZRG5IN46TM5DEVBNHHCL4HSQM@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/431706163@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_5ee8f8d1e6c99_3c723ff65bacd9605087a"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: DavidSchinazi
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/JHWhod1YOzrAV2iYjbD0EmRa96g>
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: Tue, 16 Jun 2020 16:52:36 -0000

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

Ah thanks @martinthomson that makes sense! Based on that I agree that mentioning this could help.

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