Re: [quicwg/base-drafts] MSS Clamping Support (#3330)

Igor Lubashev <> Mon, 13 January 2020 15:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 87D12120104 for <>; Mon, 13 Jan 2020 07:31:45 -0800 (PST)
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 ctXiEjfeP24W for <>; Mon, 13 Jan 2020 07:31:44 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D61AE12003E for <>; Mon, 13 Jan 2020 07:31:43 -0800 (PST)
Date: Mon, 13 Jan 2020 07:31:42 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1578929502; bh=ateRIORM6QVKH5aS7aqkYi0Gnl3QXPoEd5EEa2V/wYo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=KdnifXuT4YOlBMnOtG6O8e6Sw1VSVwelf+0fA+XVvd3xSJyY5rpEtczYQ6Iaf8J1E O0+bOpaDSPM4efTHzKnz4M0o/jVy1z3ClbLcRJHL/2SDkUJxZBkbk1q9LQIDyH5Xk7 B7kgVAsCx2pQOSuipUoQQNva+vg0KDJfNI3cx8fs=
From: Igor Lubashev <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3330/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] MSS Clamping Support (#3330)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e1c8d5ee480c_6f263fe8e56cd96012694d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: igorlord
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: Mon, 13 Jan 2020 15:31:46 -0000

@TheBlueMatt The selection of which frames to use for MPTUD probes could be left to the implementations. I doubt that implementations that go into trouble of implementing PLPMTUD would be naive enough to not think carefully of this issue.

In fact, I think data frames could be better for MPTUD probes than useless PING/PADDING in some cases.  Imagine having two streams at different priorities ready to transmit.  You can send high-priority stream's data using known-good packet sizes, while fill your PMTUD probes with low-priority stream's data.

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