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

Éric Vyncke's HTTP/3 Comment 9 #4759

Closed
LPardue opened this issue Jan 19, 2021 · 4 comments
Closed

Éric Vyncke's HTTP/3 Comment 9 #4759

LPardue opened this issue Jan 19, 2021 · 4 comments
Labels
-http iesg An issue raised during IESG review. proposal-ready An issue which has a proposal that is believed to be ready for a consensus call.
Projects
Late Stage Processing
Milestone
http-iesg

Comments

@LPardue
Copy link
Member

LPardue commented Jan 19, 2021

@evyncke said

-- Section 11.2 --
Should "and a contact of the HTTP working group (ietf-http-wg@w3.org)." rather
be "and a contact of the W3C HTTP working group (ietf-http-wg@w3.org)." ?
@LPardue LPardue added -http iesg An issue raised during IESG review. labels Jan 19, 2021
@LPardue LPardue added this to the http-iesg milestone Jan 19, 2021
@LPardue LPardue added this to Triage in Late Stage Processing via automation Jan 19, 2021
@martinthomson
Copy link
Member

Despite the email address, this is an IETF working group. This one has a long and rich history that explains the discrepancy.

@evyncke
Copy link

evyncke commented Jan 19, 2021

Amazing history probably behind ;-)

@MikeBishop
Copy link
Contributor

Proposal to make no change, since the reference is accurate.

@MikeBishop MikeBishop added the proposal-ready An issue which has a proposal that is believed to be ready for a consensus call. label Jan 19, 2021
@project-bot project-bot bot moved this from Triage to Consensus Emerging in Late Stage Processing Jan 19, 2021
@LPardue
Copy link
Member Author

LPardue commented Jan 26, 2021

Changing the HTTP WG email address is beyond the scope of this WG charter. Closing with no action.

@LPardue LPardue closed this as completed Jan 26, 2021
Late Stage Processing automation moved this from Consensus Emerging to Issue Handled Jan 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
-http iesg An issue raised during IESG review. proposal-ready An issue which has a proposal that is believed to be ready for a consensus call.
Projects
Late Stage Processing
  
Issue Handled
Milestone
http-iesg
Development

No branches or pull requests
4 participants
@martinthomson @MikeBishop @evyncke @LPardue