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

Jana Iyengar <notifications@github.com> Thu, 18 June 2020 22: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 5724F3A040F for <quic-issues@ietfa.amsl.com>; Thu, 18 Jun 2020 15:21:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.694
X-Spam-Level:
X-Spam-Status: No, score=-1.694 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_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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 UxBfk_o_JG9u for <quic-issues@ietfa.amsl.com>; Thu, 18 Jun 2020 15:21:45 -0700 (PDT)
Received: from out-15.smtp.github.com (out-15.smtp.github.com [192.30.254.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04CF33A1030 for <quic-issues@ietf.org>; Thu, 18 Jun 2020 15:21:44 -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 84D5526184A for <quic-issues@ietf.org>; Thu, 18 Jun 2020 15:21:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1592518904; bh=8RIMDaXHUumWrNd0qbW0xuumKJ1vua8gY+QAW5e4Png=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=DDH1BOBjMGGn598XWppqJYKAwIa6QbioSY5Iqd8qupHT4tHsgTrRiUA8aX/qT2aWB gez8UY3Wus7FGWObmd8xWlBTTTmei0rZgyJxQniF1w/JrWSmfiesxIc3yVN5r8a9Eu 3BYoDaMoIEqCIYLnAEbcPYarpRgdue/55b4xyspE=
Date: Thu, 18 Jun 2020 15:21:44 -0700
From: Jana Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4JYPDZ74RVGQDBTWV467E7REVBNHHCL4HSQM@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/433684136@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_5eebe8f83f589_5bbf3fbc434cd968210163"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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/tumyg3ti9pTziGRAQCqPhTYxyEU>
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: Thu, 18 Jun 2020 22:21:46 -0000

@janaiyengar commented on this pull request.



> @@ -1749,12 +1749,13 @@ 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.
 
-It is OPTIONAL for a server to be able to recover the previously sent values of
-the max_idle_timout, max_udp_payload_size, and disable_active_migration
-parameters. Lowering the values of these parameters while also accepting 0-RTT
-data could degrade the performance of the connection. Specifically, lowering the
-max_udp_payload_size could result in dropped packets leading to worse
-performance compared to rejecting 0-RTT data outright.
+A server MAY choose to store and recover the previously sent values of the

```suggestion
A server MAY store and recover the previously sent values of the
```

> +max_idle_timout, max_udp_payload_size, and disable_active_migration parameters
+and reject 0-RTT if it selects smaller values. Lowering the values of these

This new phrase "reject 0-RTT if it selects smaller values" is confusing. What are you trying to convey?

-- 
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#pullrequestreview-433684136