metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 4960: Stream Control Transmission Protocol

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9260.

Current document in this lineage: RFC 9260 — Stream Control Transmission Protocol

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC4960
Published
September 2007
Authors
R. Stewart
Status
PROPOSED STANDARD
Stream
IETF
Area
wit
Pages
152
Also known as
—
Obsoletes:
RFC 2960, RFC 3309
Obsoleted by:
RFC 9260
Updated by:
RFC 6096, RFC 6335, RFC 7053, RFC 8899

Topics

Standards lineage

This document is one revision in a chain of 8 RFCs, each formally replacing the one before it.

  1. RFC 2960 (2000)
  2. RFC 3309 (2002)
  3. RFC 4460 (2006)
  4. RFC 4960 (2007)
  5. RFC 6096 (2011)
  6. RFC 7053 (2013)
  7. RFC 8540 (2019)
  8. RFC 9260 (2022) ✓

Read the full history of Stream Control Transmission Protocol →

Referenced by

5 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/4960-stream-control-transmission-protocol