[quicwg/base-drafts] New path may not have the same RTT (#4026)

Lars Eggert <notifications@github.com> Wed, 19 August 2020 14:38 UTC

Date: Wed, 19 Aug 2020 07:38:39 -0700
From: Lars Eggert <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5WMRC7VZ3RMTXGDG55JENG7EVBNHHCRJHAV4@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/4026@github.com>
Subject: [quicwg/base-drafts] New path may not have the same RTT (#4026)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f3d396f60217_3e1519649939f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/rii_USPpbpTQQWW5ksxvZPHe4Cs>

(Broken out of #3214.)

> 9.2.  Initiating Connection Migration/
- I assert the new path may not have the same RTT, because the path could traverse a different set of network devices or be subject to different policies that influence forwarding behaviour. These are not currently listed here, but are the basis for some later text in 9.3.1. Can we mention here?


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

[quicwg/base-drafts] New path may not have the sa… Lars Eggert
Re: [quicwg/base-drafts] New path may not have th… Mike Bishop
Re: [quicwg/base-drafts] New path may not have th… ianswett
Re: [quicwg/base-drafts] New path may not have th… ianswett
Re: [quicwg/base-drafts] New path may not have th… Martin Thomson