IETF Logo Mail Archive

Re: [quicwg/base-drafts] Clarify padding of INITIAL packets (#3255)

Robin Marx <notifications@github.com> Tue, 19 November 2019 03:04 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F02C2120251 for <quic-issues@ietfa.amsl.com>; Mon, 18 Nov 2019 19:04:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level:
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: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WASX1vMo1XfX for <quic-issues@ietfa.amsl.com>; Mon, 18 Nov 2019 19:04:24 -0800 (PST)
Received: from out-22.smtp.github.com (out-22.smtp.github.com [192.30.252.205]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A45EB120255 for <quic-issues@ietf.org>; Mon, 18 Nov 2019 19:04:24 -0800 (PST)
Received: from github-lowworker-f144ac1.va3-iad.github.net (github-lowworker-f144ac1.va3-iad.github.net [10.48.16.59]) by smtp.github.com (Postfix) with ESMTP id 0A115A0775 for <quic-issues@ietf.org>; Mon, 18 Nov 2019 19:04:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1574132664; bh=kHIb5eLteuzB2WXAi5xtcFCY4/qYh+/ArNw7w+Y4cAw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=kVXpeVHMyfffsaT5GMQ/vLCVMClzasZlqy1nTvS9VH0ZOH80FohZSCd3o7/T9vZ8J yuK/sTrXg3MXkkKGFND4Q8b8scjRgC/M/dqStv+sgqkDZveDa0nAaWASc0O55HEioU YzXtTR5G4u6qQT1QbxP2o/Ry3j6wrD5sENDrGWaM=
Date: Mon, 18 Nov 2019 19:04:23 -0800
From: Robin Marx <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4TNBCARAOZ5QMNANV34CHDPEVBNHHB6PLW5A@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3255/555311145@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3255@github.com>
References: <quicwg/base-drafts/issues/3255@github.com>
Subject: Re: [quicwg/base-drafts] Clarify padding of INITIAL packets (#3255)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dd35bb7ee0d8_3ed3fa8cb0cd95c7384f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: rmarx
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/G1FGXofk53GPPLoi1axwl78IOPc>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2019 03:04:26 -0000

Thank you for the PR Martin. 

Just for my understanding: the requirement to pad client initials from the second flight onward (i.e., after receiving server packets, ACKing server initials) is purely for convenience. It is not necessary for PMTU or anti-amplification-allowance. As such, the limit should also not be enforced at intermediaries wholesale?   

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/3255#issuecomment-555311145

v2.23.0 | Report a Bug | By Email