Date: Fri, 08 Feb 2019 23:19:49 -0800
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab2492d09da7655beb9796b335b45007bcacbac3a992cf000000011876411592a169ce184b1573@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2436/462021395@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2436@github.com>
References: <quicwg/base-drafts/issues/2436@github.com>
Subject: Re: [quicwg/base-drafts] rate-limiting of CID issuance needs to be
 allowed (#2436)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5c5e7f151aadb_44533ff5636d45b471438";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/4hL7JzteO4TWEfqQiNmwy817ppc>


----==_mimepart_5c5e7f151aadb_44533ff5636d45b471438
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

> The proposal does not mandate such behavior. It's merely clarifying that such behavior is permissible.

I was concerned that you wanted to make it a requirement. Anyway, I'd also like that behaviour is reasonable predictable so app protocols don't have too many constraints on deployments. A stack used for HTTP might well be used for other things.

I'm still wondering if there are benefits to rotating CID's when not migrating, but I think there is since you might want to refresh routing tables. This is starting to be a separate, but related issue, but one thing is rate limiting, the other is convincing peer to rotate or not rotate within a given time frame, with no migration. I'd be best if transport could take the guesswork out of this.

Overall, I could see a requirement to rotate daily and requirement to supply a min count of CID's daily, just to ensure all entities, including middle boxes have something to work from.

-- 
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/2436#issuecomment-462021395
----==_mimepart_5c5e7f151aadb_44533ff5636d45b471438
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<blockquote>
<p>The proposal does not mandate such behavior. It's merely clarifying th=
at such behavior is permissible.</p>
</blockquote>
<p>I was concerned that you wanted to make it a requirement. Anyway, I'd =
also like that behaviour is reasonable predictable so app protocols don't=
 have too many constraints on deployments. A stack used for HTTP might we=
ll be used for other things.</p>
<p>I'm still wondering if there are benefits to rotating CID's when not m=
igrating, but I think there is since you might want to refresh routing ta=
bles. This is starting to be a separate, but related issue, but one thing=
 is rate limiting, the other is convincing peer to rotate or not rotate w=
ithin a given time frame, with no migration. I'd be best if transport cou=
ld take the guesswork out of this.</p>
<p>Overall, I could see a requirement to rotate daily and requirement to =
supply a min count of CID's daily, just to ensure all entities, including=
 middle boxes have something to work from.</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/2436#issuecomment-462021395">view it on GitHub</a>,=
 or <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkqwWN=
Xbj7VlDKeA35AkRKHmkyU_kAks5vLnaVgaJpZM4amvqj">mute the thread</a>.<img sr=
c=3D"https://github.com/notifications/beacon/AWbkqwEUnwSn2FC7sLvnfbCmpJiB=
xCpMks5vLnaVgaJpZM4amvqj.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":"@=
mikkelfj in #2436: \u003e The proposal does not mandate such behavior. It=
's merely clarifying that such behavior is permissible.\r\n\r\nI was conc=
erned that you wanted to make it a requirement. Anyway, I'd also like tha=
t behaviour is reasonable predictable so app protocols don't have too man=
y constraints on deployments. A stack used for HTTP might well be used fo=
r other things.\r\n\r\nI'm still wondering if there are benefits to rotat=
ing CID's when not migrating, but I think there is since you might want t=
o refresh routing tables. This is starting to be a separate, but related =
issue, but one thing is rate limiting, the other is convincing peer to ro=
tate or not rotate within a given time frame, with no migration. I'd be b=
est if transport could take the guesswork out of this.\r\n\r\nOverall, I =
could see a requirement to rotate daily and requirement to supply a min c=
ount of CID's daily, just to ensure all entities, including middle boxes =
have something to work from."}],"action":{"name":"View Issue","url":"http=
s://github.com/quicwg/base-drafts/issues/2436#issuecomment-462021395"}}}<=
/script>
<script type=3D"application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/2436#issuecomment=
-462021395",
"url": "https://github.com/quicwg/base-drafts/issues/2436#issuecomment-46=
2021395",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>=

----==_mimepart_5c5e7f151aadb_44533ff5636d45b471438--