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

QPACK-18: Normative reference for RFC2360 #4243

Closed
gloinul opened this issue Oct 19, 2020 · 2 comments · Fixed by #4246
Closed

QPACK-18: Normative reference for RFC2360 #4243

gloinul opened this issue Oct 19, 2020 · 2 comments · Fixed by #4246
Labels
-qpack editorial An issue that does not affect the design of the protocol; does not require consensus. ietf-lc An issue that was raised during IETF Last Call.
Projects
Late Stage Processing

Comments

@gloinul
Copy link
Contributor

gloinul commented Oct 19, 2020

Section 1.2:

Diagrams use the format described in Section 3.1 of [RFC2360], with the following additional conventions:

This clearly is an normative reference to RFC2360, please change its classification.
@larseggert larseggert added -qpack ietf-lc An issue that was raised during IETF Last Call. labels Oct 19, 2020
@larseggert larseggert added this to Triage in Late Stage Processing via automation Oct 19, 2020
@gloinul gloinul changed the title QPACK-31: Normative reference for RFC2360 QPACK-18: Normative reference for RFC2360 Oct 19, 2020
@larseggert
Copy link
Member

Agreed. Marking as "editorial".

@larseggert larseggert added the editorial An issue that does not affect the design of the protocol; does not require consensus. label Oct 19, 2020
@project-bot project-bot bot moved this from Triage to Editorial Issues in Late Stage Processing Oct 19, 2020
@larseggert larseggert mentioned this issue Oct 19, 2020
Merged
@MikeBishop
Copy link
Contributor

Given that the diagrams themselves are illustrative and the text governs, is the format used in the diagrams actually essential to correctly implementing the protocol?

Late Stage Processing automation moved this from Editorial Issues to Issue Handled Oct 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
-qpack editorial An issue that does not affect the design of the protocol; does not require consensus. ietf-lc An issue that was raised during IETF Last Call.
Projects
Late Stage Processing
  
Issue Handled
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Make 2360 normative larseggert/base-drafts
3 participants
@larseggert @MikeBishop @gloinul