Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

MAX_STREAM_DATA to replace LIMIT_UPDATE #486

Closed
mikkelfj opened this issue Apr 28, 2017 · 0 comments
Closed

MAX_STREAM_DATA to replace LIMIT_UPDATE #486

mikkelfj opened this issue Apr 28, 2017 · 0 comments
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.

Comments

@mikkelfj
Copy link
Contributor

10.3. Stream Concurrency

A receiver MUST NOT renege on an advertisement; that is, once a receiver advertises a stream ID via a LIMIT_UPDATE frame, it MUST NOT subsequently advertise a smaller maximum ID. A sender may receive LIMIT_UPDATE frames out of order; a sender MUST therefore ignore any LIMIT_UPDATE that does not increase the maximum.
@janaiyengar janaiyengar mentioned this issue Apr 28, 2017
Merged
@mnot mnot added editorial An issue that does not affect the design of the protocol; does not require consensus. -transport labels May 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mnot @mikkelfj