Re: [quicwg/base-drafts] Fix language around CC on migration (#2918)

Mike Bishop <> Mon, 29 July 2019 20:22 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1A26312006A for <>; Mon, 29 Jul 2019 13:22:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Status: No, score=-7.999 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_32=0.001, 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 VQYzpAgV2_if for <>; Mon, 29 Jul 2019 13:22:23 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 90D92120045 for <>; Mon, 29 Jul 2019 13:22:23 -0700 (PDT)
Date: Mon, 29 Jul 2019 13:22:22 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1564431742; bh=4eXAgpRsOXXohhjpWyrYJY12j2HXWCwFjjNEpMWaU7M=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zT/ySAnRJgKEE9Mlx3CknwzmFeQ+YnsG8VLsfNWiq5+RfgxaqoGJYVYtDX17Kmcl3 stOLjBlsVd63LNKw3FdB23KVWJpjE8Y5AnHDik6qTfq+JikREkmxAdf1Q1lanlQlTr nkYmayYblxlOa3y4vNngJiXnxVEMH18cbGQ4DGTI=
From: Mike Bishop <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2918/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Fix language around CC on migration (#2918)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d3f557eabd74_3a723f80bf4cd9641343d7"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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, 29 Jul 2019 20:22:25 -0000

MikeBishop approved this pull request.

>  immediately reset the congestion controller and round-trip time estimator for
-the new path to initial values (see Sections A.3 and B.3 in {{QUIC-RECOVERY}}).
-An endpoint MUST NOT return to the send rate used for the previous path unless
-it is reasonably sure that the previous send rate is valid for the new path.
-For instance, a change in the client's port number is likely indicative of a
-rebinding in a middlebox and not a complete change in path.  This determination
-likely depends on heuristics, which could be imperfect; if the new path capacity
-is significantly reduced, ultimately this relies on the congestion controller
-responding to congestion signals and reducing send rates appropriately.
+the new path to initial values (see Sections A.3 and B.3 in {{QUIC-RECOVERY}})
+unless it has knowledge that the previous send rate or round-trip time estimate

unless it has knowledge that a previous send rate or round-trip time estimate
One reason a peer might do that is that you migrated cell->Wi-Fi->cell, and it still remembers the values from when you were on cellular.  Perhaps don't restrict this to the immediate previous measurement?

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