RFC 6096: Stream Control Transmission Protocol (SCTP) Chunk Flags Registration
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 defines the procedure for registering chunk flags with the Internet Assigned Numbers Authority (IANA) for the Stream Control Transmission Protocol (SCTP). It updates RFC 4960 and also defines the IANA registry for contents for currently defined chunk types. It does not change SCTP in any other way. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6096
- Published
- January 2011
- Authors
- M. Tuexen; R. Stewart
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 8
- Also known as
- —
Standards lineage
This document is one revision in a chain of 8 RFCs, each formally replacing the one before it.
- RFC 2960 (2000)
- RFC 3309 (2002)
- RFC 4460 (2006)
- RFC 4960 (2007)
- RFC 6096 (2011)
- RFC 7053 (2013)
- RFC 8540 (2019)
- 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.
- RFC 6093On the Implementation of the TCP Urgent MechanismObsoleted
January 2011
- RFC 6083Datagram Transport Layer Security (DTLS) for Stream Control Transmission Protocol (SCTP)Updated
January 2011
- RFC 6069Making TCP More Robust to Long Connectivity Disruptions (TCP-LCD)Current
December 2010
- RFC 6056Recommendations for Transport-Protocol Port RandomizationCurrent
January 2011
- RFC 6040Tunnelling of Explicit Congestion NotificationUpdated
November 2010
- RFC 6016Support for the Resource Reservation Protocol (RSVP) in Layer 3 VPNsCurrent
October 2010
- RFC 6191Reducing the TIME-WAIT State Using TCP TimestampsCurrent
April 2011
- RFC 5961Improving TCP's Robustness to Blind In-Window AttacksUpdated
August 2010
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?