IETF Logo Mail Archive

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

Jana Iyengar <notifications@github.com> Thu, 30 July 2020 12:24 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 69BE13A0E11 for <quic-issues@ietfa.amsl.com>; Thu, 30 Jul 2020 05:24:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.502
X-Spam-Level:
X-Spam-Status: No, score=-1.502 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_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 M0_V9NMAd0oP for <quic-issues@ietfa.amsl.com>; Thu, 30 Jul 2020 05:24:31 -0700 (PDT)
Received: from out-9.smtp.github.com (out-9.smtp.github.com [192.30.254.192]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A90D3A0A90 for <quic-issues@ietf.org>; Thu, 30 Jul 2020 05:24:31 -0700 (PDT)
Received: from github-lowworker-9bcb4a1.ac4-iad.github.net (github-lowworker-9bcb4a1.ac4-iad.github.net [10.52.25.84]) by smtp.github.com (Postfix) with ESMTP id B07ED580D8D for <quic-issues@ietf.org>; Thu, 30 Jul 2020 05:24:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1596111870; bh=Xxn9fPIFTiqqdJvwozuscyvWXMmrBy27DvRS5d0SoaI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=g9PjQ2/nLZQijta/rb/p7/8uKFwjt9Ro6rcXkZMBCSiSTgLHLOuyHVeWPPXp1HtCj d70FZWIcKgdYdkgE2pMkKxVWtMXIf83WoPissXUuZhE4EWMdb4Ci6sGizVkc6Et3Pb N2327xnQ6xjXMjrRb1+ZL+QUxC2hUKUpyeem8SqI=
Date: Thu, 30 Jul 2020 05:24:30 -0700
From: Jana Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYUTIK3P64N6NBJZAV5F2OP5EVBNHHCPUKUAM@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/458348368@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_5f22bbfe6b8e1_71b816f8875f1"; 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/0rfIbqXLb3a9zFlWM3TfYeYrlEA>
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 12:24:34 -0000

@janaiyengar commented on this pull request.



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

I'd like to make some editorial suggestions to martin's proposal, but I like that text.

-- 
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#discussion_r462957734

v2.37.1 | Report a Bug | By Email | System Status