Date: Sun, 09 Jun 2019 23:47:10 -0700
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJKZOPSIEHYJKTKADID53BMXW5EVBNHHBWDXNEU@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/500310603@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_5cfdfcee11bc9_5e4b3f9c302cd95c12242c0";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/hDP_qwbP5h72t4oDlK48TJ6DHNo>


----==_mimepart_5cfdfcee11bc9_5e4b3f9c302cd95c12242c0
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Changing CID in response to migration is a soft requirement since it cannot always be enforced since NAT rebinding might happen without endpoint interference. It can hurt privacy though.

CID changes can also happen without migration. One reason is for the peer to do so after an idle period because the risk of NAT rebinding is high. Another reason is to ensure CIDs do not get stale on long living connections since the peers routing infrastructure might regroup or move valid CID patterns to a new epoch.

-- 
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-500310603
----==_mimepart_5cfdfcee11bc9_5e4b3f9c302cd95c12242c0
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>Changing CID in response to migration is a soft requirement since it cannot always be enforced since NAT rebinding might happen without endpoint interference. It can hurt privacy though.</p>
<p>CID changes can also happen without migration. One reason is for the peer to do so after an idle period because the risk of NAT rebinding is high. Another reason is to ensure CIDs do not get stale on long living connections since the peers routing infrastructure might regroup or move valid CID patterns to a new epoch.</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=AFTOJK3USLB4OHI4H7EXEP3PZX2G5A5CNFSM4HWPX2Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXJCESY#issuecomment-500310603">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK5SHVXQV4QP3RJN6MTPZX2G5ANCNFSM4HWPX2ZQ">mute the thread</a>.<img src="https://github.com/notifications/beacon/AFTOJK5S64TLRVDXTHK5KB3PZX2G5A5CNFSM4HWPX2Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXJCESY.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=AFTOJK3USLB4OHI4H7EXEP3PZX2G5A5CNFSM4HWPX2Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXJCESY#issuecomment-500310603",
"url": "https://github.com/quicwg/base-drafts/issues/2778?email_source=notifications\u0026email_token=AFTOJK3USLB4OHI4H7EXEP3PZX2G5A5CNFSM4HWPX2Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXJCESY#issuecomment-500310603",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5cfdfcee11bc9_5e4b3f9c302cd95c12242c0--