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

QPACK-18: HTTP semantics section reference #4242

Closed
gloinul opened this issue Oct 19, 2020 · 1 comment · Fixed by #4247
Closed

QPACK-18: HTTP semantics section reference #4242

gloinul opened this issue Oct 19, 2020 · 1 comment · Fixed by #4247
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.

Comments

@gloinul
Copy link
Contributor

gloinul commented Oct 19, 2020

Section 1.1: HTTP field line:
A name-value pair sent as part of an HTTP field section. See Section 5 of [SEMANTICS].

I would guess that this can be refined to point to section 5.4.

@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: HTTP semantics section reference QPACK-18: HTTP semantics section reference Oct 19, 2020
@larseggert
Copy link
Member

Proposed change is "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
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
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
Development

Successfully merging a pull request may close this issue.

2 participants