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

Permanent transport parameters #4880

Closed
martinthomson opened this issue Apr 30, 2021 · 1 comment · Fixed by #4887
Closed

Permanent transport parameters #4880

martinthomson opened this issue Apr 30, 2021 · 1 comment · Fixed by #4887

Comments

@martinthomson
Copy link
Member

The RFC editor asks:

Should the "QUIC Transport Parameters" registry include a "permanent" range (similar to the "QUIC Versions" registry)? Or are values outside of those marked "provisional" all considered permanent?

I believe that this is just an error in transcription. This should match the others and permanent assignments can be made with a specification.

I realize that this is super-late, but I realize that we reserved up to 0x3f for error codes (where size matters very little), but not for transport parameters (where size can matter). Do we want to update that at the same time?

-- https://www.iana.org/assignments/quic/quic.xhtml

@larseggert larseggert added this to Triage in Late Stage Processing via automation Apr 30, 2021
@DavidSchinazi
Copy link
Contributor

I had assumed that we had reserved 0x00-0x3f in transport parameters too. I suspect that was the intent, and we just forgot to add that sentence. I would really prefer we update the doc to reserve 0x00-0x3f for transport parameters just like we do for errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Late Stage Processing
  
Issue Handled
Development

Successfully merging a pull request may close this issue.

2 participants