Date: Thu, 09 Jul 2020 09:55:07 -0700
From: Igor Lubashev <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJK6UDCXFETIUOZEVET55CMWOXEVBNHHCMFSQTA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3765/656239210@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3765@github.com>
References: <quicwg/base-drafts/issues/3765@github.com>
Subject: Re: [quicwg/base-drafts] disable_active_migration with SPA (#3765)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5f074beb15c16_5ab63f8b81acd964145451";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/gTHc4nAFSUamaQHcIZjqn5tTpLM>


----==_mimepart_5f074beb15c16_5ab63f8b81acd964145451
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

I think we actually can **almost** support the use cases I presented without a change, actually.

A server that does not desire a client to actively migrate can just avoid sending NEW_CONNECTION_ID frames.  Since migration to the SPA requires a change in CID, and a CID sent in preferred_address is the only additional CID available, that CID will be used up during SPA migration and no additional active migrations will be possible.

This **almost** solves the problem, because the client can combine active migration with SPA migration.  If we prohibit such active migration at the same time with SPA migration, if disable_active_migration TP is present (and, possibly, no NEW_CONNECTION_IDs have been received), it would solve the problem completely.

-- 
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/3765#issuecomment-656239210
----==_mimepart_5f074beb15c16_5ab63f8b81acd964145451
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p></p>
<p>I think we actually can <strong>almost</strong> support the use cases I presented without a change, actually.</p>
<p>A server that does not desire a client to actively migrate can just avoid sending NEW_CONNECTION_ID frames.  Since migration to the SPA requires a change in CID, and a CID sent in preferred_address is the only additional CID available, that CID will be used up during SPA migration and no additional active migrations will be possible.</p>
<p>This <strong>almost</strong> solves the problem, because the client can combine active migration with SPA migration.  If we prohibit such active migration at the same time with SPA migration, if disable_active_migration TP is present (and, possibly, no NEW_CONNECTION_IDs have been received), it would solve the problem completely.</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/3765#issuecomment-656239210">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK5OW6DKZPS4FCRSY3DR2XY6XANCNFSM4N6LJSKQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AFTOJK73JUWMI34VPKBA563R2XY6XA5CNFSM4N6LJSK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOE4OWU2Q.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/3765#issuecomment-656239210",
"url": "https://github.com/quicwg/base-drafts/issues/3765#issuecomment-656239210",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5f074beb15c16_5ab63f8b81acd964145451--