Re: [quicwg/base-drafts] Transport parameter registry is too constraining for innovation (#3020)

Kazuho Oku <> Tue, 24 September 2019 21:05 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B072C1200DB for <>; Tue, 24 Sep 2019 14:05:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Status: No, score=-6.382 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, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vpT9mI7qI7Hg for <>; Tue, 24 Sep 2019 14:05:16 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1FE3D120071 for <>; Tue, 24 Sep 2019 14:05:16 -0700 (PDT)
Date: Tue, 24 Sep 2019 14:05:15 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1569359115; bh=YDTMs/l3emdxNqPVjz2dZhV1N2tFzTbbgnHta70t+Dk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0QQfLmDcOwkooQYM5H38+xXipy3StbOiK4usAZXKser5FN0CpI8V/pa7ZX+C3XB03 v0nd8ut5yzJ8KXva2V+m7BPJxMHFy5VndYHD/5XFfgUVfllJc2qTPo1DoxMpM9HIJ7 FIgsEPjxMUnYvGa+6BMUABFg8YnswL6bvmHrxtYY=
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3020/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Transport parameter registry is too constraining for innovation (#3020)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d8a850b6a95_10813fcb070cd96c128745"; 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
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 24 Sep 2019 21:05:18 -0000

I'd be opposed to changing the transport parameter lengths to varints, as that means departure from the TLS notation that we use for defining TPs. It's very different from changing the IDs to varints, which is just changing the type of a particular variable.

IIRC, we discussed if we should switch to a different notation, and decided to go with the TLS-based design. At least I have built (or maintained) code based on that.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: