- From: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Date: Mon, 21 Jul 2014 08:07:08 +0000
- To: Martin Thomson <martin.thomson@gmail.com>
- cc: Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
In message <CABkgnnVbn7LYmbB3y=FxxhsnVAtvXjJ5+iZj4QKpWCftocn-eQ@mail.gmail.com> , Martin Thomson writes: >As I already said, I don't see any need. Desync ends pretty quickly with a >GoAway. The question is if we should do something to make sure that it happens faster and with more certainty than "pretty quickly" ? Has anybody tried to do a fuzzer-test to see how robust their implementation is for an almost correctly working peer ? >> <https://github.com/http2/http2-spec/issues/555> >> >> Anyone with thoughts on this? >> > Has anybody considered frame-desynchronization ? >> > >> > The framing layer has neither pattern, checksum or sequence numbers >> > to help us tell if the sender and receiver have become mis-synchronized, -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Received on Monday, 21 July 2014 08:21:00 UTC