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

Add FACK reference #2119

Merged
merged 2 commits into from Dec 13, 2018
Merged

Add FACK reference #2119

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
07f4e5d
Add FACK reference
janaiyengar Dec 12, 2018
d04dbf6
move FACK reference
janaiyengar Dec 12, 2018
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
14 changes: 12 additions & 2 deletions draft-ietf-quic-recovery.md
View file
Open in desktop
Expand Up @@ -44,6 +44,15 @@ normative:
org: Mozilla
role: editor

informative:

FACK:
title: "Forward Acknowledgement: Refining TCP Congestion Control"
author:
- ins: M. Mathis
- ins: J. Mahdavi
date: 1996-08
seriesinfo: ACM SIGCOMM

--- abstract

Expand Down Expand Up @@ -300,7 +309,7 @@ frame. For more information, see Section 13.2 of {{QUIC-TRANSPORT}}.
## Ack-based Detection

Ack-based loss detection implements the spirit of TCP's Fast Retransmit
{{?RFC5681}}, Early Retransmit {{?RFC5827}}, FACK, SACK loss recovery
{{?RFC5681}}, Early Retransmit {{?RFC5827}}, FACK {{FACK}}, SACK loss recovery
{{?RFC6675}}, and RACK {{?RACK=I-D.ietf-tcpm-rack}}. This section provides an
overview of how these algorithms are implemented in QUIC.

Expand All @@ -325,7 +334,8 @@ smaller initial reordering thresholds to minimize recovery latency.
### Packet Threshold

The RECOMMENDED initial value for the packet reordering threshold
(kPacketThreshold) is 3, based on TCP loss detection {{?RFC5681}} {{?RFC6675}}.
(kPacketThreshold) is 3, based on best practices for TCP loss detection
{{?RFC5681}} {{?RFC6675}}.

Some networks may exhibit higher degrees of reordering, causing a sender to
detect spurious losses. Implementers MAY use algorithms developed for TCP, such
Expand Down