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

Frame type extensibility #233

Closed
martinthomson opened this issue Jan 25, 2017 · 3 comments
Closed

Frame type extensibility #233

martinthomson opened this issue Jan 25, 2017 · 3 comments
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.

Comments

@martinthomson
Copy link
Member

The draft currently says:

Frames of unknown types are ignored.

Which is basically impossible. The only option an endpoint has when it encounters an unknown frame type is to throw out the entire frame or terminate the connection. We should pick the latter.
@martinthomson martinthomson added design An issue that affects the design of the protocol; resolution requires consensus. -transport labels Jan 25, 2017
@ianswett
Copy link
Contributor

You're correct. That should be removed.

@martinthomson
Copy link
Member Author

martinthomson commented Jan 25, 2017 •
edited

Note that we also have #194 and #62 that might be resolved in one fell swoop. Edit: #62 isn't going to die.

@martinthomson martinthomson mentioned this issue Apr 27, 2017
Closed
@martinthomson martinthomson changed the title Unknown frame types Frame type extensibility Apr 27, 2017
@mnot mnot added this to Frames in QUIC Apr 28, 2017
@mnot mnot moved this from Packets to Reliability in QUIC Apr 28, 2017
@mnot mnot moved this from Reliability to Middleboxen in QUIC Apr 28, 2017
@mnot mnot removed this from Middleboxen in QUIC Apr 28, 2017
@mnot mnot added this to Odd Jobs in QUIC Apr 28, 2017
@martinthomson martinthomson added editorial An issue that does not affect the design of the protocol; does not require consensus. and removed design An issue that affects the design of the protocol; resolution requires consensus. labels Jun 10, 2017
@martinthomson
Copy link
Member Author

Duplicate of #58. Well, not that the offending text no longer appears anyway.

@mnot mnot removed this from Odd Jobs in QUIC Jun 21, 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
@martinthomson @ianswett