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

Mike Bishop <> Thu, 10 October 2019 19:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B0EFE120170 for <>; Thu, 10 Oct 2019 12:20:20 -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 I2q7yn60Ncoj for <>; Thu, 10 Oct 2019 12:20:19 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CE8D2120089 for <>; Thu, 10 Oct 2019 12:20:18 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 32B006611EF for <>; Thu, 10 Oct 2019 12:20:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1570735218; bh=QY0DROTNoz3eFXgB3FLcYCwk2xU0tZQcxcp2nJE0jmU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=XzelJTZrVELc8VEGW/uUx2CFyXwWngyoLX60L3qr0VgEfLylAYS1Pl7A65lqo2C9l Swm6KnMbjEvdDX6J3X2w/VmzHkruc99B6/O8GiGaE+xZUHaoWUKrJl+L83gAcHz2sV tTTtRWhUxWthQfmuOI4zUF+51ZBGGR28h+Ky7yFc=
Date: Thu, 10 Oct 2019 12:20:18 -0700
From: Mike Bishop <>
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_5d9f847224997_11393fde6eccd968858a7"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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 19:20:21 -0000

> > 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.
> I don't know where you get this from. It's total datagram size that matters, not the contents of the rest of the datagram (which is why the neqo padding strategy works).

I'm not seeing a conflict between these statements.  If the packet contains an Initial, the total datagram size must be at least 1200 bytes.  You can achieve this by padding any packet in the payload; I don't think anyone is advocating for requiring the padding be in a particular spot.

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