===== RFC4960 - Stream Control Transmission Protocol ===== [[dido:public:ra:xapend:xapend.b_stds:tech:ietf:start| return to the IETF Standards ]] | Title | Stream Control Transmission Protocol | | Acronym | SCTP | | Version | 2007 | | Document Number | RFC4960 | | Release Date | September 2007 | | Reference | [[https://tools.ietf.org/html/rfc4960]] |
Data sheet for RFC4960 Stream Control Transmission Protocol (SCTP)
: **Note**: The following is an excerpt from the official IETF RFC. It is provided here as a convenience and is not authoritative. Refer to the original document as the authoritative reference. ==== Introduction ==== This document obsoletes RFC 2960 and RFC 3309. It describes the [[dido:public:ra:xapend:xapend.a_glossary:s:sctp]]. SCTP is designed to transport Public Switched Telephone Network (PSTN) signaling messages over [[dido:public:ra:xapend:xapend.a_glossary:i:ip]] networks, but is capable of broader applications. 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: * acknowledged error-free non-duplicated transfer of user data, * data fragmentation to conform to discovered path MTU size, * sequenced delivery of user messages within multiple streams, with an option for order-of-arrival delivery of individual user messages, * optional bundling of multiple user messages into a single SCTP packet, and * network-level [[dido:public:ra:xapend:xapend.a_glossary:f:faulttolerance|fault tolerance]] through supporting of multi-homing at either or both ends of an association. The design of SCTP includes appropriate congestion avoidance behavior and resistance to flooding and masquerade attacks. /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- /* To add a discussion page to this page, comment out the line that says ~~DISCUSSION:off~~ */ ~~DISCUSSION:on|Outstanding Issues~~ ~~DISCUSSION:off~~