Date: Thu, 07 Nov 2019 12:42:27 -0800
From: Eric Kinnear <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJKZ5FJSW7ATFHDAWXZ532G2DHEVBNHHB5Y6ONQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3193/551254796@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3193@github.com>
References: <quicwg/base-drafts/issues/3193@github.com>
Subject: Re: [quicwg/base-drafts] active_connection_id_limit interacts poorly
 with Retire Prior To (#3193)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5dc481b3beed_22f3fcc1b4cd96c1280af";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/DL5Q8dcyHnC46KWdm2vBTG9kJhE>


----==_mimepart_5dc481b3beed_22f3fcc1b4cd96c1280af
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

There definitely was a reason we avoided making this a strict requirement=
, and I think this played into it, but this is the benefit of having RPT =
delivered in the same frame that delivers a new one. =0D
=0D
Perhaps modify the text to indicate that the error is if the limit is exc=
eeded after retiring any in RPT?=0D
=0D
Or even some non-normative text along the lines of =E2=80=9CIf RPT retire=
s all outstanding CIDS, immediately start sending new packets with the ne=
w CID and make sure you only check the limit after retiring any indicated=
 in RPT=E2=80=9D? =0D
=0D
On one hand, it=E2=80=99s kind of an annoying thing to keep track of. But=
 on the other, making it a hard requirement does decently simplify a lot =
of other scenarios. =0D
=0D
That said, we should probably go dig up the other reasons we avoided this=
 the first time around. =0D
=0D
-- =0D
You are receiving this because you are subscribed to this thread.=0D
Reply to this email directly or view it on GitHub:=0D
https://github.com/quicwg/base-drafts/issues/3193#issuecomment-551254796=

----==_mimepart_5dc481b3beed_22f3fcc1b4cd96c1280af
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>There definitely was a reason we avoided making this a strict requirem=
ent, and I think this played into it, but this is the benefit of having R=
PT delivered in the same frame that delivers a new one.</p>=0D
<p>Perhaps modify the text to indicate that the error is if the limit is =
exceeded after retiring any in RPT?</p>=0D
<p>Or even some non-normative text along the lines of =E2=80=9CIf RPT ret=
ires all outstanding CIDS, immediately start sending new packets with the=
 new CID and make sure you only check the limit after retiring any indica=
ted in RPT=E2=80=9D?</p>=0D
<p>On one hand, it=E2=80=99s kind of an annoying thing to keep track of. =
But on the other, making it a hard requirement does decently simplify a l=
ot of other scenarios.</p>=0D
<p>That said, we should probably go dig up the other reasons we avoided t=
his the first time around.</p>=0D
=0D
<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/3193?email_source=3Dnotifications&amp;email_token=3D=
AFTOJK4XJ4DOJNUKVEX4KB3QSR4THA5CNFSM4JJPZITKYY3PNVWWK3TUL52HS4DFVREXG43VM=
VBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDNXWDA#issuecomment-551254796">view it on=
 GitHub</a>, or <a href=3D"https://github.com/notifications/unsubscribe-a=
uth/AFTOJK6YPA2LCLPZSV6SBFTQSR4THANCNFSM4JJPZITA">unsubscribe</a>.<img sr=
c=3D"https://github.com/notifications/beacon/AFTOJKZRRPH7RQ6GBJOVTSDQSR4T=
HA5CNFSM4JJPZITKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWS=
ZGOEDNXWDA.gif" height=3D"1" width=3D"1" alt=3D"" /></p>=0D
<script type=3D"application/ld+json">[=0D
{=0D
"@context": "http://schema.org",=0D
"@type": "EmailMessage",=0D
"potentialAction": {=0D
"@type": "ViewAction",=0D
"target": "https://github.com/quicwg/base-drafts/issues/3193?email_source=
=3Dnotifications\u0026email_token=3DAFTOJK4XJ4DOJNUKVEX4KB3QSR4THA5CNFSM4=
JJPZITKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDNXWD=
A#issuecomment-551254796",=0D
"url": "https://github.com/quicwg/base-drafts/issues/3193?email_source=3D=
notifications\u0026email_token=3DAFTOJK4XJ4DOJNUKVEX4KB3QSR4THA5CNFSM4JJP=
ZITKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDNXWDA#i=
ssuecomment-551254796",=0D
"name": "View Issue"=0D
},=0D
"description": "View this Issue on GitHub",=0D
"publisher": {=0D
"@type": "Organization",=0D
"name": "GitHub",=0D
"url": "https://github.com"=0D
}=0D
}=0D
]</script>=

----==_mimepart_5dc481b3beed_22f3fcc1b4cd96c1280af--