Date: Fri, 04 May 2018 05:47:02 -0700
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4abe6c5c0ae363d359420283eb618272a5c68c61ac492cf000000011704184692a169ce131475f5@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1336/386590536@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1336@github.com>
References: <quicwg/base-drafts/issues/1336@github.com>
Subject: Re: [quicwg/base-drafts] Consistent presenting Connection ID in
 packet or frame (#1336)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5aec5646b166c_1f233fe0e27c8f78767c6";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/vNrjphdWtSQhLJdKkUz-CB14kjI>


----==_mimepart_5aec5646b166c_1f233fe0e27c8f78767c6
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

If a client uses an ephemeral port to connect to a peer, the client would have to choose to re-use that port to create a new QUIC connection.  I don't see why it wouldn't know whether that was possible when it created the connection?

I expect most client code will not use the same port for multiple QUIC connections, but if they support that(ie: maybe server to server connections?), then they should't use 0-len CIDs.

Do you have a use case in mind where typically you don't need a CID and then suddenly you do?

-- 
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/1336#issuecomment-386590536
----==_mimepart_5aec5646b166c_1f233fe0e27c8f78767c6
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>If a client uses an ephemeral port to connect to a peer, the client wo=
uld have to choose to re-use that port to create a new QUIC connection.  =
I don't see why it wouldn't know whether that was possible when it create=
d the connection?</p>
<p>I expect most client code will not use the same port for multiple QUIC=
 connections, but if they support that(ie: maybe server to server connect=
ions?), then they should't use 0-len CIDs.</p>
<p>Do you have a use case in mind where typically you don't need a CID an=
d then suddenly you do?</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/1336#issuecomment-386590536">view it on GitHub</a>,=
 or <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkq5_T=
MPv1ZXT0dDA0xMZmn9aybBknks5tvE3GgaJpZM4Tx5-h">mute the thread</a>.<img sr=
c=3D"https://github.com/notifications/beacon/AWbkq6JO9AzFPaZwga0IghCVNtel=
i0TIks5tvE3GgaJpZM4Tx5-h.gif" height=3D"1" width=3D"1" alt=3D"" /></p>
<div itemscope itemtype=3D"http://schema.org/EmailMessage">
<div itemprop=3D"action" itemscope itemtype=3D"http://schema.org/ViewActi=
on">
  <link itemprop=3D"url" href=3D"https://github.com/quicwg/base-drafts/is=
sues/1336#issuecomment-386590536"></link>
  <meta itemprop=3D"name" content=3D"View Issue"></meta>
</div>
<meta itemprop=3D"description" content=3D"View this Issue on GitHub"></me=
ta>
</div>

<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://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6=
-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubuserconte=
nt.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","=
action":{"name":"Open in GitHub","url":"https://github.com/quicwg/base-dr=
afts"}},"updates":{"snippets":[{"icon":"PERSON","message":"@ianswett in #=
1336: If a client uses an ephemeral port to connect to a peer, the client=
 would have to choose to re-use that port to create a new QUIC connection=
.  I don't see why it wouldn't know whether that was possible when it cre=
ated the connection?\r\n\r\nI expect most client code will not use the sa=
me port for multiple QUIC connections, but if they support that(ie: maybe=
 server to server connections?), then they should't use 0-len CIDs.\r\n\r=
\nDo you have a use case in mind where typically you don't need a CID and=
 then suddenly you do?"}],"action":{"name":"View Issue","url":"https://gi=
thub.com/quicwg/base-drafts/issues/1336#issuecomment-386590536"}}}</scrip=
t>=

----==_mimepart_5aec5646b166c_1f233fe0e27c8f78767c6--