Re: [quicwg/base-drafts] Transport Parameters are not APLN Specific (#3973)

Jana Iyengar <notifications@github.com> Thu, 30 July 2020 20:58 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 63B573A0CB9 for <quic-issues@ietfa.amsl.com>; Thu, 30 Jul 2020 13:58:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.101
X-Spam-Level:
X-Spam-Status: No, score=-3.101 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_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 KHLHK6kedL6j for <quic-issues@ietfa.amsl.com>; Thu, 30 Jul 2020 13:58:57 -0700 (PDT)
Received: from out-22.smtp.github.com (out-22.smtp.github.com [192.30.252.205]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1A913A0CB8 for <quic-issues@ietf.org>; Thu, 30 Jul 2020 13:58:57 -0700 (PDT)
Received: from github-lowworker-d93c4b6.va3-iad.github.net (github-lowworker-d93c4b6.va3-iad.github.net [10.48.17.47]) by smtp.github.com (Postfix) with ESMTP id ED85A560064 for <quic-issues@ietf.org>; Thu, 30 Jul 2020 13:58:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1596142736; bh=X6vBz5AuK/kWHiMvih8QLZjpYPHTL3AGD1KhRGRFaxw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=lWumC4Ulzec3MvA/fvhtwH1h0IApUxjEJUH59Gb1kwt8MqMKFgzwukec4aH+V+v53 QVUdQvEiFthQeh8mUxqc5bHsHlCa9Gcd7ssVyHhrG7Jwpo+Yvv0sPVKjEaV9FWB8Kl Jizg3tlj7H+zXAFY54M1LJ84Rm0ATM7s6IB+udWw=
Date: Thu, 30 Jul 2020 13:58:56 -0700
From: Jana Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6PGR77DZFVPJHXGD55F4KZBEVBNHHCPUKUAM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3973/review/458751580@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3973@github.com>
References: <quicwg/base-drafts/pull/3973@github.com>
Subject: Re: [quicwg/base-drafts] Transport Parameters are not APLN Specific (#3973)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f233490de89b_547416f83765b"; 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/eU2yBcFso5oCC4V19VOQqZzNqvk>
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, 30 Jul 2020 20:58:59 -0000

@janaiyengar commented on this pull request.

Editorial suggestions

> +Protocol negotiation with Application Layer Protocol Negotiation (ALPN; see
+{{?ALPN=RFC7301}}) allows clients to offer multiple application protocols with
+connection attempts. The single set of transport parameters offered by a client
+apply to all application protocols that the client offers. Application protocols
+can make recommendations about the values for transport parameters, such as
+suggesting minimum values for stream or flow control limits. Application
+protocols that place hard constraints on transport parameters could make it
+impossible for clients to attempt a connection that includes other application
+protocols with different constraints.

```suggestion
Application Layer Protocol Negotiation (ALPN; see {{?ALPN=RFC7301}}) allows
clients to offer multiple application protocols during connection
establishment. The transport parameters that a client includes during the
handshake apply to all application protocols that the client offers. Application
protocols can recommend values for transport parameters, such as the initial
flow control limits. However, application protocols that require values for
transport parameters will make	it impossible for a client to offer multiple
application protocols with conflicting requirements.
```

-- 
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/3973#pullrequestreview-458751580