Subject: [quicwg/base-drafts] MAX_STREAM_DATA is valid in the "idle" state (#483)

From: Martin Thomson <[email-masked]>
Date: Thu, 27 Apr 2017 23:01:15 -0700

Reordering might mean that this arrives ahead of time.  It would be unusual, but not unreasonably so for that to happen.

For instance, the h2 stack in Firefox sends a WINDOW_UPDATE immediately after sending a request for something it really wants.  This allows it to set the initial flow control window small, but have generous limits on important requests.  If that strategy were used, it wouldn't be unusual for the MAX_STREAM_DATA and STREAM frames to end up in different packets.

I built this on #457 because that touches the same text.

Closes #188.
You can view, comment on, or merge this pull request online at:

  https://github.com/quicwg/base-drafts/pull/483

-- Commit Summary --

  * Allow STREAM_BLOCKED on unopenable streams
  * MAX_STREAM_DATA might arrive on an idle stream

-- File Changes --

    M draft-ietf-quic-transport.md (20)

-- Patch Links --

https://github.com/quicwg/base-drafts/pull/483.patch
https://github.com/quicwg/base-drafts/pull/483.diff

-- 
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/483