2003
DOI: 10.17487/rfc3517
|View full text |Cite
|
Sign up to set email alerts
|

A Conservative Selective Acknowledgment (SACK)-based Loss Recovery Algorithm for TCP

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
109
0
2

Year Published

2004
2004
2020
2020

Publication Types

Select...
6
3

Relationship

2
7

Authors

Journals

citations
Cited by 113 publications
(111 citation statements)
references
References 11 publications
0
109
0
2
Order By: Relevance
“…If additional losses within the current window occur and are congestion-based (i.e., no Oracle notification for the loss was received) the TCP will reduce cwnd upon retransmission of the first congestion-based loss in the window and clear the flag that indicates a congestion response has not been invoked. This scheme is similar to using TCP SACK [11] or TCP NewReno [19] in that one cwnd reduction per "loss event" is taken.…”
Section: Oracle Notificationsmentioning
confidence: 99%
“…If additional losses within the current window occur and are congestion-based (i.e., no Oracle notification for the loss was received) the TCP will reduce cwnd upon retransmission of the first congestion-based loss in the window and clear the flag that indicates a congestion response has not been invoked. This scheme is similar to using TCP SACK [11] or TCP NewReno [19] in that one cwnd reduction per "loss event" is taken.…”
Section: Oracle Notificationsmentioning
confidence: 99%
“…It is best if Packetization Protocols use an explicit loss detection mechanism such as a Selective Acknowledgment (SACK) scoreboard [RFC3517] or ACK Vector [RFC4340] to distinguish real losses from reordered data, although implicit mechanisms such as TCP Reno style duplicate acknowledgments counting are sufficient.…”
Section: Mechanism To Detect Lossmentioning
confidence: 99%
“…A TCP should be expected to implement SACK; however, SACK is a negotiated option and is only used if support is advertised by both sides of a connection. This document [RFC3517] describes a relatively sophisticated algorithm that a TCP sender can use for loss recovery when SACK reports more than one segment lost from a single flight of data.…”
Section: Sack-based Loss Recovery and Congestion Controlmentioning
confidence: 99%