Date: Wed, 29 Apr 2020 08:48:42 -0700
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJK3FL2ZQYM347G5BLPV4WWBNVEVBNHHCITYZTQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3608@github.com>
Subject: [quicwg/base-drafts] 5-tuple routing and SPA (#3608)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5ea9a1da45679_52c73ff7fc4cd9642007610";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/sJKHlGqwPiaSVUiZtoZl61U07XI>


----==_mimepart_5ea9a1da45679_52c73ff7fc4cd9642007610
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Offshoot from #3536 review.  Servers behind a load balancer, and the load balancer isn't CID-aware.  Each server gives out an IP:port per client in the `preferred_address`  parameter.  _If_ the client moves to the SPA, then future migration is fine -- it will continue to talk to the same server using the preferred address.  If the client doesn't move, those future migrations will break.  There's currently no way to set `disable_migration` to "only if you don't use my preferred address".

Similarly, if the primary connection is to an anycast address, if the client fails to move to the preferred address, subsequent migration will likely break.

Should we blanket recommend that clients not actively migrate if they ignore / are unsuccessful in using the SPA?  Or should there be a way for the server to indicate that?

-- 
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/3608
----==_mimepart_5ea9a1da45679_52c73ff7fc4cd9642007610
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p></p>
<p>Offshoot from <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="585300603" data-permission-text="Title is private" data-url="https://github.com/quicwg/base-drafts/issues/3536" data-hovercard-type="pull_request" data-hovercard-url="/quicwg/base-drafts/pull/3536/hovercard" href="https://github.com/quicwg/base-drafts/pull/3536">#3536</a> review.  Servers behind a load balancer, and the load balancer isn't CID-aware.  Each server gives out an IP:port per client in the <code>preferred_address</code>  parameter.  <em>If</em> the client moves to the SPA, then future migration is fine -- it will continue to talk to the same server using the preferred address.  If the client doesn't move, those future migrations will break.  There's currently no way to set <code>disable_migration</code> to "only if you don't use my preferred address".</p>
<p>Similarly, if the primary connection is to an anycast address, if the client fails to move to the preferred address, subsequent migration will likely break.</p>
<p>Should we blanket recommend that clients not actively migrate if they ignore / are unsuccessful in using the SPA?  Or should there be a way for the server to indicate that?</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/quicwg/base-drafts/issues/3608">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK57HSTAYNLJFPOIWGDRPBD5VANCNFSM4MT247UQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AFTOJK4THLI34VWPAHV5LTDRPBD5VA5CNFSM4MT247U2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4JCPDGOA.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/3608",
"url": "https://github.com/quicwg/base-drafts/issues/3608",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5ea9a1da45679_52c73ff7fc4cd9642007610--