Re: [quicwg/base-drafts] Allow ClientHello to span multiple QUIC packets (#3045)

Nick Banks <> Tue, 17 September 2019 17:01 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A7F39120954 for <>; Tue, 17 Sep 2019 10:01:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Status: No, score=-6.454 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_20=1.546, 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 qMHJrV-DFRb0 for <>; Tue, 17 Sep 2019 10:01:41 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DBE431208EE for <>; Tue, 17 Sep 2019 10:01:36 -0700 (PDT)
Date: Tue, 17 Sep 2019 10:01:36 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1568739696; bh=LN8tJYc8VZIUsTKSv3dJ7jXPLig1LPPqch7tMhJe4+w=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pbkOEdnjFbqqgicW5vnj5AE/4KUWtTv68E4JwGegOszdjowLpQV3Zhcl0qqTBjji2 TQqEFp/icNL7jgUjzUdxJqHGTfe1419ePVt8zGeUyLa74J7KWgfS1tFAedPSyEIz7v 7coSMovHj0JcL3/5vqsISDQubqdjeG50pOILtP9A=
From: Nick Banks <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3045/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Allow ClientHello to span multiple QUIC packets (#3045)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d8111702c4da_56ca3fe511acd95c2607f0"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nibanks
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, 17 Sep 2019 17:01:44 -0000

I'm not arguing that this PR would require loads more code, but I definitely don't agree that it's a "good simplification" of the current design. This adds additional attack surfaces that must be analyzed and implementations ensure they have adequate defense.

Again, I ask is this absolutely required for V1? What chartered requirements for QUIC deem this change necessary for V1?

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