Date: Sun, 30 Dec 2018 20:55:53 -0800
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4abf3025235af7b2599767be25e88a94f500d1741e592cf000000011841635992a169ce17792cde@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2253/450608362@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2253@github.com>
References: <quicwg/base-drafts/issues/2253@github.com>
Subject: Re: [quicwg/base-drafts] Consider making h3 frame types varint (#2253)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5c29a159ceabf_715f3f817f2d45c01456c9";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/JftPrgeS3zFaYedU5l2awoEVfWU>


----==_mimepart_5c29a159ceabf_715f3f817f2d45c01456c9
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

>> The request headers of a context-push cannot be sent in a way that a client (that does not understand the extension) can ignore.
> 
> I don't think that is true. If you assume that this is a QPACK-encoded header block, that would be true (because it would create an expectation of acknowledgment), but you don't need to use QPACK.

Maybe I should have pointed out that push streams start with a Push ID, however if a server has a usable Push ID is not determined until it receives a MAX_PUSH_ID frame from the client. Doesn't sending a push stream in 0.5 RTT violate that requirement?

-- 
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/2253#issuecomment-450608362
----==_mimepart_5c29a159ceabf_715f3f817f2d45c01456c9
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<blockquote>
<blockquote>
<p>The request headers of a context-push cannot be sent in a way that a c=
lient (that does not understand the extension) can ignore.</p>
</blockquote>
<p>I don't think that is true. If you assume that this is a QPACK-encoded=
 header block, that would be true (because it would create an expectation=
 of acknowledgment), but you don't need to use QPACK.</p>
</blockquote>
<p>Maybe I should have pointed out that push streams start with a Push ID=
, however if a server has a usable Push ID is not determined until it rec=
eives a MAX_PUSH_ID frame from the client. Doesn't sending a push stream =
in 0.5 RTT violate that requirement?</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/2253#issuecomment-450608362">view it on GitHub</a>,=
 or <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkq1-0=
9EXFjm5MmuCR1pYhmmzsjnHUks5u-ZjZgaJpZM4ZgKQr">mute the thread</a>.<img sr=
c=3D"https://github.com/notifications/beacon/AWbkqwZIU6skb7lhDxT-9F9VZ3AF=
0APwks5u-ZjZgaJpZM4ZgKQr.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":"@=
kazuho in #2253: \u003e\u003e The request headers of a context-push canno=
t be sent in a way that a client (that does not understand the extension)=
 can ignore.\r\n\u003e \r\n\u003e I don't think that is true. If you assu=
me that this is a QPACK-encoded header block, that would be true (because=
 it would create an expectation of acknowledgment), but you don't need to=
 use QPACK.\r\n\r\nMaybe I should have pointed out that push streams star=
t with a Push ID, however if a server has a usable Push ID is not determi=
ned until it receives a MAX_PUSH_ID frame from the client. Doesn't sendin=
g a push stream in 0.5 RTT violate that requirement?"}],"action":{"name":=
"View Issue","url":"https://github.com/quicwg/base-drafts/issues/2253#iss=
uecomment-450608362"}}}</script>
<script type=3D"application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/2253#issuecomment=
-450608362",
"url": "https://github.com/quicwg/base-drafts/issues/2253#issuecomment-45=
0608362",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>=

----==_mimepart_5c29a159ceabf_715f3f817f2d45c01456c9--