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

Marten Seemann <> Sun, 13 October 2019 11:47 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 922AB12003E for <>; Sun, 13 Oct 2019 04:47:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Status: No, score=-6.596 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_28=1.404, 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 xoAvB7W2SPn6 for <>; Sun, 13 Oct 2019 04:47:53 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 28B5D120024 for <>; Sun, 13 Oct 2019 04:47:53 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 9F536261640 for <>; Sun, 13 Oct 2019 04:47:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1570967272; bh=7JBIMzPwKENXeGvflMHMqTOcBqir3wuCVrLKLExWj9I=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QAbJweWLQkfKjRhg1yOn/0HrZcoUAXIUjXgVy8PXirs8EyeeQ6uQ3df1EvsCY5aBL XCMjwaa/oixCjuEfaI4bLt29fgw+pRABf5rR/GtP9y93KbOniibkd2k8gHKosrc2MY f8TJmtW523X1eNV3io75OAckKnsAh8zXOghIzIiw=
Date: Sun, 13 Oct 2019 04:47:52 -0700
From: Marten Seemann <>
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_5da30ee859ff2_62fd3f9ccd0cd95c193035"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: marten-seemann
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: Sun, 13 Oct 2019 11:47:55 -0000

I'm in favor of the change that @DavidSchinazi is suggesting in #3087.
There's no reason for us to use TLS presentation language, if anything, it just makes the spec harder to read for people who are unfamiliar with the TLS presentation language (if I remember correctly, this came up multiple times on issues here and / or on Slack).

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