Worst-case performance limitation of TCP SACK and a feasible solution

Srijith, K.N.; Jacob, Lillykutty; Ananda, A.L.

doi:10.1109/iccs.2002.1183313

Cited by 10 publications

(10 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The key difference between [13] and [5] is that [13] uses byte as the offset unit, but [5] uses the unchanged segment size as the unit. Hence, the scheme presented in [5] can represent the more SACK blocks using the same TCP option space (40 bytes can be available for 19 SACK blocks at least), and thus it is more effective in some scenarios, compared to that of [13].…”

Section: Related Workmentioning

confidence: 99%

“…In [13], a concept of offset is presented to send the more SACK blocks' information. In the scheme, the sender only sends one 32-bit absolute sequence number for the highest sequence number of the out-of-order segments (denote it by A), instead of sending all absolute ones.…”

Section: Related Workmentioning

confidence: 99%

“…Both [13] and [5] use offsets to maximize the blocks' number in SACK option. The key difference between [13] and [5] is that [13] uses byte as the offset unit, but [5] uses the unchanged segment size as the unit.…”

Section: Related Workmentioning

confidence: 99%

“…2. [13] It is noted that each offset has the same length (labeled 'X ') which is decided by the maximum offset (O max ) with respect to A as follows:…”

Section: Related Workmentioning

confidence: 99%

“…By definition of SACK option format proposed in [13], the total length of whole SACK option field will have the following bytes:…”

Section: Related Workmentioning

confidence: 99%

See 4 more Smart Citations

A Segment-Based SACK Scheme for TCP Over the Error-Prone Links

Chen

Cui

Lee

2010

Wireless Pers Commun

View full text Add to dashboard Cite

The TCP Selective ACK (SACK) is used to notify information on the sequence space of the receiving buffer to the sender. By definition of RFC 2018, however, each SACK block has to be described by the two 32-bit unsigned integers, which may introduce significant extra load in the reverse ACK path when TCP connection is error-prone. Moreover, due to the 40-byte limitation of TCP option field, the available option space may not be sufficient to report all of the sequence blocks when the errors occur in a sudden burst. This may result in the unnecessary spurious retransmissions while the reverse SACK path is severely congested. To overcome such shortcomings, we propose a segment-based TCP SACK scheme in this paper. Both the theoretical analysis and simulation results show that the proposed scheme not only can significantly reduce the SACK overhead but also can avoid the unwanted spurious retransmissions in some specific error-prone scenarios.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

“…2. [13] It is noted that each offset has the same length (labeled 'X ') which is decided by the maximum offset (O max ) with respect to A as follows:…”

Section: Related Workmentioning

confidence: 99%

“…By definition of SACK option format proposed in [13], the total length of whole SACK option field will have the following bytes:…”

Section: Related Workmentioning

confidence: 99%

See 3 more Smart Citations