| Ethan Blanton and Mark Allman. Using TCP DSACKs and SCTP Duplicate TSNs to Detect Spurious Retransmissions, 2004. RFC 3708. |
....Response to a spurious timeout by different TCPs. Timestamps are enabled and the bug fix is disabled. the sequence number of a packet that triggered a DUPACK [RFC2883] D SACK info comes too late to avoid go back N retransmissions, but it can be used to learn about unnecessary retransmissions [BA01b] and adapt the for the future. In our experience, the impact of delay spikes on real world TCPs is worse than have been described above. Almost every TCP tested against a delay spike revealed implementation bugs [GU01b] One goal of this document is to make the TCP developers aware of the ....
E. Blanton, M. Allman. Using TCP DSACKs and SCTP Duplicate TSNs to Detect Spurious Retransmissions, August 2001, work in progress.
No context found.
Ethan Blanton and Mark Allman. Using TCP DSACKs and SCTP Duplicate TSNs to Detect Spurious Retransmissions, 2004. RFC 3708.
No context found.
Ethan Blanton and Mark Allman. Using TCP DSACKs and SCTP Duplicate TSNs to Detect Spurious Retransmissions, 2004. RFC 3708.
No context found.
Ethan Blanton and Mark Allman. Using TCP DSACKs and SCTP Duplicate TSNs to Detect Spurious Retransmissions, 2004. RFC 3708.
No context found.
E. Blanton and M. Allman, "Using TCP DSACKs and SCTP Duplicate TSNs to detect spurious retransmissions," Internet Draft, draft-blantondsack -use-01.txt, August 2001.
No context found.
E. Blanton and M. Allman, Using TCP DSACKs and SCTP Duplicate TSNs to Detect Spurious Retransmissions. Available at: http://www.ietf.org/internet-drafts/ draft-ietf-tsvwg-dsack-use-01.txt, last checked 03.10.2003.
No context found.
Blanton, E. and M. Allman, "Using TCP DSACKs and SCTP Duplicate TSNs to Detect Spurious Retransmissions", Work in Progress.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC