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

HTTP/QUIC is an abbreviation for "HTTP over QUIC" #1687

Merged
merged 1 commit into from Aug 27, 2018
Merged

HTTP/QUIC is an abbreviation for "HTTP over QUIC" #1687

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
16 changes: 8 additions & 8 deletions draft-ietf-quic-http.md
View file
Open in desktop
@@ -1,6 +1,6 @@
---
title: Hypertext Transfer Protocol (HTTP) over QUIC
abbrev: HTTP over QUIC
abbrev: HTTP/QUIC
docname: draft-ietf-quic-http-latest
date: {DATE}
category: std
Expand Down Expand Up @@ -1462,8 +1462,8 @@ QUIC has the same concepts of "stream" and "connection" errors that HTTP/2
provides. However, because the error code space is shared between multiple
components, there is no direct portability of HTTP/2 error codes.

The HTTP/2 error codes defined in Section 7 of {{!RFC7540}} map to the HTTP over
QUIC error codes as follows:
The HTTP/2 error codes defined in Section 7 of {{!RFC7540}} map to the HTTP/QUIC
error codes as follows:

NO_ERROR (0x0):
: HTTP_NO_ERROR in {{http-error-codes}}.
Expand Down Expand Up @@ -1517,10 +1517,10 @@ Error codes need to be defined for HTTP/2 and HTTP/QUIC separately. See

# Security Considerations

The security considerations of HTTP over QUIC should be comparable to those of
HTTP/2 with TLS. Note that where HTTP/2 employs PADDING frames to make a
connection more resistant to traffic analysis, HTTP/QUIC can rely on QUIC's own
PADDING frames or employ the reserved frame and stream types discussed in
The security considerations of HTTP/QUIC should be comparable to those of HTTP/2
with TLS. Note that where HTTP/2 employs PADDING frames to make a connection
more resistant to traffic analysis, HTTP/QUIC can rely on QUIC's own PADDING
frames or employ the reserved frame and stream types discussed in
{{frame-grease}} and {{stream-grease}}.

The modified SETTINGS format contains nested length elements, which could pose
Expand All @@ -1540,7 +1540,7 @@ established in {{?RFC7301}}.
The "hq" string identifies HTTP/QUIC:

Protocol:
: HTTP over QUIC
: HTTP/QUIC

Identification Sequence:
: 0x68 0x71 ("hq")
Expand Down
5 changes: 2 additions & 3 deletions draft-ietf-quic-qpack.md
View file
Open in desktop
Expand Up @@ -65,9 +65,8 @@ normative:
--- abstract

This specification defines QPACK, a compression format for efficiently
representing HTTP header fields, to be used in HTTP over QUIC. This is a
variation of HPACK header compression that seeks to reduce head-of-line
blocking.
representing HTTP header fields, to be used in HTTP/QUIC. This is a variation of
HPACK header compression that seeks to reduce head-of-line blocking.

--- note_Note_to_Readers

Expand Down