Re: [quicwg/base-drafts] Packets on one path must not adjust values for a different path (#3139)

Eric Kinnear <notifications@github.com> Mon, 04 November 2019 05:43 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 A3FF212008B for <quic-issues@ietfa.amsl.com>; Sun, 3 Nov 2019 21:43:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Level:
X-Spam-Status: No, score=-6.596 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_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 aRXpIZCDgIDv for <quic-issues@ietfa.amsl.com>; Sun, 3 Nov 2019 21:43:22 -0800 (PST)
Received: from out-17.smtp.github.com (out-17.smtp.github.com [192.30.252.200]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6132120077 for <quic-issues@ietf.org>; Sun, 3 Nov 2019 21:43:22 -0800 (PST)
Received: from github-lowworker-943b171.ac4-iad.github.net (github-lowworker-943b171.ac4-iad.github.net [10.52.22.59]) by smtp.github.com (Postfix) with ESMTP id E635A6E01E4 for <quic-issues@ietf.org>; Sun, 3 Nov 2019 21:43:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1572846201; bh=LG2SJcirgvxW3RSGv33E16kh5coHqgOxKZ8MvLzYHRI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=K+q9pdsZbugpbV+IqIpLO3mZj69wfqgyzLkiyaKecGOicQCggBIds/Z0DjGiRPmc1 jTZ1fRRGct8Cb4eGne2B3C235V5Px661QZYxfv25aOcBsALYemWMuDQ6Vtp/BGYhyj enelPDwvYU6/cL0FyZhxq6COp9QMFVIFAU+9v9mk=
Date: Sun, 03 Nov 2019 21:43:21 -0800
From: Eric Kinnear <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK3YWJSBKVVEWJWQ5LF3ZTWPTEVBNHHB47SZJY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3139/review/310884986@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3139@github.com>
References: <quicwg/base-drafts/pull/3139@github.com>
Subject: Re: [quicwg/base-drafts] Packets on one path must not adjust values for a different path (#3139)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dbfba79d6a58_25923fb2358cd96865881d"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: erickinnear
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/RQ3YU4kDyNjrViTWpC5nYXdntxE>
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: Mon, 04 Nov 2019 05:43:25 -0000

erickinnear commented on this pull request.



> @@ -2096,7 +2096,7 @@ more likely to indicate an intentional migration rather than an attack.
 ## Loss Detection and Congestion Control {#migration-cc}
 
 The capacity available on the new path might not be the same as the old path.
-Packets sent on the old path SHOULD NOT contribute to congestion control or RTT
+Packets sent on the old path MUST NOT contribute to congestion control or RTT
 estimation for the new path.
 

I'd tend to agree with Ian that it's probably not necessary to add text covering that -- you're doing the safest thing if you treat them as completely independent, and you're likely to have new data from the new path just from validation or within a few RTTs.

(That said, I'd be quite interested in the results of experiments in this area, and there's no enforcement here that prevents such experimentation.)

-- 
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/pull/3139#discussion_r341908356