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

HTTP-31: HTTP/3 Connection definition? #4206

Closed
gloinul opened this issue Oct 14, 2020 · 5 comments · Fixed by #4212
Closed

HTTP-31: HTTP/3 Connection definition? #4206

gloinul opened this issue Oct 14, 2020 · 5 comments · Fixed by #4212
Labels
-http 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 14, 2020

Section 2.2.:

"connection:
A transport-layer connection between two endpoints, using QUIC as the transport protocol.
connection error:
An error that affects the entire HTTP/3 connection."

In a total of 11 places this document uses "HTTP/3 connection". The word connection exists 213 times in this document (HTML version). So are there a difference between connection and HTTP/3 Connection, and if it is can that be clearly expressed. Else maybe alignment would be better.

Secondly, I think the above "connection" definition is likely missing one important aspect isn't it? I have the impression that an "HTTP/3" connection is a QUIC connection established with the purpose of communicating HTTP/3 over it. That intention is likely explicitly expressed at QUIC connection establishment using ALPN?

@larseggert larseggert added -http ietf-lc An issue that was raised during IETF Last Call. labels Oct 14, 2020
@larseggert larseggert added this to Triage in Late Stage Processing via automation Oct 14, 2020
@gloinul
Copy link
Contributor Author

gloinul commented Oct 15, 2020

So that pull request resolves the definition of the HTTP connection. Does the usage of HTTP/3 connection vs Connection in the document need adjustment? In other words, can you please check all the usage of connection if there is difference and if anywhere it needs to be clarified that it is not an HTTP/3 connection?

@larseggert
Copy link
Member

Based on #4212, labeling this as "editorial"

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

Having looked through the occurrences of "connection" in the document, I mostly think it's clear from context which type of connection we're talking about. (It also helps that an HTTP/3 connection is a QUIC connection, and so it's rarely necessary to distinguish the two.) I did a slightly aggressive pass in 2530b98, but I think I'm going to pare that down a bit.

@MikeBishop
Copy link
Contributor

Okay, I've pushed a less-aggressive change as dae7b75.

@gloinul
Copy link
Contributor Author

gloinul commented Oct 16, 2020

Thanks @MikeBishop that commit appear good to me. I think with these changes this issue is resolved.

Late Stage Processing automation moved this from Editorial Issues to Issue Handled Oct 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-http 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.

3 participants