Date: Wed, 14 Aug 2019 23:51:38 -0700
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJK3J5HKVBJPZDO4MK3V3MIZXVEVBNHHBWDXNEU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2778/521536111@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2778@github.com>
References: <quicwg/base-drafts/issues/2778@github.com>
Subject: Re: [quicwg/base-drafts] CID change still required in response to
 migration? (#2778)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5d5500faa35e4_10f83fc4f7ecd9601084f8";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/U2XKt8bktZSncEVzFn6D1AaQLbk>


----==_mimepart_5d5500faa35e4_10f83fc4f7ecd9601084f8
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Agreed. IIUC, the only endpoint that "initiates" a CID change is the client, because only the client side that migrates (or probes) a new path. This is the case for SPA too.

Therefore, I believe that stating something along the lines of the following is sufficient: a server MUST respond with a new CID to a packet that has been received on a new path with a new CID.

-- 
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/2778#issuecomment-521536111
----==_mimepart_5d5500faa35e4_10f83fc4f7ecd9601084f8
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>Agreed. IIUC, the only endpoint that "initiates" a CID change is the client, because only the client side that migrates (or probes) a new path. This is the case for SPA too.</p>
<p>Therefore, I believe that stating something along the lines of the following is sufficient: a server MUST respond with a new CID to a packet that has been received on a new path with a new CID.</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/2778?email_source=notifications&amp;email_token=AFTOJK3SODA4LDKH7DUWBP3QET4HVA5CNFSM4HWPX2Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4LAE3Y#issuecomment-521536111">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK52LGCCN4RFCU2QDBTQET4HVANCNFSM4HWPX2ZQ">mute the thread</a>.<img src="https://github.com/notifications/beacon/AFTOJK6GDIEQ4NR5AYZU7BLQET4HVA5CNFSM4HWPX2Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4LAE3Y.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/2778?email_source=notifications\u0026email_token=AFTOJK3SODA4LDKH7DUWBP3QET4HVA5CNFSM4HWPX2Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4LAE3Y#issuecomment-521536111",
"url": "https://github.com/quicwg/base-drafts/issues/2778?email_source=notifications\u0026email_token=AFTOJK3SODA4LDKH7DUWBP3QET4HVA5CNFSM4HWPX2Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4LAE3Y#issuecomment-521536111",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5d5500faa35e4_10f83fc4f7ecd9601084f8--