ObsoletedPROPOSED STANDARDIETF stream

RFC 7053: SACK-IMMEDIATELY Extension for the 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 9260Stream Control Transmission Protocol

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

This document updates RFC 4960 by defining a method for the sender of a DATA chunk to indicate that the corresponding Selective Acknowledgment (SACK) chunk should be sent back immediately and should not be delayed. It is done by specifying a bit in the DATA chunk header, called the (I)mmediate bit, which can get set by either the Stream Control Transmission Protocol (SCTP) implementation or the application using an SCTP stack. Since unknown flags in chunk headers are ignored by SCTP implementations, this extension does not introduce any interoperability problems.

Document record

Document ID
RFC7053
Published
November 2013
Authors
M. Tuexen; I. Ruengeler; R. Stewart
Status
PROPOSED STANDARD
Stream
IETF
Area
wit
Pages
8
Also known as
Obsoleted by:
RFC 9260
Updates:
RFC 4960

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/7053-sack-immediately-extension-for-the-stream-control-transmission-protocol