Skip to content

Commit

Permalink
Mentional receiver-initiated once more
Browse files Browse the repository at this point in the history
  • Loading branch information
martinthomson committed Mar 22, 2015
1 parent 989a362 commit 3832f62
Showing 1 changed file with 8 additions and 8 deletions.
16 changes: 8 additions & 8 deletions draft-ietf-httpbis-http2.xml
Original file line number Diff line number Diff line change
Expand Up @@ -2449,14 +2449,14 @@ HTTP2-Settings = token68
</t>

<t>
After sending a GOAWAY frame, the sender can discard frames for streams with identifiers
higher than the identified last stream. However, any frames that alter connection state
cannot be completely ignored. For instance, <x:ref>HEADERS</x:ref>,
<x:ref>PUSH_PROMISE</x:ref> and <x:ref>CONTINUATION</x:ref> frames MUST be minimally
processed to ensure the state maintained for header compression is consistent (see <xref
target="HeaderBlock"/>); similarly DATA frames MUST be counted toward the connection flow
control window. Failure to process these frames can cause flow control or header
compression state to become unsynchronized.
After sending a GOAWAY frame, the sender can discard frames for streams initiated by the
receiver with identifiers higher than the identified last stream. However, any frames
that alter connection state cannot be completely ignored. For instance,
<x:ref>HEADERS</x:ref>, <x:ref>PUSH_PROMISE</x:ref> and <x:ref>CONTINUATION</x:ref> frames
MUST be minimally processed to ensure the state maintained for header compression is
consistent (see <xref target="HeaderBlock"/>); similarly DATA frames MUST be counted
toward the connection flow control window. Failure to process these frames can cause flow
control or header compression state to become unsynchronized.
</t>

<t>
Expand Down

0 comments on commit 3832f62

Please sign in to comment.