Re: [quicwg/base-drafts] Does the amplification limit apply to PTO packets? (#3413)

ianswett <> Sun, 22 March 2020 13:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 498513A05AC for <>; Sun, 22 Mar 2020 06:08:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.008
X-Spam-Status: No, score=-2.008 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, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 dpodt9cFzyId for <>; Sun, 22 Mar 2020 06:08:05 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8EDAE3A0522 for <>; Sun, 22 Mar 2020 06:08:05 -0700 (PDT)
Date: Sun, 22 Mar 2020 06:08:04 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1584882484; bh=eSklaF1H09l2padwpnJsI/nsAiE/lzR5YIrrer+YQww=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QGOzLHaiQiWEADh/iomFoX/yFGQxKEBdVofk8zQLwA8g3TiEqMk3QpuPuIGG7PHsy gZ/wPjFUgtPtxQpsekwHlhvX6HDiku+hrzi7vb7hYRBWCOD+XF2egoIMM9+w7BBdEP 6L7SzM5AC9To9o5HCQ/7GPG6DOs41KO4PQSChkng=
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3413/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Does the amplification limit apply to PTO packets? (#3413)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e77633475a07_57bc3fb6a6acd9648030ed"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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: Sun, 22 Mar 2020 13:08:08 -0000

@ekr the PTO should be updated when an ack-eliciting packet is sent, since the right edge moves, so that case should already be handled correctly.  I'll write an editorial PR to try to make all this extra clear.

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