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

Roy's suggestion for multiplexing justification #3791

Merged
merged 1 commit into from Jun 30, 2020
Merged

Roy's suggestion for multiplexing justification #3791

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
10 changes: 5 additions & 5 deletions draft-ietf-quic-http.md
View file
Open in desktop
Expand Up @@ -107,11 +107,11 @@ semantics over a new transport protocol, QUIC.
HTTP/1.1 {{?HTTP11=I-D.ietf-httpbis-messaging}} is a TCP mapping which uses
whitespace-delimited text fields to convey HTTP messages. While these exchanges
are human-readable, using whitespace for message formatting leads to parsing
complexity and motivates tolerance of variant behavior. Because each
connection can transfer only a single HTTP request or response at a time in each
direction, multiple parallel TCP connections are often used, reducing the
ability of the congestion controller to effectively manage traffic between
endpoints.
complexity and motivates tolerance of variant behavior. Because HTTP/1.x does
not include a multiplexing layer, multiple TCP connections are often used to
service requests in parallel. However, that has a negative impact on congestion
control and network efficiency, since TCP does not share congestion control
across multiple connections.

HTTP/2 {{?HTTP2=RFC7540}} introduced a binary framing and multiplexing layer to
improve latency without modifying the transport layer. However, because the
Expand Down