Date: Wed, 17 Apr 2019 14:09:20 +0000 (UTC)
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4abe894568fd09de4918cfcf865964f58150c8ac4c392cebac4660f92a169ce19e2f635@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2629@github.com>
Subject: [quicwg/base-drafts] H3 GOAWAY guidance still refers to MAX_STREAM_ID
 (#2629)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5cb7338f8aaee_44293fd2970cd95c540226";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/lLF-bR4tXhilH5OOC2MPGWYDTj0>

----==_mimepart_5cb7338f8aaee_44293fd2970cd95c540226
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

So a while back @lnicco pointed out on #1717 that GOAWAY guidance wasn't great, and @MikeBishop fixed this with nice prose in #1712. This is presently located in https://tools.ietf.org/html/draft-ietf-quic-http-19#section-6.2

In the meantime, the transport has replaced `MAX_STREAM_ID` with `MAX_STREAMS`. The guidance for connection clousure is now a little stale and needs an update.

My one question is: if a server advertises `initial_max_streams_bidi` TP as 1, it processes one request on stream 0 and sends GOAWAY, is it expected that the GOAWAY contains a `stream_id` value of 4? NB: stream 4 was never a valid client-initiated bidirectional stream.

-- 
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/2629
----==_mimepart_5cb7338f8aaee_44293fd2970cd95c540226
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>So a while back <a class=3D"user-mention" data-hovercard-type=3D"user" d=
ata-hovercard-url=3D"/hovercards?user_id=3D54891" data-octo-click=3D"hoverc=
ard-link-click" data-octo-dimensions=3D"link_type:self" href=3D"https://git=
hub.com/lnicco">@lnicco</a> pointed out on <a class=3D"issue-link js-issue-=
link" data-error-text=3D"Failed to load issue title" data-id=3D"355395993" =
data-permission-text=3D"Issue title is private" data-url=3D"https://github.=
com/quicwg/base-drafts/issues/1717" data-hovercard-type=3D"issue" data-hove=
rcard-url=3D"/quicwg/base-drafts/issues/1717/hovercard" href=3D"https://git=
hub.com/quicwg/base-drafts/issues/1717">#1717</a> that GOAWAY guidance wasn=
't great, and <a class=3D"user-mention" data-hovercard-type=3D"user" data-h=
overcard-url=3D"/hovercards?user_id=3D4273797" data-octo-click=3D"hovercard=
-link-click" data-octo-dimensions=3D"link_type:self" href=3D"https://github=
.com/MikeBishop">@MikeBishop</a> fixed this with nice prose in <a class=3D"=
issue-link js-issue-link" data-error-text=3D"Failed to load issue title" da=
ta-id=3D"354864827" data-permission-text=3D"Issue title is private" data-ur=
l=3D"https://github.com/quicwg/base-drafts/issues/1712" data-hovercard-type=
=3D"pull_request" data-hovercard-url=3D"/quicwg/base-drafts/pull/1712/hover=
card" href=3D"https://github.com/quicwg/base-drafts/pull/1712">#1712</a>. T=
his is presently located in <a href=3D"https://tools.ietf.org/html/draft-ie=
tf-quic-http-19#section-6.2" rel=3D"nofollow">https://tools.ietf.org/html/d=
raft-ietf-quic-http-19#section-6.2</a></p>
<p>In the meantime, the transport has replaced <code>MAX_STREAM_ID</code> w=
ith <code>MAX_STREAMS</code>. The guidance for connection clousure is now a=
 little stale and needs an update.</p>
<p>My one question is: if a server advertises <code>initial_max_streams_bid=
i</code> TP as 1, it processes one request on stream 0 and sends GOAWAY, is=
 it expected that the GOAWAY contains a <code>stream_id</code> value of 4? =
NB: stream 4 was never a valid client-initiated bidirectional stream.</p>

<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/2629">view it on GitHub</a>, or <a href=3D"https://github.c=
om/notifications/unsubscribe-auth/AWbkq7HUzppVrumk2h48AfVEshQSvH0Rks5vhysPg=
aJpZM4c1Joz">mute the thread</a>.<img src=3D"https://github.com/notificatio=
ns/beacon/AWbkqxpUtEMfkRpHa370lxV5TVfAAT9Gks5vhysPgaJpZM4c1Joz.gif" height=
=3D"1" width=3D"1" alt=3D"" /></p>
<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":"DESCRIPTION","message":"H3 GOAWAY gu=
idance still refers to MAX_STREAM_ID (#2629)"}],"action":{"name":"View Issu=
e","url":"https://github.com/quicwg/base-drafts/issues/2629"}}}</script>
<script type=3D"application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/2629",
"url": "https://github.com/quicwg/base-drafts/issues/2629",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>=

----==_mimepart_5cb7338f8aaee_44293fd2970cd95c540226--