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

Martin Thomson <> Thu, 10 October 2019 02:12 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B1593120072 for <>; Wed, 9 Oct 2019 19:12:00 -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 8zdJQeWwWVjo for <>; Wed, 9 Oct 2019 19:11:59 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CA837120020 for <>; Wed, 9 Oct 2019 19:11:58 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id AFC806A0E34 for <>; Wed, 9 Oct 2019 19:11:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1570673517; bh=6eqbikqcebmooZjdprqiIDABocCJuzXvuuzZxE6jZA4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=T2W5nvGOhprIA5CAXl3PUnNePeCyqFlU4axaRzGaSuQwHCVbTGdbZ+zQhw8pbuXtE Ijw6cPDEq5VacGhZ1amrvHmkz3+evEoVoZTBaFkz9tPg6X31jT6656lIUZjWDT3bTd rSJ27Os+Gs/oo3HSNtOULR5cyeabrX8uAVZmQovo=
Date: Wed, 09 Oct 2019 19:11:57 -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_5d9e936da062c_10543fd4580cd96c70040"; 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: Thu, 10 Oct 2019 02:12:01 -0000

The insight I had here was this:

If you are sending Initial, it is possible that this is the only packet in the datagram that can be processed by your peer.  If that is the case, then a client needs to ensure that it pads the datagram as though no other packets were present.

You can infer from the fact that you have Handshake keys that the server is able to process Handshake packets, and then extend that to say that if you include Handshake packets then the server won't need padding.  But then you can extend that inference to saying that there is no need to send any Initial packets (as the current draft does; currently, you are not required to keep Initial keys once you are sending with Handshake keys).

Either way, I figure that it is better to keep things simple and say "if Initial, pad".  In those cases where padding ends up being excessive, it's only excessive for a short while.

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