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.

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

RST_STREAM / GOAWAY opaque data #17

Closed
mnot opened this issue Feb 18, 2013 · 3 comments
Closed

RST_STREAM / GOAWAY opaque data #17

mnot opened this issue Feb 18, 2013 · 3 comments

Comments

@mnot
Copy link
Member

@mnot mnot commented Feb 18, 2013

In Tokyo, there was discussion of whether it would be useful to allow opaque data in RST_STREAM and GOAWAY. Waiting for a full proposal.

@jasnell
Copy link
Contributor

@jasnell jasnell commented Jun 12, 2013

I believe the default for these ought to be not to include opaque data, however, a frame specific flag could be used to indicate additional data. e.g. add an ADDITIONAL_DATA (0x2) flag. If the flag is not set, additional data is ignored or treated like a protocol error.

@willchan
Copy link
Contributor

@willchan willchan commented Jun 12, 2013

I think it'd be useful to allow opaque data. I'm not going to bother fighting for my bike shed color, but if I were to pick, I'd just use the length field. I don't think a flag really gains us anything, except more cases in our code that need to be specified as ignored/error.

@ghost ghost assigned martinthomson Jun 13, 2013
@mnot
Copy link
Member Author

@mnot mnot commented Jun 13, 2013

Discussed at SF Interim; will put into implementation draft but mark AT RISK. Hasan to help with text.

@mnot mnot closed this Jul 31, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants