Date: Mon, 04 Feb 2019 23:07:08 +0000 (UTC)
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab17474aaf97b9c13a202c41cefcf719fd20730b6292cf000000011870879c92a169ce183b427c@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2412/460449754@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2412@github.com>
References: <quicwg/base-drafts/issues/2412@github.com>
Subject: Re: [quicwg/base-drafts] MAX_PUSH_ID: lower-than-previous value conn
 error seems too severe (#2412)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5c58c59c73545_2e703fb1b44d45b83654d5";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/u0-3_qP7Km6ZgUh_iC7_I7ybHfc>

----==_mimepart_5c58c59c73545_2e703fb1b44d45b83654d5
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I see your point of view. The downside is that the client application layer=
 needs to coordinate its sending of this frame to ensure the sequence is st=
rictly growing - this constrains some of the design choices an implementati=
on might choose to make. =0D
=0D
I question the severity because I don't know why a server would get so upse=
t by seeing a value that is smaller than it had before. If the server is at=
 the current max streams amount, it is unable to generate pushes until some=
thing increases the max. What could possibly go wrong? =E2=84=A2=EF=B8=8F I=
 don't want to fall into the trap of justifying ever decision but this one =
is not resonating with me probably because I am missing something.=0D
=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/2412#issuecomment-460449754=

----==_mimepart_5c58c59c73545_2e703fb1b44d45b83654d5
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>I see your point of view. The downside is that the client application la=
yer needs to coordinate its sending of this frame to ensure the sequence is=
 strictly growing - this constrains some of the design choices an implement=
ation might choose to make.</p>=0D
<p>I question the severity because I don't know why a server would get so u=
pset by seeing a value that is smaller than it had before. If the server is=
 at the current max streams amount, it is unable to generate pushes until s=
omething increases the max. What could possibly go wrong? <g-emoji class=3D=
"g-emoji" alias=3D"tm" fallback-src=3D"https://github.githubassets.com/imag=
es/icons/emoji/unicode/2122.png">=E2=84=A2=EF=B8=8F</g-emoji> I don't want =
to fall into the trap of justifying ever decision but this one is not reson=
ating with me probably because I am missing something.</p>=0D
=0D
<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&mda=
sh;<br />You are receiving this because you are subscribed to this thread.<=
br />Reply to this email directly, <a href=3D"https://github.com/quicwg/bas=
e-drafts/issues/2412#issuecomment-460449754">view it on GitHub</a>, or <a h=
ref=3D"https://github.com/notifications/unsubscribe-auth/AWbkq5KArdmYb-ExAM=
YmvFuWifTYVhp_ks5vKL0cgaJpZM4aiHsa">mute the thread</a>.<img src=3D"https:/=
/github.com/notifications/beacon/AWbkqwVF9be5gfesFPbKD1RPC3DTwU_gks5vKL0cga=
JpZM4aiHsa.gif" height=3D"1" width=3D"1" alt=3D"" /></p>=0D
<script type=3D"application/json" data-scope=3D"inboxmarkup">{"api_version"=
:"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"Gi=
tHub"},"entity":{"external_key":"github/quicwg/base-drafts","title":"quicwg=
/base-drafts","subtitle":"GitHub repository","main_image_url":"https://gith=
ub.githubassets.com/images/email/message_cards/header.png","avatar_image_ur=
l":"https://github.githubassets.com/images/email/message_cards/avatar.png",=
"action":{"name":"Open in GitHub","url":"https://github.com/quicwg/base-dra=
fts"}},"updates":{"snippets":[{"icon":"PERSON","message":"@LPardue in #2412=
: I see your point of view. The downside is that the client application lay=
er needs to coordinate its sending of this frame to ensure the sequence is =
strictly growing - this constrains some of the design choices an implementa=
tion might choose to make. \r\n\r\nI question the severity because I don't =
know why a server would get so upset by seeing a value that is smaller than=
 it had before. If the server is at the current max streams amount, it is u=
nable to generate pushes until something increases the max. What could poss=
ibly go wrong? =E2=84=A2=EF=B8=8F I don't want to fall into the trap of jus=
tifying ever decision but this one is not resonating with me probably becau=
se I am missing something.\r\n"}],"action":{"name":"View Issue","url":"http=
s://github.com/quicwg/base-drafts/issues/2412#issuecomment-460449754"}}}</s=
cript>=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/2412#issuecomment-4=
60449754",=0D
"url": "https://github.com/quicwg/base-drafts/issues/2412#issuecomment-4604=
49754",=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_5c58c59c73545_2e703fb1b44d45b83654d5--