Date: Fri, 04 May 2018 05:14:31 -0700
From: Patrick McManus <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4abdd08258a70d56d7877791eb0f194026f752dc7fd92cf00000001170410a792a169ce131475f5@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/386582905@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_5aec4ea7db0aa_25712aff7ea0cf501784f8";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Z_pHUyduBykx2jPHLS1cTt6TdRc>


----==_mimepart_5aec4ea7db0aa_25712aff7ea0cf501784f8
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

tangentially, no CID-len for short packets caused a problem for @larseggert who wanted to disambiguate between 0-len and non-0 len CID on the same 4 tuple. I believe in the omit-cid era he would omit them on the first connection from a 4 tuple and start using them after that.

plausibly the compromise for that is bringing back a shorter amount of signaling for a variable length encoding.. either making the min cid len 1 byte instead of 4, or even (less desirably imo) bringing the omit cid bit back.


-- 
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-386582905
----==_mimepart_5aec4ea7db0aa_25712aff7ea0cf501784f8
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>tangentially, no CID-len for short packets caused a problem for <a cla=
ss=3D"user-mention" data-hovercard-user-id=3D"200328" data-octo-click=3D"=
hovercard-link-click" data-octo-dimensions=3D"link_type:self" href=3D"htt=
ps://github.com/larseggert">@larseggert</a> who wanted to disambiguate be=
tween 0-len and non-0 len CID on the same 4 tuple. I believe in the omit-=
cid era he would omit them on the first connection from a 4 tuple and sta=
rt using them after that.</p>
<p>plausibly the compromise for that is bringing back a shorter amount of=
 signaling for a variable length encoding.. either making the min cid len=
 1 byte instead of 4, or even (less desirably imo) bringing the omit cid =
bit back.</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-386582905">view it on GitHub</a>,=
 or <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkq5wv=
oqnIHJIsymOpL7M2Pm9IyoL1ks5tvEYngaJpZM4Tx5-h">mute the thread</a>.<img sr=
c=3D"https://github.com/notifications/beacon/AWbkqyYG9IdVikv3hwd9aqy-ptoM=
gqLrks5tvEYngaJpZM4Tx5-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-386582905"></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":"@mcmanus in #1=
336: tangentially, no CID-len for short packets caused a problem for @lar=
seggert who wanted to disambiguate between 0-len and non-0 len CID on the=
 same 4 tuple. I believe in the omit-cid era he would omit them on the fi=
rst connection from a 4 tuple and start using them after that.\r\n\r\npla=
usibly the compromise for that is bringing back a shorter amount of signa=
ling for a variable length encoding.. either making the min cid len 1 byt=
e instead of 4, or even (less desirably imo) bringing the omit cid bit ba=
ck.\r\n"}],"action":{"name":"View Issue","url":"https://github.com/quicwg=
/base-drafts/issues/1336#issuecomment-386582905"}}}</script>=

----==_mimepart_5aec4ea7db0aa_25712aff7ea0cf501784f8--