Date: Wed, 16 Aug 2017 00:17:52 +0000 (UTC)
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab053ffc0ac6ce5a798c5d00d05a41f9e0cecf254a92cf0000000115ab513092a169ce0ee8a0bd@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/730/c322623734@github.com>
In-Reply-To: <quicwg/base-drafts/pull/730@github.com>
References: <quicwg/base-drafts/pull/730@github.com>
Subject: Re: [quicwg/base-drafts] Change design and and FIN to flow control
 (#730)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_59938f309a23c_54a03fa2c8cc3c3811259e";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/7wzvwj5SalIsAYrs6dDOhSolPGE>

----==_mimepart_59938f309a23c_54a03fa2c8cc3c3811259e
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

I don't think we want to flow control the FIN, which works out since the FIN does not consume an offset. The text actually seems clear on this point... if you keep everything in terms of bytes, and not in terms of offsets, the text is consistent. Subodh: Do you still see a need for clarification?

-- 
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/pull/730#issuecomment-322623734
----==_mimepart_59938f309a23c_54a03fa2c8cc3c3811259e
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>I don't think we want to flow control the FIN, which works out since the=
 FIN does not consume an offset. The text actually seems clear on this poin=
t... if you keep everything in terms of bytes, and not in terms of offsets,=
 the text is consistent. Subodh: Do you still see a need for clarification?=
</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/pull/730#issuecomment-322623734">view it on GitHub</a>, or <a href=
=3D"https://github.com/notifications/unsubscribe-auth/AWbkq5Pp558qSgL-8VQ1D=
lyGXiVIUTQPks5sYjUwgaJpZM4O2yDB">mute the thread</a>.<img alt=3D"" height=
=3D"1" src=3D"https://github.com/notifications/beacon/AWbkqyJ2qhHoyLbfaQ7P6=
XiDgHaXLjx1ks5sYjUwgaJpZM4O2yDB.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/pull=
/730#issuecomment-322623734"></link>
  <meta itemprop=3D"name" content=3D"View Pull Request"></meta>
</div>
<meta itemprop=3D"description" content=3D"View this Pull Request 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":"@janaiyengar in #730: I don't th=
ink we want to flow control the FIN, which works out since the FIN does not=
 consume an offset. The text actually seems clear on this point... if you k=
eep everything in terms of bytes, and not in terms of offsets, the text is =
consistent. Subodh: Do you still see a need for clarification?"}],"action":=
{"name":"View Pull Request","url":"https://github.com/quicwg/base-drafts/pu=
ll/730#issuecomment-322623734"}}}</script>=

----==_mimepart_59938f309a23c_54a03fa2c8cc3c3811259e--