Stream Control Transmission Protocol
RFC 9260, “Stream Control Transmission Protocol”, is a Proposed Standard document published in June 2022 by R. Stewart, M. Tüxen, K. Nielsen. It obsoletes RFC 4460, RFC 4960, RFC 6096, RFC 7053, RFC 8540. The canonical text is published by the RFC Editor.
Abstract
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 9260 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 9259 Operations, Administration, and Maintenance in Segment Routing over IPv6
- RFC 9261 Exported Authenticators in TLS
- RFC 9258 Importing External Pre-Shared Keys for TLS 1.3
- RFC 9262 Tree Engineering for Bit Index Explicit Replication
- RFC 9257 Guidance for External Pre-Shared Key Usage in TLS
- RFC 9263 Network Service Header Metadata Type 2 Variable-Length Context Headers
- RFC 9256 Segment Routing Policy Architecture
- RFC 9264 Linkset: Media Types and a Link Relation Type for Link Sets