HTTP/2 Guidance and Extensions #363
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This looks pretty good, I have a comment about ALTSVC that I will make on #242. |
Closed
martinthomson
approved these changes
Mar 9, 2017
draft-ietf-quic-http.md
Outdated
| # Considerations for Transitioning from HTTP/2 | ||
|
|
||
| HTTP/QUIC is strongly informed by HTTP/2, and bears many similarities. This | ||
| section points out useful differences from HTTP/2 and describes how to map |
There was a problem hiding this comment.
Not all the differences are useful. I would use the word "important".
draft-ietf-quic-http.md
Outdated
| frame ID has been reserved in order to maximize portability between HTTP/2 and | ||
| HTTP/QUIC implementations. However, equivalent frames between the two mappings | ||
| are not identical. | ||
|
|
There was a problem hiding this comment.
Another important difference is that while there is an absolute ordering between every frame in h2, this is not true for frames on different streams in QUIC. You mention this below, but only obliquely. I think that it's important enough for a paragraph.
| Some transport-level options that HTTP/2 specifies via the SETTINGS frame are | ||
| superseded by QUIC transport parameters in HTTP/QUIC. The HTTP-level options | ||
| that are retained in HTTP/QUIC have the same value as in HTTP/2. | ||
|
|
There was a problem hiding this comment.
Another important difference: settings can't change.
|
Addressed Martin's feedback, and consolidated more text into the new section. If we want to switch to a new IANA registry, it's a fairly small step from here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Collates the HTTP/2 migration guidance from various places into a single section, and expands on details about how HTTP/2 extensions can be used/ported. In the process, I added more IANA stuff, which should address the HTTP portion of #359.
Builds on #274; Closes #242.