RFC 3708: Using TCP Duplicate Selective Acknowledgement (DSACKs) and Stream Control Transmission Protocol (SCTP) Duplicate Transmission Sequence Numbers (TSNs) to Detect Spurious Retransmissions
In plain English — editorial summary, not part of the RFC
TCP and Stream Control Transmission Protocol (SCTP) provide notification of duplicate segment receipt through Duplicate Selective Acknowledgement (DSACKs) and Duplicate Transmission Sequence Number (TSN) notification, respectively. This document presents conservative methods of using this information to identify unnecessary retransmissions for various applications. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC3708
- Published
- February 2004
- Authors
- E. Blanton; M. Allman
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- wit
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3758Stream Control Transmission Protocol (SCTP) Partial Reliability ExtensionCurrent
May 2004
- RFC 3436Transport Layer Security over Stream Control Transmission ProtocolUpdated
December 2002
- RFC 3554On the Use of Stream Control Transmission Protocol (SCTP) with IPsecCurrent
July 2003
- RFC 3868Signalling Connection Control Part User Adaptation Layer (SUA)Current
October 2004
- RFC 3873Stream Control Transmission Protocol (SCTP) Management Information Base (MIB)Current
September 2004
- RFC 3331Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Adaptation LayerCurrent
September 2002
- RFC 4233Integrated Services Digital Network (ISDN) Q.921-User Adaptation LayerUpdated
January 2006
- RFC 4460Stream Control Transmission Protocol (SCTP) Specification Errata and IssuesObsoleted
April 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?