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

Martin Thomson <> Fri, 11 October 2019 00:23 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7853912003E for <>; Thu, 10 Oct 2019 17:23:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Status: No, score=-6.382 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_24=1.618, 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 2RhNCYgDkVkK for <>; Thu, 10 Oct 2019 17:23: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 BC39E12007C for <>; Thu, 10 Oct 2019 17:23:32 -0700 (PDT)
Date: Thu, 10 Oct 2019 17:23:31 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1570753411; bh=/41kpNLE41MGzFItjpuaaUg6T0nt6T8mqmGGt8Hk4Ms=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=FZ7PwYdLvapxXGuQPFs/mBeI/OSTB0OsfBf7viyvWJj2OPGw3/2ufxDeVLmQBOwKX TZn+nRBiY/M2et6b/Po2lS8Nirby666qJvtUMiODnAi3cHDhrvPWGHwwEbzo4fvL9q cEk4njx7bX2fRrevDbKL3tma928TSjBADryKitw4=
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_5d9fcb83dbf46_7593fe7528cd95c1127d0"; 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 00:23:34 -0000

Imprecise wording on my part.  "pads the datagram as though no other packets were present" might be better as "as though no other packets can be processed by the server".

Let's keep in mind that the proposed changes is just striking "only" in "Clients MUST ensure that UDP datagrams containing ~~only~~ Initial packets have UDP payloads of at least 1200 bytes, [...]".

I agree that this will result in larger packets than are ideal in a couple of cases.  But the ACK-only Initial packets a client sent are most likely coalesced with other packets outside of cases where the padding is genuinely required.

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