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

Martin Thomson <notifications@github.com> Thu, 30 July 2020 02:20 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 C021F3A0BA3 for <quic-issues@ietfa.amsl.com>; Wed, 29 Jul 2020 19:20:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level:
X-Spam-Status: No, score=-3.099 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_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 7Dv5IjD-hOsv for <quic-issues@ietfa.amsl.com>; Wed, 29 Jul 2020 19:20:25 -0700 (PDT)
Received: from out-20.smtp.github.com (out-20.smtp.github.com [192.30.252.203]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CFFB3A0BA1 for <quic-issues@ietf.org>; Wed, 29 Jul 2020 19:20:24 -0700 (PDT)
Received: from github-lowworker-1dbcc59.ash1-iad.github.net (github-lowworker-1dbcc59.ash1-iad.github.net [10.56.105.54]) by smtp.github.com (Postfix) with ESMTP id 44C3DE1E7E for <quic-issues@ietf.org>; Wed, 29 Jul 2020 19:20:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1596075624; bh=x3kpLcKfXDdGyqXrzzGpoSd0+i4KBpm+OT6cOhpMMpc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=k3bthHTBrNRjtEgIfGN0eHnoofbipxCTZlFAm6iTWwwVYVyOJnJl6EIvEOFxxFRyJ nTWIrYO6T/To72E3vu1DToI8yfuYVXt1rttNP65T5S+/U60Fi9ljcC8rHmRaY5EBhA hGpCMZRb5Q/8QIe1cXCxlsvKwjyuu0fhCNEdC898=
Date: Wed, 29 Jul 2020 19:20:24 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK2O6TUJUAAG64KOL5F5FYHWREVBNHHCPUKUAM@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/458026730@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_5f222e6835015_196516f83228ec"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/de31iPFtBhzl4Rzn1rM_PUeFeUs>
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 02:20:28 -0000

@martinthomson commented on this pull request.

Thanks for putting this together.  I wasn't sure that I understood what you wanted before.

> @@ -1741,6 +1741,13 @@ parameters as a connection error of type TRANSPORT_PARAMETER_ERROR.
 Endpoints use transport parameters to authenticate the negotiation of
 connection IDs during the handshake; see {{cid-auth}}.
 
+When sent by the client, transport parameters are not specific to a particular
+ALPN being negotiated.  Therefore, a client cannot have application protocol
+specific values in the transport parameters.  Application protocols should take
+this into account when designing versioning schemes, and not place restrictions
+on the values in the transport parameters that might prevent protocol changes
+in future version of the application protocol.

There is a difference between requirements and recommendations.  We do recommend in HTTP/3 that a certain number of unidirectional stream be available, but it is [just a recommendation](https://quicwg.org/base-drafts/draft-ietf-quic-http.html#section-6.2-4).

I think that this could be clearer then:

> Protocol negotiation with Application Layer Protocol Negotiation (ALPN; see {{?ALPN=RFC7301}}) allows clients to offer multiple application protocols during connection establishing. 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.

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