Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id 776661286E7
 for <quic-issues@ietfa.amsl.com>; Fri, 14 Dec 2018 17:57:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.056
X-Spam-Level: 
X-Spam-Status: No, score=-8.056 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1,
 DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404,
 HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5,
 SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key)
 header.d=github.com
Received: from mail.ietf.org ([4.31.198.44])
 by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id e-I-5OqwCVkg for <quic-issues@ietfa.amsl.com>;
 Fri, 14 Dec 2018 17:57:40 -0800 (PST)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id CC289130EB1
 for <quic-issues@ietf.org>; Fri, 14 Dec 2018 17:57:39 -0800 (PST)
Date: Fri, 14 Dec 2018 17:57:38 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
 s=pf2014; t=1544839058;
 bh=/g5pSNRlaP2HtD//YOFFNoEBsl+CQaTv3Pqz90s6xZc=;
 h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
 List-Archive:List-Post:List-Unsubscribe:From;
 b=F6nDMNoTuJNIfyLhqzjZRzI7M7pHCyjUA5hAAnG0sQt8krKFtG0a4vS/euB5OARzp
 CEWIP7MzfGZDi6RD7fbTWeIvIj/BpLXc00P0djSZeJ0Ldojl6bJXr/Qw41zhxrJnrm
 Nx1vGU4zGqLIEqu6GmbYb2KASZSC8mRhn+HonuUE=
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab2127b71fa10a48730b205c094552cff5cb02e33a92cf00000001182c219292a169ce174b5875@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/447527813@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_5c145f92775e6_141d3fed200d45c4105703f";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/OgxYuhidxWLDmdIgBAsIraPEVmY>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG
 <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>,
 <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>,
 <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Dec 2018 01:57:42 -0000


----==_mimepart_5c145f92775e6_141d3fed200d45c4105703f
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

My recollection is what @MikeBishop says.  I remember discussing that changing CID on both sides allows a flow to be broken up into flowlets, but if the address is the same on both sides, that's a pretty clear signal anyways. I am fine with requiring a change only if the peer's CID and address change.

-- 
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-447527813
----==_mimepart_5c145f92775e6_141d3fed200d45c4105703f
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>My recollection is what <a class=3D"user-mention" data-hovercard-type=3D=
"user" data-hovercard-url=3D"/hovercards?user_id=3D4273797" data-octo-cli=
ck=3D"hovercard-link-click" data-octo-dimensions=3D"link_type:self" href=3D=
"https://github.com/MikeBishop">@MikeBishop</a> says.  I remember discuss=
ing that changing CID on both sides allows a flow to be broken up into fl=
owlets, but if the address is the same on both sides, that's a pretty cle=
ar signal anyways. I am fine with requiring a change only if the peer's C=
ID and address change.</p>

<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-447527813">view it on GitHub</a>,=
 or <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkqzxR=
Z7bhJVVt2uyxzlOeTWiYvHSYks5u5FcSgaJpZM4ZSOPm">mute the thread</a>.<img sr=
c=3D"https://github.com/notifications/beacon/AWbkq_4ElloKG4IdGGxZIqd8QFTS=
9LYYks5u5FcSgaJpZM4ZSOPm.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":"@=
janaiyengar in #2145: My recollection is what @MikeBishop says.  I rememb=
er discussing that changing CID on both sides allows a flow to be broken =
up into flowlets, but if the address is the same on both sides, that's a =
pretty clear signal anyways. I am fine with requiring a change only if th=
e peer's CID and address change."}],"action":{"name":"View Issue","url":"=
https://github.com/quicwg/base-drafts/issues/2145#issuecomment-447527813"=
}}}</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=
-447527813",
"url": "https://github.com/quicwg/base-drafts/issues/2145#issuecomment-44=
7527813",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>=

----==_mimepart_5c145f92775e6_141d3fed200d45c4105703f--

