Date: Sun, 17 Mar 2019 16:50:25 -0700
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab7d66f045e7213c15dada07b8d070340d3f5c532992cf0000000118a69f4192a169ce1926a629@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2526/473728271@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2526@github.com>
References: <quicwg/base-drafts/issues/2526@github.com>
Subject: Re: [quicwg/base-drafts] PUSH_ID as a frame (#2526)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5c8edd4164540_3ab93fc3a94d45c01920380";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/eFilsDSRSuVIi6kHfEpkwf9_K-0>


----==_mimepart_5c8edd4164540_3ab93fc3a94d45c01920380
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

> With the current text, if I receive something bogus on a push stream (after the preface) I'll have to keep the stream around (because the push stream may come out of order) waiting for a PUSH_PROMISE with that ID that may never come.

This sounds like the case @rmarx is looking at. I'd argue this is a good reason for the current design, frame processing should only take place once the PUSH_PROMISE is received. 

But I'd like to understand how framing could help avoid errors. 

-- 
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/2526#issuecomment-473728271
----==_mimepart_5c8edd4164540_3ab93fc3a94d45c01920380
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<blockquote>
<p>With the current text, if I receive something bogus on a push stream (=
after the preface) I'll have to keep the stream around (because the push =
stream may come out of order) waiting for a PUSH_PROMISE with that ID tha=
t may never come.</p>
</blockquote>
<p>This sounds like the case <a class=3D"user-mention" data-hovercard-typ=
e=3D"user" data-hovercard-url=3D"/hovercards?user_id=3D2240689" data-octo=
-click=3D"hovercard-link-click" data-octo-dimensions=3D"link_type:self" h=
ref=3D"https://github.com/rmarx">@rmarx</a> is looking at. I'd argue this=
 is a good reason for the current design, frame processing should only ta=
ke place once the PUSH_PROMISE is received.</p>
<p>But I'd like to understand how framing could help avoid errors.</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/2526#issuecomment-473728271">view it on GitHub</a>,=
 or <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkq1pS=
EmH39nHn202bByFjCaZdpEIrks5vXtTBgaJpZM4b4l6m">mute the thread</a>.<img sr=
c=3D"https://github.com/notifications/beacon/AWbkq-bMkd5jCgRDf1ki6KV2qDkg=
yjJQks5vXtTBgaJpZM4b4l6m.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":"@=
LPardue in #2526: \u003e With the current text, if I receive something bo=
gus on a push stream (after the preface) I'll have to keep the stream aro=
und (because the push stream may come out of order) waiting for a PUSH_PR=
OMISE with that ID that may never come.\r\n\r\nThis sounds like the case =
@rmarx is looking at. I'd argue this is a good reason for the current des=
ign, frame processing should only take place once the PUSH_PROMISE is rec=
eived. \r\n\r\nBut I'd like to understand how framing could help avoid er=
rors. "}],"action":{"name":"View Issue","url":"https://github.com/quicwg/=
base-drafts/issues/2526#issuecomment-473728271"}}}</script>
<script type=3D"application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/2526#issuecomment=
-473728271",
"url": "https://github.com/quicwg/base-drafts/issues/2526#issuecomment-47=
3728271",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>=

----==_mimepart_5c8edd4164540_3ab93fc3a94d45c01920380--