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

Tidy up reference style #4820

Merged
merged 9 commits into from Feb 2, 2021
Merged

Tidy up reference style #4820

Changes from 1 commit
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
e9f421e
Tidy up reference style
mnot Jan 28, 2021
fa4979a
fix spacing nits
mnot Jan 28, 2021
7963266
Update draft-ietf-quic-recovery.md
mnot Jan 28, 2021
93513e6
Fix transport
mnot Jan 28, 2021
cc04920
Rewrap
MikeBishop Jan 28, 2021
457e5c8
Update draft-ietf-quic-transport.md
mnot Jan 28, 2021
f90dcc5
Update draft-ietf-quic-transport.md
mnot Jan 28, 2021
0329148
Update draft-ietf-quic-transport.md
mnot Jan 28, 2021
49c7e54
Bullet X in Section Y of [Z]
martinthomson Jan 29, 2021
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
2 changes: 1 addition & 1 deletion draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -4023,7 +4023,7 @@ acknowledged. This includes packets that are acknowledged after being declared
lost, which can happen in the presence of network reordering. Doing so requires
senders to retain information about packets after they are declared lost. A
sender can discard this information after a period of time elapses that
adequately allows for reordering, such as a PTO ( {{Section 6.2 of
adequately allows for reordering, such as a PTO ({{Section 6.2 of
QUIC-RECOVERY}}), or on other events, such as reaching a memory limit.

Upon detecting losses, a sender MUST take appropriate congestion control action.
Expand Down