RFC 3758: Stream Control Transmission Protocol (SCTP) Partial Reliability Extension
In plain English — editorial summary, not part of the RFC
This memo describes an extension to the Stream Control Transmission Protocol (SCTP) that allows an SCTP endpoint to signal to its peer that it should move the cumulative ack point forward. When both sides of an SCTP association support this extension, it can be used by an SCTP implementation to provide partially reliable data transmission service to an upper layer protocol. This memo describes the protocol extensions, which consist of a new parameter for INIT and INIT ACK, and a new FORWARD TSN chunk type, and provides one example of a partially reliable service that can be provided to the upper layer via this mechanism. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3758
- Published
- May 2004
- Authors
- R. Stewart; M. Ramalho; Q. Xie; M. Tuexen; P. Conrad
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3708Using TCP Duplicate Selective Acknowledgement (DSACKs) and Stream Control Transmission Protocol (SCTP) Duplicate Transmission Sequence Numbers (TSNs) to Detect Spurious RetransmissionsCurrent
February 2004
- RFC 3436Transport Layer Security over Stream Control Transmission ProtocolUpdated
December 2002
- 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 3554On the Use of Stream Control Transmission Protocol (SCTP) with IPsecCurrent
July 2003
- 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?