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

Jump to bottom

H3 guidance on CONNECTION_CLOSE does make clear if the type is 0x1c or 0x1d #3428

Closed
LPardue opened this issue Feb 5, 2020 · 0 comments · Fixed by #3437
Closed

H3 guidance on CONNECTION_CLOSE does make clear if the type is 0x1c or 0x1d #3428

LPardue opened this issue Feb 5, 2020 · 0 comments · Fixed by #3437
Labels
-http editorial
Projects
Late Stage Processing

Comments

@LPardue
Copy link
Member

@LPardue LPardue commented Feb 5, 2020

Draft 25 section 5.3 says:

An HTTP/3 implementation can immediately close the QUIC connection at
any time. This results in sending a QUIC CONNECTION_CLOSE frame to
the peer; the error code in this frame indicates to the peer why the
connection is being closed.

This doesn't specifically tie down H3-initiated closure to only use the application variant of CONNECTION_CLOSE (0x1d). This gets a bit strange when combined with later guidance to use H3 error codes or treat unknown error codes as H3_NO_ERROR
@LPardue LPardue added the -http label Feb 5, 2020
@LPardue LPardue added this to Triage in Late Stage Processing Feb 5, 2020
@larseggert larseggert added the editorial label Feb 6, 2020
@project-bot project-bot bot moved this from Triage to Editorial Issues in Late Stage Processing Feb 6, 2020
@MikeBishop MikeBishop mentioned this issue Feb 6, 2020
Merged
Late Stage Processing automation moved this from Editorial Issues to Text Incorporated Feb 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
-http editorial
Projects
Late Stage Processing
  
Issue Handled
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Application-layer close in HTTP/3 quicwg/base-drafts
2 participants
@larseggert @LPardue