2000
DOI: 10.17487/rfc2883
|View full text |Cite
|
Sign up to set email alerts
|

An Extension to the Selective Acknowledgement (SACK) Option for TCP

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

1
169
0
7

Year Published

2002
2002
2021
2021

Publication Types

Select...
7
3

Relationship

1
9

Authors

Journals

citations
Cited by 278 publications
(177 citation statements)
references
References 2 publications
1
169
0
7
Order By: Relevance
“…Duplicate segments at the TCP receiver normally trigger DSACKs [9]. The DSACK statistics provide a measure of network resources that were wasted by overly aggressive retransmits of nearly all types, except segments with no pay-load.…”
Section: Tcpmentioning
confidence: 99%
“…Duplicate segments at the TCP receiver normally trigger DSACKs [9]. The DSACK statistics provide a measure of network resources that were wasted by overly aggressive retransmits of nearly all types, except segments with no pay-load.…”
Section: Tcpmentioning
confidence: 99%
“…If an out-of-order packet arrives, a duplicated ACK is sent, and if an in-order packet arrives, the ACK sending may be delayed (but one ACK should be sent for at least every second packet arrival and no later than 500 ms after the first arrival [8]). Selective ACKs (SACK), which indicate non-contiguous blocks of consecutive bytes correctly received, have also been defined [9,10].…”
Section: Reliable Delivery In Tcpmentioning
confidence: 99%
“…It then reacts, say, by recovering previous congestion responses and/or disabling future congestion responses for a time period. The Eifel algorithm (Ludwig and Katz, 2000), DSACK TCP (Floyd et al, 2000), and TCP-DOOR (Wang and Zhang, 2002), belong to this class.…”
Section: Related Workmentioning
confidence: 99%