Re: [quicwg/base-drafts] Padding requirement seems to be incorrect. (#3053)

Martin Thomson <> Fri, 11 October 2019 02:42 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 706FE1200E6 for <>; Thu, 10 Oct 2019 19:42:33 -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 NoKBSdAhcZBb for <>; Thu, 10 Oct 2019 19:42:32 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0A3B8120041 for <>; Thu, 10 Oct 2019 19:42:32 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 137CE1C0288 for <>; Thu, 10 Oct 2019 19:42:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1570761751; bh=Q+BeAzPMwOn3+FmuqyFGHRlOpjj10L1qVEogEc8dNb8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=PtQZ0xwt3bSx60PEl1ideaik0sj7m95rmdZ/PljwyHPVEpQgVW9XHqsrKYSnU3aem uU8KF4cNykgL1pXpWDsCv/t9h1PZ3wIeY+cC0jMre38obGmMRMxGWoxFVF6Qhe9J1b Hzm9wSiCM7mnS1NPAS/LP1fTGHH+3+9qYjECTwF0=
Date: Thu, 10 Oct 2019 19:42:31 -0700
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3053/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Padding requirement seems to be incorrect. (#3053)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d9fec1754db_1c403f82142cd9602310bd"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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: Fri, 11 Oct 2019 02:42:34 -0000

The change makes it clear that if you send Initial+0-RTT then you should still pad to 1200.  That's all.  Previously, you would not have been required to pad, which would have been bad.

Most of the debate and discussion is about the knock-on consequences of applying the broader rule, which I don't think are that important.  And yes, the whole "when do you discard Initial keys" thing does confound things a little.

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