Date: Thu, 13 Dec 2018 12:21:59 -0800
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab20cfb989d4c0dce07fd0058d940f86ca7a15c5d092cf00000001182a816792a169ce174b5875@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2145/447107827@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2145@github.com>
References: <quicwg/base-drafts/issues/2145@github.com>
Subject: Re: [quicwg/base-drafts] Don't change CID on peer CID change (#2145)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5c12bf674c357_29fa3fd3d04d45c02449cb";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/bygxEP8AFQFrWSagoLimb7LObQE>


----==_mimepart_5c12bf674c357_29fa3fd3d04d45c02449cb
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

IIRC, @ekr is correct; we agreed to do this on peer address change.

- If you don't know you've been rebound and you reuse a CID, you've already linked yourself; the peer changing CID in response is pointless.
- If you either anticipate a rebinding or proactively change ports, and change both CID and address simultaneously, then it doesn't matter which of those triggers the peer to switch.
- If you switch CID without changing address, the address links you with fairly high probability anyway, so it doesn't really matter if the peer switches.

-- 
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/2145#issuecomment-447107827
----==_mimepart_5c12bf674c357_29fa3fd3d04d45c02449cb
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>IIRC, <a class=3D"user-mention" data-hovercard-type=3D"user" data-hove=
rcard-url=3D"/hovercards?user_id=3D1111457" data-octo-click=3D"hovercard-=
link-click" data-octo-dimensions=3D"link_type:self" href=3D"https://githu=
b.com/ekr">@ekr</a> is correct; we agreed to do this on peer address chan=
ge.</p>
<ul>
<li>If you don't know you've been rebound and you reuse a CID, you've alr=
eady linked yourself; the peer changing CID in response is pointless.</li=
>
<li>If you either anticipate a rebinding or proactively change ports, and=
 change both CID and address simultaneously, then it doesn't matter which=
 of those triggers the peer to switch.</li>
<li>If you switch CID without changing address, the address links you wit=
h fairly high probability anyway, so it doesn't really matter if the peer=
 switches.</li>
</ul>

<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&m=
dash;<br />You are receiving this because you are subscribed to this thre=
ad.<br />Reply to this email directly, <a href=3D"https://github.com/quic=
wg/base-drafts/issues/2145#issuecomment-447107827">view it on GitHub</a>,=
 or <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkq4v-=
YgRchIVWArZTxH9-ZePZbDkyks5u4rbngaJpZM4ZSOPm">mute the thread</a>.<img sr=
c=3D"https://github.com/notifications/beacon/AWbkq_zeAc-RsnhYiJ3RcpLIQD1u=
UGSZks5u4rbngaJpZM4ZSOPm.gif" height=3D"1" width=3D"1" alt=3D"" /></p>
<script type=3D"application/json" data-scope=3D"inboxmarkup">{"api_versio=
n":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name"=
:"GitHub"},"entity":{"external_key":"github/quicwg/base-drafts","title":"=
quicwg/base-drafts","subtitle":"GitHub repository","main_image_url":"http=
s://github.githubassets.com/images/email/message_cards/header.png","avata=
r_image_url":"https://github.githubassets.com/images/email/message_cards/=
avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/q=
uicwg/base-drafts"}},"updates":{"snippets":[{"icon":"PERSON","message":"@=
MikeBishop in #2145: IIRC, @ekr is correct; we agreed to do this on peer =
address change.\r\n\r\n- If you don't know you've been rebound and you re=
use a CID, you've already linked yourself; the peer changing CID in respo=
nse is pointless.\r\n- If you either anticipate a rebinding or proactivel=
y change ports, and change both CID and address simultaneously, then it d=
oesn't matter which of those triggers the peer to switch.\r\n- If you swi=
tch CID without changing address, the address links you with fairly high =
probability anyway, so it doesn't really matter if the peer switches."}],=
"action":{"name":"View Issue","url":"https://github.com/quicwg/base-draft=
s/issues/2145#issuecomment-447107827"}}}</script>
<script type=3D"application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/2145#issuecomment=
-447107827",
"url": "https://github.com/quicwg/base-drafts/issues/2145#issuecomment-44=
7107827",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>=

----==_mimepart_5c12bf674c357_29fa3fd3d04d45c02449cb--