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

Restructure the abstract and overview #4329

Merged
merged 7 commits into from
Nov 10, 2020
Merged

Restructure the abstract and overview #4329

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
f6a0f3c
Restructure the abstract and overview
martinthomson Nov 4, 2020
d32ab43
Tweak abstract again
martinthomson Nov 5, 2020
28df8f0
A delivery from Oxford
martinthomson Nov 5, 2020
9944eba
Feedback
martinthomson Nov 5, 2020
94aeddc
Jana's suggestions
martinthomson Nov 9, 2020
b880714
-both
martinthomson Nov 10, 2020
4b60b93
Damn, I was worried someone might like this
martinthomson Nov 10, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -142,11 +142,11 @@ unidirectional streams, which allow a single endpoint to send data. A
credit-based scheme is used to limit stream creation and to bound the amount of
data that can be sent.

Application data can be reliably delivered by QUIC. An acknowledgment-based
algorithm for detecting and recovering from loss of data is described in
{{QUIC-RECOVERY}}. QUIC depends on congestion control to avoid network
congestion. An exemplary congestion control algorithm is also described in
{{QUIC-RECOVERY}}.
QUIC provides the necessary feedback to implement reliable delivery and
congestion control. An algorithm for detecting and recovering from loss of
data is described in {{QUIC-RECOVERY}}. QUIC depends on congestion control
to avoid network congestion. An exemplary congestion control algorithm is
also described in {{QUIC-RECOVERY}}.

QUIC connections are not strictly bound to a single network path. Connection
migration uses connection identifiers to allow connections to transfer to a new
Expand Down