W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2019

Re: Shouldn't we add a new CLOSING state in H2 ?

From: Patrick McManus <mcmanus@ducksong.com>
Date: Sat, 26 Jan 2019 17:29:16 -0500
Message-ID: <CAOdDvNr=w6+Vi5kekYzswi4kVUCwoWYgHjMc5gnz3aLaryEHtQ@mail.gmail.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
On Sat, Jan 26, 2019 at 4:47 PM Martin Thomson <mt@lowentropy.net> wrote:

> On Sat, Jan 26, 2019, at 08:04, Patrick McManus wrote:
> > 3] wait for h3 where this little tcp artifact of intentionally losing
> data
> > is not an issue.
>
> h3 won't solve this issue.  At least not given its current design.


Perhaps you are looking at a broader issue than I am (and thought was what
wily was describing).. I was specifically referring to the pattern that
forces the RST when tcp data hits the closed connection which in return
forces the truncation and dropping of buffered valid recvd (even ack'd)
data on the client.. That should go away (ha) in h3, no?
Received on Saturday, 26 January 2019 22:29:52 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 26 January 2019 22:29:54 UTC