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 AB029129A87
 for <quic-issues@ietfa.amsl.com>; Mon,  4 Feb 2019 15:48:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.552
X-Spam-Level: 
X-Spam-Status: No, score=-12.552 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1,
 DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001,
 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 2XuSJq1z1trX for <quic-issues@ietfa.amsl.com>;
 Mon,  4 Feb 2019 15:48:15 -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 965E71294FA
 for <quic-issues@ietf.org>; Mon,  4 Feb 2019 15:48:15 -0800 (PST)
Date: Mon, 04 Feb 2019 15:48:14 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
 s=pf2014; t=1549324094;
 bh=BOQiNftrCDEXXAZkcHWtFWrXp4etdDmksmPwX7Sv2WQ=;
 h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
 List-Archive:List-Post:List-Unsubscribe:From;
 b=vRmTNgxWZkYAaza2OTbOLCHnFubd1UGSVieBIzuasja0UVwTj6KyPrcn1F1qT7xtd
 /VfYxBellEOOyvJnnWyO0QEHjA2US0Uv3Lhy8CzqIXYUYUU5BV/WfSfV+3nygW7Ubd
 LsUUErS1zw9Cou3Pe0lJL2bSlIInvFHuVbXY1xg4=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab4de1ca5c18e3e3af9fc8e2d43ce940e52f83facd92cf000000011870913e92a169ce183ba2c6@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2413/460459352@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2413@github.com>
References: <quicwg/base-drafts/issues/2413@github.com>
Subject: Re: [quicwg/base-drafts] Mandate using a new connection ID on
 migration (#2413)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5c58cf3e959f0_768d3fcba32d45c097163";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/Si51xKY-EoVwWb3_61eSBkXw-lk>
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: Mon, 04 Feb 2019 23:48:18 -0000


----==_mimepart_5c58cf3e959f0_768d3fcba32d45c097163
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Thanks for finding that @erickinnear.  That supports the change being editorial-only.

As for the perceived conflict, yeah, the text is not ideal.  I'll find some way to reword it.  Perhaps by observing that you can never run out of zero-length connection IDs.

@igorlord, allowing a peer to exhaust connection IDs to maintain linkability across migrations is an attack that I'd rather we not have.

-- 
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/2413#issuecomment-460459352
----==_mimepart_5c58cf3e959f0_768d3fcba32d45c097163
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>Thanks for finding that <a class=3D"user-mention" data-hovercard-type=3D=
"user" data-hovercard-url=3D"/hovercards?user_id=3D32474881" data-octo-cl=
ick=3D"hovercard-link-click" data-octo-dimensions=3D"link_type:self" href=
=3D"https://github.com/erickinnear">@erickinnear</a>.  That supports the =
change being editorial-only.</p>
<p>As for the perceived conflict, yeah, the text is not ideal.  I'll find=
 some way to reword it.  Perhaps by observing that you can never run out =
of zero-length connection IDs.</p>
<p><a class=3D"user-mention" data-hovercard-type=3D"user" data-hovercard-=
url=3D"/hovercards?user_id=3D25256216" data-octo-click=3D"hovercard-link-=
click" data-octo-dimensions=3D"link_type:self" href=3D"https://github.com=
/igorlord">@igorlord</a>, allowing a peer to exhaust connection IDs to ma=
intain linkability across migrations is an attack that I'd rather we not =
have.</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/2413#issuecomment-460459352">view it on GitHub</a>,=
 or <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkq2TA=
ds0J5Q88ucbKDz3HDm2MJkoKks5vKMa-gaJpZM4aiOuh">mute the thread</a>.<img sr=
c=3D"https://github.com/notifications/beacon/AWbkq8PHP5eAJ0wb5IlgJTd53ry-=
7mStks5vKMa-gaJpZM4aiOuh.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":"@=
martinthomson in #2413: Thanks for finding that @erickinnear.  That suppo=
rts the change being editorial-only.\r\n\r\nAs for the perceived conflict=
, yeah, the text is not ideal.  I'll find some way to reword it.  Perhaps=
 by observing that you can never run out of zero-length connection IDs.\r=
\n\r\n@igorlord, allowing a peer to exhaust connection IDs to maintain li=
nkability across migrations is an attack that I'd rather we not have."}],=
"action":{"name":"View Issue","url":"https://github.com/quicwg/base-draft=
s/issues/2413#issuecomment-460459352"}}}</script>
<script type=3D"application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/2413#issuecomment=
-460459352",
"url": "https://github.com/quicwg/base-drafts/issues/2413#issuecomment-46=
0459352",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>=

----==_mimepart_5c58cf3e959f0_768d3fcba32d45c097163--

