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

Martin Thomson <notifications@github.com> Tue, 04 February 2020 15:41 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 9627E12084A for <quic-issues@ietfa.amsl.com>; Tue, 4 Feb 2020 07:41:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.896
X-Spam-Level:
X-Spam-Status: No, score=-3.896 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_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 usE3VGkKuKlT for <quic-issues@ietfa.amsl.com>; Tue, 4 Feb 2020 07:41:50 -0800 (PST)
Received: from out-28.smtp.github.com (out-28.smtp.github.com [192.30.252.211]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 883EF12084C for <quic-issues@ietf.org>; Tue, 4 Feb 2020 07:41:50 -0800 (PST)
Date: Tue, 04 Feb 2020 07:41:49 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1580830909; bh=YpQwxpuI9ig/WSlYfrKqKtlIHAWhoUXjwzL5ogqug4w=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=kO4jbpeuUvcoiGueWEyNdU3axxui5+eRzoCB/jYdu239nNrWMy2RY1ML3aaYi3K7M RcL/ZRaUKxM/YIRJ3cWGjH/BIxbtqbytlpjipOwtmK5vp3HdHTLteJN9464TIgoLtX nPOY/qxyjpOTrv7/tnuvBxsbNAiSunkewziSkdfg=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK3U2WAYZ2TRHMZYJUF4I3BT3EVBNHHCCXPLHM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3413@github.com>
Subject: [quicwg/base-drafts] Does the amplification limit apply to PTO packets? (#3413)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e3990bd8a3c3_45133f87d62cd95c45243c"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/u-hEvTbEDe9uE_3XdZVM5E-ncPU>
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, 04 Feb 2020 15:41:52 -0000

>From @gorryfair in #3214, this is not a nit:

>> Prior to validating the client address, servers MUST NOT send more
than three times as many bytes as the number of bytes they have
received.

> So, let me understand - does that include retransmissions? or is this constrain within the PTO or something?

I think that the intent was that the server limit its sending, including PTO.


-- 
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/3413