Re: [quicwg/base-drafts] Are transport parameters mandatory? (#2528)

Kazuho Oku <> Tue, 19 March 2019 22:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E4FA112E036 for <>; Tue, 19 Mar 2019 15:00:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Status: No, score=-6.597 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_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 6bUzIPbTph6Q for <>; Tue, 19 Mar 2019 15:00:29 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CF91D1311CF for <>; Tue, 19 Mar 2019 15:00:28 -0700 (PDT)
Date: Tue, 19 Mar 2019 15:00:27 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1553032827; bh=CrfkAuyNO0HrExSXdSoXia7QbqVJVYc0e4ErftlZEJI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ZxoYtE/o8jM5cxQ3DFeN+Z0hQpDXYdGCMfUBY0smd4rbDSbjOEwUiYGXakNYpaHB4 /oazphoAMleoMrW5pEebYm+DpcWAEDPrNUaV7jtyCl9WAJ4wis4xBbK4oxmRsITbA5 YEFFedWShKzk7hwWaJj5jsJxEYUvzitMpJkVRmZs=
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2528/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Are transport parameters mandatory? (#2528)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c91667b5d86b_27bd3f86cf2d45c011484a"; 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, 19 Mar 2019 22:00:31 -0000

I think we can call the entire extension as an option.

As to @DavidSchinazi's point, I'm not sure if it helps in practice. TLS 1.3 stacks that run on top of TCP does not have (and it's doubtful if all of them would have) the capability to detect and raise an error when it sees the QUIC TP extension.

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