ObsoletedINFORMATIONALIETF stream

RFC 8540: Stream Control Transmission Protocol: Errata and Issues in RFC 4960

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 9260Stream Control Transmission Protocol

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

This document is a compilation of issues found since the publication of RFC 4960 in September 2007, based on experience with implementing, testing, and using the Stream Control Transmission Protocol (SCTP) along with the suggested fixes. This document provides deltas to RFC 4960 and is organized in a time-ordered way. The issues are listed in the order in which they were brought up. Because some text is changed several times, the last delta in the text is the one that should be applied. In addition to the deltas, a description of each problem and the details of the solution for each are also provided.

Document record

Document ID
RFC8540
Published
February 2019
Authors
R. Stewart; M. Tuexen; M. Proshin
Status
INFORMATIONAL
Stream
IETF
Area
wit
Pages
94
Also known as
Obsoleted by:
RFC 9260

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

One later RFC formally updates or obsoletes 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/8540-stream-control-transmission-protocol-errata-and-issues-in-rfc-4960