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 E74E4126BF0
 for <quic-issues@ietfa.amsl.com>; Fri,  4 May 2018 05:40:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.606
X-Spam-Level: 
X-Spam-Status: No, score=-6.606 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, 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,
 T_DKIMWL_WL_HIGH=-0.01] 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 mvmqHttsrMaf for <quic-issues@ietfa.amsl.com>;
 Fri,  4 May 2018 05:40:29 -0700 (PDT)
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 3517C120047
 for <quic-issues@ietf.org>; Fri,  4 May 2018 05:40:29 -0700 (PDT)
Date: Fri, 04 May 2018 05:40:28 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
 s=pf2014; t=1525437628;
 bh=+wbgi5zcW/uWSdmsI7leKyFxCd+3E/Mvj9HXWgfOQ8M=;
 h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
 List-Archive:List-Post:List-Unsubscribe:From;
 b=trViEvnA5HhFxy9WPlWrQIorzMOK5SqutIVTWjjMUIBwV15DjKj9GI5KKRLDRqCNO
 e+b1yDb0V3WgX8B/YPIQ5E3D/RA7Y6yAxXe3nUaQkymesijNLcSlNCBC7cx7Jsz69P
 O/RtSBjuvs8jtKUTHt3ycdW30Eyqq+HxBiqOicUo=
From: Lars Eggert <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab329a5cfb1cf57f317f76f2994f6f0e2f860a8bbd92cf00000001170416bc92a169ce131475f5@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/386588885@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_5aec54bc55314_255d2aff7ea0cf503198bf";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: larseggert
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/pB1KCHtFLQozaIbuvBMp4Yre5cs>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 04 May 2018 12:40:31 -0000


----==_mimepart_5aec54bc55314_255d2aff7ea0cf503198bf
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Regarding "when you expect the 4-tuple to identify the connection" - what do you do if you have omitted the CID for a connection, but that expectation ends up being wrong?

Not being able to accept additional connections on a 4-tuple (with non-omitted CIDs) IMO severely limits the possibility to use omitted CIDs, to the point where we might as well ditch them completely.

-- 
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-386588885
----==_mimepart_5aec54bc55314_255d2aff7ea0cf503198bf
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>Regarding "when you expect the 4-tuple to identify the connection" - w=
hat do you do if you have omitted the CID for a connection, but that expe=
ctation ends up being wrong?</p>
<p>Not being able to accept additional connections on a 4-tuple (with non=
-omitted CIDs) IMO severely limits the possibility to use omitted CIDs, t=
o the point where we might as well ditch them completely.</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-386588885">view it on GitHub</a>,=
 or <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkqz7H=
2thSeL4jL8tVF6ABSzOzubHzks5tvEw8gaJpZM4Tx5-h">mute the thread</a>.<img sr=
c=3D"https://github.com/notifications/beacon/AWbkqwsMJswfnUxEMrWZsUu63k0o=
NBECks5tvEw8gaJpZM4Tx5-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-386588885"></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":"@larseggert in=
 #1336: Regarding \"when you expect the 4-tuple to identify the connectio=
n\" - what do you do if you have omitted the CID for a connection, but th=
at expectation ends up being wrong?\r\n\r\nNot being able to accept addit=
ional connections on a 4-tuple (with non-omitted CIDs) IMO severely limit=
s the possibility to use omitted CIDs, to the point where we might as wel=
l ditch them completely."}],"action":{"name":"View Issue","url":"https://=
github.com/quicwg/base-drafts/issues/1336#issuecomment-386588885"}}}</scr=
ipt>=

----==_mimepart_5aec54bc55314_255d2aff7ea0cf503198bf--

