Draft evaluation for QUIC. #17
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
chrisn
reviewed
Jan 19, 2017
| # QUIC | ||
|
|
||
| [QUIC](https://www.chromium.org/quic) is a multiplexed stream transport over | ||
| UDP. It advertises the following benefits: |
There was a problem hiding this comment.
I suggest changing "benefits" to "benefits over TCP"
chrisn
reviewed
Jan 19, 2017
| controller and display. The following mapping could be used to associate | ||
| streams with Presentation API concepts: | ||
|
|
||
| - One reserved stream 5 for control messages between the controller and display. |
Adds non-functional requirements for user experience. Additional editing.
Template for transport evaluation
|
Thanks for looking it over @chrisn. Merged |
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.
Addresses Issue #9: Evaluate QUIC as a protocol transport
Based on conversation with a QUIC developer in Chromium and evaluation of the spec, this is a draft evaluation of QUIC using the template in PR #16.
Many details need to be determined and also reconciled with the current draft specification; my initial review was based on the public documents on chromium.org, and not the current IETF draft.
So consider this a first draft :)