Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Obsoletes:

RFC 2960,RFC 3309

Obsoleted by:

RFC 9260

Updated by:

RFC 6096,RFC 6335,RFC 7053,RFC 8899

Author:

R. Stewart, Ed.

Stream:

IETF

Source:

tsvwg (wit)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC4960

Discuss this RFC: Send questions or comments to the mailing listtsvwg@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 4960

Abstract

This document obsoletes RFC 2960 and RFC 3309. Itdescribes the Stream Control Transmission Protocol (SCTP). SCTP isdesigned to transport Public Switched Telephone Network (PSTN)signaling messages over IP networks, but is capable of broaderapplications.

SCTP is a reliable transport protocol operating on top of aconnectionless packet network such as IP. It offers the followingservices 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, withan option for order-of-arrival delivery of individual usermessages,

-- optional bundling of multiple user messages into a single SCTPpacket, and

-- network-level fault tolerance through supporting of multi-homingat either or both ends of an association.

The design of SCTP includes appropriate congestion avoidance behaviorand resistance to flooding and masquerade attacks. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.