Stream Control Transmission Protocol, June 2022
- File formats:
- Also available: XML file for editing
- PROPOSED STANDARD
- RFC 4460, RFC 4960, RFC 6096, RFC 7053, RFC 8540
- R. Stewart
- tsvwg (tsv)
Cite this RFC: TXT | XML | BibTeX
Discuss this RFC: Send questions or comments to the mailing list firstname.lastname@example.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 9260
This document describes the Stream Control Transmission Protocol (SCTP) and obsoletes RFC 4960. It incorporates the specification of the chunk flags registry from RFC 6096 and the specification of the I bit of DATA chunks from RFC 7053. Therefore, RFCs 6096 and 7053 are also obsoleted by this document. In addition, RFCs 4460 and 8540, which describe errata for SCTP, are obsoleted by this document.
SCTP was originally designed to transport Public Switched Telephone Network (PSTN) signaling messages over IP networks. It is also suited to be used for other applications, for example, WebRTC.
SCTP is a reliable transport protocol operating on top of a connectionless packet network, such as IP. It offers the following services to its users:
The design of SCTP includes appropriate congestion avoidance behavior and resistance to flooding and masquerade attacks.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.