Date: Fri, 08 Sep 2017 14:32:24 +0000 (UTC)
From: martinduke <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4abce97d204517bc086b1418c03c72a0dab05b77b1f92cf0000000115ca6bf792a169ce0f025d79@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/743/328119244@github.com>
In-Reply-To: <quicwg/base-drafts/issues/743@github.com>
References: <quicwg/base-drafts/issues/743@github.com>
Subject: Re: [quicwg/base-drafts] Stream closed state and acknowledgments
 (#743)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_59b2a9f7386fe_18223f7e91fc1c38552c2";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/2aH7xWBsgPzffFwUenMDBP4d8eU>

----==_mimepart_59b2a9f7386fe_18223f7e91fc1c38552c2
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

I think the stream should remain open until full acknowledgment, for two reasons. One, per #765 the logical place to put in flight data is in the stream data structure, so I have to keep it around.

Two, a QUIC stream has roughly the semantics of a TCP close and it would be nice to adhere to those norms.

But I concede that it isn't a big deal either way.

-- 
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/743#issuecomment-328119244
----==_mimepart_59b2a9f7386fe_18223f7e91fc1c38552c2
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>I think the stream should remain open until full acknowledgment, for two=
 reasons. One, per <a href=3D"https://github.com/quicwg/base-drafts/issues/=
765" class=3D"issue-link js-issue-link" data-url=3D"https://github.com/quic=
wg/base-drafts/issues/765" data-id=3D"255754536" data-error-text=3D"Failed =
to load issue title" data-permission-text=3D"Issue title is private">#765</=
a> the logical place to put in flight data is in the stream data structure,=
 so I have to keep it around.</p>
<p>Two, a QUIC stream has roughly the semantics of a TCP close and it would=
 be nice to adhere to those norms.</p>
<p>But I concede that it isn't a big deal either way.</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/743#issuecomment-328119244">view it on GitHub</a>, or <a hr=
ef=3D"https://github.com/notifications/unsubscribe-auth/AWbkq-UmiSvDXXbRVYR=
AUiPnuYh2InqJks5sgU_3gaJpZM4O-AeX">mute the thread</a>.<img alt=3D"" height=
=3D"1" src=3D"https://github.com/notifications/beacon/AWbkqzoILZ5epSKk6DBxk=
fudwXOc1D5fks5sgU_3gaJpZM4O-AeX.gif" width=3D"1" /></p>
<div itemscope itemtype=3D"http://schema.org/EmailMessage">
<div itemprop=3D"action" itemscope itemtype=3D"http://schema.org/ViewAction=
">
  <link itemprop=3D"url" href=3D"https://github.com/quicwg/base-drafts/issu=
es/743#issuecomment-328119244"></link>
  <meta itemprop=3D"name" content=3D"View Issue"></meta>
</div>
<meta itemprop=3D"description" content=3D"View this Issue on GitHub"></meta>
</div>

<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://clou=
d.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290=
892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/asset=
s/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name=
":"Open in GitHub","url":"https://github.com/quicwg/base-drafts"}},"updates=
":{"snippets":[{"icon":"PERSON","message":"@martinduke in #743: I think the=
 stream should remain open until full acknowledgment, for two reasons. One,=
 per #765 the logical place to put in flight data is in the stream data str=
ucture, so I have to keep it around.\r\n\r\nTwo, a QUIC stream has roughly =
the semantics of a TCP close and it would be nice to adhere to those norms.=
\r\n\r\nBut I concede that it isn't a big deal either way."}],"action":{"na=
me":"View Issue","url":"https://github.com/quicwg/base-drafts/issues/743#is=
suecomment-328119244"}}}</script>=

----==_mimepart_59b2a9f7386fe_18223f7e91fc1c38552c2--