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

Editorial changes #1341

Merged
merged 2 commits into from May 8, 2018
Merged

Editorial changes #1341

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0ee6c91
Add colon
martinthomson May 8, 2018
8b11341
Only really h2 with TLS
martinthomson May 8, 2018
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
4 changes: 2 additions & 2 deletions draft-ietf-quic-http.md
View file
Open in desktop
Expand Up @@ -1297,7 +1297,7 @@ STREAM_CLOSED (0x5):
: Not applicable, since QUIC handles stream management. Would provoke a
QUIC_STREAM_DATA_AFTER_TERMINATION from the QUIC layer.

FRAME_SIZE_ERROR (0x6)
FRAME_SIZE_ERROR (0x6):
: No single mapping. See new error codes defined in {{http-error-codes}}.

REFUSED_STREAM (0x7):
Expand Down Expand Up @@ -1329,7 +1329,7 @@ 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.
HTTP/2 with TLS.

The modified SETTINGS format contains nested length elements, which could pose
a security risk to an uncautious implementer. A SETTINGS frame parser MUST
Expand Down