Re: [quicwg/base-drafts] QUIC/ALPN Version Specific Transport Parameters (#3965)
Kazuho Oku <notifications@github.com> Tue, 28 July 2020 16:10 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 E59163A0E64 for <quic-issues@ietfa.amsl.com>; Tue, 28 Jul 2020 09:10:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.574
X-Spam-Level:
X-Spam-Status: No, score=-1.574 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_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H3=-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 1jpPpIa_Hgc5 for <quic-issues@ietfa.amsl.com>; Tue, 28 Jul 2020 09:10:56 -0700 (PDT)
Received: from out-10.smtp.github.com (out-10.smtp.github.com [192.30.254.193]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DD4A3A0E53 for <quic-issues@ietf.org>; Tue, 28 Jul 2020 09:10:56 -0700 (PDT)
Received: from github-lowworker-9d2806a.ash1-iad.github.net (github-lowworker-9d2806a.ash1-iad.github.net [10.56.102.50]) by smtp.github.com (Postfix) with ESMTP id A7DAD580EB9 for <quic-issues@ietf.org>; Tue, 28 Jul 2020 09:10:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1595952655; bh=uREjPXJDTgdAF9ZIzdFOOVXq5fO5HyqnVrZD1U6v/iY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=e9CbTnWgkxadHiYHK0qaCkYTBdtbNEpfFGECfHnAmhNYIt4YbVXmAA/QSMbIB1OqE B48NWowIL0MTtXscrvzzaNBHjIIROA6eAVnw755yyzr6OieW3Z9fyMDJO9uXLdpSG1 htzu87cYesG/NWQYQLg3sbhgVnIciAvTVRMhqN00=
Date: Tue, 28 Jul 2020 09:10:55 -0700
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYYTCB5HLPZP5PTTCV5FQXQ7EVBNHHCPQ7KSI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3965/665132085@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3965@github.com>
References: <quicwg/base-drafts/issues/3965@github.com>
Subject: Re: [quicwg/base-drafts] QUIC/ALPN Version Specific Transport Parameters (#3965)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f204e0f815a6_749a16f81365d9"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/W8Bv6D0Ol89_OYsyA4Hc2U8kdmE>
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, 28 Jul 2020 16:10:58 -0000
I agree to what @DavidSchinazi and @mjoras say. In addition to what they have stated, I'd point out that endpoints can loosen the settings by sending frames after the handshake is complete. Most transport parameters are merely used to communicate the initial values. And for other parameters that communicate the final value (e.g., max_ack_delay), we can add frames for changing the behavior as we find out the needs. -- 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/issues/3965#issuecomment-665132085
- [quicwg/base-drafts] QUIC/ALPN Version Specific T… Nick Banks
- Re: [quicwg/base-drafts] QUIC/ALPN Version Specif… David Schinazi
- Re: [quicwg/base-drafts] QUIC/ALPN Version Specif… mjoras
- Re: [quicwg/base-drafts] QUIC/ALPN Version Specif… Nick Banks
- Re: [quicwg/base-drafts] QUIC/ALPN Version Specif… Nick Banks
- Re: [quicwg/base-drafts] QUIC/ALPN Version Specif… Nick Banks
- Re: [quicwg/base-drafts] QUIC/ALPN Version Specif… David Schinazi
- Re: [quicwg/base-drafts] QUIC/ALPN Version Specif… Kazuho Oku
- Re: [quicwg/base-drafts] QUIC/ALPN Version Specif… Nick Banks
- Re: [quicwg/base-drafts] QUIC/ALPN Version Specif… David Schinazi
- Re: [quicwg/base-drafts] QUIC/ALPN Version Specif… ianswett
- Re: [quicwg/base-drafts] QUIC/ALPN Version Specif… Lucas Pardue
- Re: [quicwg/base-drafts] QUIC/ALPN Version Specif… Martin Thomson
- Re: [quicwg/base-drafts] QUIC/ALPN Version Specif… Nick Banks
- Re: [quicwg/base-drafts] QUIC/ALPN Version Specif… Lars Eggert
- Re: [quicwg/base-drafts] QUIC/ALPN Version Specif… Jana Iyengar