Stream Control Transmission Protocol
RFC 4960
Revision differences
Document history
Date | By | Action |
---|---|---|
2020-01-21
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'This document obsoletes RFC 2960 and RFC 3309. It describes the Stream Control Transmission Protocol … Received changes through RFC Editor sync (changed abstract to 'This document obsoletes RFC 2960 and RFC 3309. It describes the Stream Control Transmission Protocol (SCTP). SCTP is designed to transport Public Switched Telephone Network (PSTN) signaling messages over 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 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. [STANDARDS-TRACK]') |
2015-10-14
|
(System) | Notify list changed from tsvwg-chairs@ietf.org, rrs@cisco.com to (None) |
2008-11-05
|
(System) | Posted related IPR disclosure: Comcast IP Holdings I, LLC's Statement about IPR related to RFC 3953, RFC 4415, RFC 4759, RFC 4769 … |
2007-09-26
|
Amy Vezza | State Changes to RFC Published from RFC Ed Queue by Amy Vezza |
2007-09-26
|
Amy Vezza | [Note]: 'RFC 4960' added by Amy Vezza |
2007-09-21
|
(System) | RFC published |