SCTP is standardized by the (IETF) in . The SCTP reference implementation was released as part of version 7 in 2008 and has since been widely ported to other platforms.
Where Stream Control Transmission Protocol leads. Every connection below has a source: a link in this article, a shared Wikipedia category, or CirrusSearch text similarity. Articles already on your trail are left out.
Study aids for Stream Control Transmission Protocol
Terminology
SCTP
The Stream Control Transmission Protocol (SCTP) is a computer networking communications protocol in the transport layer of the Internet protocol suite.
Terms the article defines in bold, quoted in context.
Categories:
Computer-related introductions in 2000
Streaming
Internet Standards
Transport layer protocols
Multihoming
1,762 words · 27 references · revision 1368463329 · CC BY-SA 4.0
The IETF Signaling Transport (SIGTRAN) working group defined the protocol (number 1321) in October 2000,2 and the IETF Transport Area (TSVWG) working group maintains it. RFC9260 defines the protocol. RFC3286 provides an introduction.
Message-based multi-streaming
SCTP applications submit data for transmission in messages (groups of bytes) to the SCTP transport layer. SCTP places messages and control information into separate chunks (data chunks and control chunks), each identified by a chunk header. The protocol can fragment a message into multiple data chunks, but each data chunk contains data from only one user message. SCTP bundles the chunks into SCTP packets. The SCTP packet, which is submitted to the Internet Protocol, consists of a packet header, SCTP control chunks (when necessary), followed by SCTP data chunks (when available).
SCTP may be characterized as message-oriented, meaning it transports a sequence of messages (each being a group of bytes), rather than transporting an unbroken stream of bytes as in TCP. As in UDP, in SCTP a sender sends a message in one operation, and that exact message is passed to the receiving application process in one operation. In contrast, TCP is a stream-oriented protocol, transporting streams of bytes reliably and in order. However TCP does not allow the receiver to know how many times the sender application called on the TCP transport passing it groups of bytes to be sent out. At the sender, TCP simply appends more bytes to a queue of bytes waiting to go out over the network, rather than having to keep a queue of individual separate outbound messages which must be preserved as such.
The term multi-streaming refers to the capability of SCTP to transmit several independent streams of chunks in parallel, for example transmitting web page images simultaneously with the web page text. In essence, it involves bundling several connections into a single SCTP association, operating on messages (or chunks) rather than bytes.
TCP preserves byte order in the stream by including a byte sequence number with each segment. SCTP, on the other hand, assigns a sequence number or a message-idnote 1 to each message sent in a stream. This allows independent ordering of messages in different streams. However, message ordering is optional in SCTP; a receiving application may choose to process messages in the order of receipt instead of in the order of sending.
Features
Features of SCTP include:
Reliable transmission of both ordered and unordered data streams
Multihoming support in which one or both endpoints of a connection can consist of more than one IP address, enabling transparent fail-over between redundant network paths
Delivery of chunks within independent streams eliminates unnecessary head-of-line blocking, as opposed to TCP byte-stream delivery.
Explicit partial reliability
Path selection and monitoring to select a primary data transmission path and test the connectivity of the transmission path
Validation and acknowledgment mechanisms protect against flooding attacks and provide notification of duplicated or missing data chunks.
The designers of SCTP originally intended it for the transport of telephony (i.e. Signaling System 7) over Internet Protocol, with the goal of duplicating some of the reliability attributes of the SS7 signaling network in IP. This IETF effort is known as SIGTRAN. In the meantime, other uses have been proposed, for example, the Diameter protocol3 and Reliable Server Pooling (RSerPool).4
Motivation and adoption
TCP has provided the primary means to transfer data reliably across the Internet. However, TCP has imposed limitations on several applications. From RFC4960:
TCP provides both reliable data transfer and strict order-of-transmission delivery of data. Some applications need reliable transfer without sequence maintenance, while others would be satisfied with partial ordering of the data. In both of these cases, the head-of-line blocking property of TCP causes unnecessary delay.
For applications exchanging distinct records or messages, the stream-oriented nature of TCP requires the addition of explicit markers or other encoding to delineate the individual records.
In order to avoid sending many small IP packets where one single larger packet would have sufficed, the TCP implementation may delay transmitting data while waiting for possibly more data being queued by the application (Nagle's algorithm). Although many TCP implementations allow the disabling of Nagle's algorithm, this is not required by the specification. SCTP, on the other hand, allows undelayed transmission to be configured as a default for an association, eliminating any undesired delays, but at the cost of higher transfer overhead.5
The limited scope of TCP sockets complicates the task of providing highly-available data transfer capability using multihomed hosts.
TCP is relatively vulnerable to denial-of-service attacks, such as SYN attacks.
Adoption of SCTP has been slowed by lack of awareness, lack of implementations (particularly in Microsoft Windows), lack of application support and lack of network support.6
Asymmetric multihoming: local multihoming to remote single homing
Asymmetric multihoming: local single homing to remote multihoming
SCTP provides redundant paths to increase reliability.
Each SCTP end point needs to check reachability of the primary and redundant addresses of the remote end point using a heartbeat. Each SCTP end point needs to acknowledge the heartbeats it receives from the remote end point.
When SCTP sends a message to a remote address, the source interface will only be decided by the routing table of the host (and not by SCTP).
In asymmetric multihoming, one of the two endpoints does not support multihoming.
In local multihoming and remote single homing, if the remote primary address is not reachable, the SCTP association fails even if an alternate path is possible.
The common header, which occupies the first 12 bytes and is highlighted in blue.
The data chunks, which occupy the remaining portion of the packet. The first chunk is highlighted in green, and the last of N chunks (Chunk N) is highlighted in red.
Bits
0–7
8–15
16–23
24–31
+0
Source port
Destination port
32
Verification tag
64
Checksum
96
Chunk 1 type
Chunk 1 flags
Chunk 1 length
128
Chunk 1 data
…
…
…
Chunk N type
Chunk N flags
Chunk N length
…
Chunk N data
Each chunk starts with a one-byte type identifier, with 15 chunk types defined by RFC9260, and at least 5 more defined by additional RFCs.note 2 Eight flag bits, a two-byte length field, and the data compose the remainder of the chunk. If the chunk does not form a multiple of 4 bytes (i.e., the length is not a multiple of 4), then it is padded with zeros, which are not included in the chunk length. The two-byte length field limits each chunk to a 65,535-byte length (including the type, flags and length fields).
Security
Although encryption was not part of the original SCTP design, SCTP was designed with features for improved security, such as 4-way handshake (compared to TCP 3-way handshake) to protect against SYN flooding attacks, and large "cookies" for association verification and authenticity.
Reliability was also a key part of the security design of SCTP. Multihoming enables an association to stay open even when some routes and interfaces are down. This is of particular importance for SIGTRAN as it carries SS7 over an IP network using SCTP, and requires strong resilience during link outages to maintain telecommunication service even when enduring network anomalies.
Implementations
The SCTP reference implementation runs on FreeBSD, Mac OS X, Microsoft Windows, and Linux.8
Multipath TCP – which allows a TCP connection to use multiple paths to maximize resource usage and increase redundancy
Happy Eyeballs – originally designed for efficient selection of IPv4 or IPv6 for a connection;24 could also be adapted to select from different transport protocols such as TCP and SCTP25
Notes
note 1The DATA chunk uses a sequence number for ordered messages, the I-DATA chunk, which solves some problems with the original DATA chunk, uses a message-id for all messages
In the absence of native SCTP support in operating systems, it is possible to tunnel SCTP over UDP,22 as well as to map TCP API calls to SCTP calls so existing applications can use SCTP without modification.23
6458
RFC6096 Stream Control Transmission Protocol (SCTP) Chunk Flags Registration (obsoleted by RFC 9260)
RFC5062 Security Attacks Found Against the Stream Control Transmission Protocol (SCTP) and Current Countermeasures
RFC5061 Stream Control Transmission Protocol (SCTP) Dynamic Address Reconfiguration
RFC5043 Stream Control Transmission Protocol (SCTP) Direct Data Placement (DDP) Adaptation
RFC4960 Stream Control Transmission Protocol (obsoleted by RFC 9260)
RFC4895 Authenticated Chunks for the Stream Control Transmission Protocol (SCTP)
RFC4820 Padding Chunk and Parameter for the Stream Control Transmission Protocol (SCTP)
RFC4460 Stream Control Transmission Protocol (SCTP) Specification Errata and Issues (obsoleted by RFC 9260)
7Olsson, Magnus; Mulligan, Catherine; Sultana, Shabnam; Rommer, Stefan; Frid, Lars (2013). EPC and 4G packet networks: driving the mobile broadband revolution (2nd ed.). Amsterdam Boston: Elsevier/AP, Academic Press is an imprint of Elsevier. p. 491. ISBN 978-0-12-394595-2.
8"Reference Implementation for SCTP - RFC4960". GitHub. Retrieved 2013-10-14. “This is the reference implementation for SCTP. It is portable and runs on FreeBSD/MAC-OS/Windows and in User Space (including linux).”
12"About FreeBSD's Technological Advances". The FreeBSD Project. 2008-03-09. Retrieved 2008-09-13. “SCTP: FreeBSD 7.0 is the reference implementation for the new IETF Stream Control Transmission Protocol (SCTP) protocol, intended to support VoIP, telecommunications, and other applications with strong reliability and variable quality transmission through features such as multi-path delivery, fail-over, and multi-streaming.”
ExplicitmRemoving link(s) because Expired PROD, concern was: Not suitable for an encyclopedia. Largely a synthesis of various standards and a collection of external links, with no attempt to establish notability. (XFDcloser)−4diff
Transmission Control Protocol (TCP) uses one of several congestion control algorithms that include various aspects of an additive increase/multiplicative decrease (AIMD) scheme, along with other…
Principal protocol used to stream data across an IP network
The Transmission Control Protocol (TCP) is one of the main protocols of the Internet protocol suite, providing reliable, ordered, and error-checked delivery of a stream of octets (bytes) between applications running on hosts communicating via an IP network.
The Internet Engineering Task Force (IETF) is a standards organization for the Internet responsible for the technical standards of the Internet protocol suite (TCP/IP).
Framework for communication protocols used in IP networking
The Internet protocol suite, commonly known as TCP/IP, is a framework for organizing the communication protocols used in the Internet and similar computer networks according to functional criteria.
In computer networking, the transport layer is an abstraction layer in a network protocol stack that provides communication services between applications.
Network that allows computers to share resources and communicate with each other
In computer science, computer engineering, and telecommunications, a network is a group of communicating computers and peripherals called hosts, which communicate data to other hosts via communication protocols, as facilitated by networking hardware.
Principal protocol used for transmission of datagrams across an IP network
In computer networking, the User Datagram Protocol (UDP) is one of the core communication protocols of the Internet protocol suite used to send messages (transported as datagrams in packets) to other hosts on an Internet Protocol (IP) network.
The Session Initiation Protocol (SIP) is a signaling protocol used for initiating, maintaining, modifying, and terminating communication sessions that involve multimedia elements such as voice, video, and messaging.
Mobile telephony is the provision of Wireless telephone services to mobile phones, distinguishing it from fixed-location telephony provided via landline phones.
A web page, or webpage, sometimes contextually shortened to just page, is a document, typically published on the Web, and normally viewed using a web browser, which consists of hypertext and often additional components such as scripts and graphics.
SYN flooding (or TCP SYN flood) is a form of denial-of-service attack against systems that provide services over the Transmission Control Protocol (TCP).
