RE: sending WINDOW_UPDATE when in reserved (remote)

I’d say reserved (local) needs updating.  Once you know what the server is sending you, you’ll reasonably be able to give it window to keep sending.

From: Patrick McManus [mailto:pmcmanus@mozilla.com]
Sent: Thursday, October 23, 2014 12:47 PM
To: HTTP Working Group
Subject: sending WINDOW_UPDATE when in reserved (remote)

Hi All.
Firefox receives a PUSH_PROMISE  from node-http2 (speaking -14). That puts Firefox into reserved-remote and node into reserved-local.
Firefox sends a WINDOW_UPDATE on that stream and node replies with GOAWAY Protocol-Error
Section 5.1 of -14 has this to say:
reserved (local): [..]

A PRIORITY<http://http2.github.io/http2-spec/index.html#PRIORITY> frame MAY be received in this state. Receiving any type of frame other than RST_STREAM<http://http2.github.io/http2-spec/index.html#RST_STREAM> or PRIORITY<http://http2.github.io/http2-spec/index.html#PRIORITY> on a stream in this state MUST be treated as a connection error (Section 5.4.1<http://http2.github.io/http2-spec/index.html#ConnectionErrorHandler>) of type PROTOCOL_ERROR<http://http2.github.io/http2-spec/index.html#PROTOCOL_ERROR>.

point to node! However it also has this to say:
reserved (remote): [..]

An endpoint MAY send a PRIORITY<http://http2.github.io/http2-spec/index.html#PRIORITY> frame in this state to reprioritize the reserved stream. An endpoint MUST NOT send any type of frame other than RST_STREAM<http://http2.github.io/http2-spec/index.html#RST_STREAM>, WINDOW_UPDATE<http://http2.github.io/http2-spec/index.html#WINDOW_UPDATE>, or PRIORITY<http://http2.github.io/http2-spec/index.html#PRIORITY> in this state.

point to firefox! We're all winners here.

Which state should be changed?

-Patrick