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

IANA review of -http; question 1 #4371

Closed
larseggert opened this issue Nov 17, 2020 · 3 comments · Fixed by #4392
Closed

IANA review of -http; question 1 #4371

larseggert opened this issue Nov 17, 2020 · 3 comments · Fixed by #4392
Assignees
Labels
-http ietf-lc An issue that was raised during IETF Last Call.
Milestone

Comments

@larseggert
Copy link
Member

larseggert commented Nov 17, 2020

Please see the review email for full context. This issue is tracking the following IANA question:

IANA Question --> [ RFC-to-be Section 11.2 of the current draft request creation of three new registries: frame types, settings and error codes. Should those registries be placed on the registry page created by draft-ietf-quic-transport or should a new registry page for HTTP/3 be created separate from the registry for QUIC?

@larseggert larseggert added this to Triage in Late Stage Processing via automation Nov 17, 2020
@larseggert larseggert added this to the http-iana milestone Nov 17, 2020
@MikeBishop
Copy link
Contributor

Responded to e-mail as well, but for GitHub tracking purposes, I believe HTTP/3 should be its own registry page, separate from QUIC and analogous to HTTP/2.

@gloinul
Copy link
Contributor

gloinul commented Nov 17, 2020

@MikeBishop I think that is a good proposal.

@martinthomson
Copy link
Member

Can we put that in the draft then?

@janaiyengar janaiyengar added the ietf-lc An issue that was raised during IETF Last Call. label Nov 18, 2020
Late Stage Processing automation moved this from Triage to Issue Handled Nov 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-http ietf-lc An issue that was raised during IETF Last Call.
Projects
Late Stage Processing
  
Issue Handled
Development

Successfully merging a pull request may close this issue.

5 participants