RFC 6458: Sockets API Extensions for the Stream Control Transmission Protocol (SCTP)
In plain English — editorial summary, not part of the RFC
This document describes a mapping of the Stream Control Transmission Protocol (SCTP) into a sockets API. The benefits of this mapping include compatibility for TCP applications, access to new SCTP features, and a consolidated error and event notification scheme. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6458
- Published
- December 2011
- Authors
- R. Stewart; M. Tuexen; K. Poon; P. Lei; V. Yasevich
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 115
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6429TCP Sender Clarification for Persist ConditionObsoleted
December 2011
- RFC 6411Applicability of Keying Methods for RSVP SecurityCurrent
October 2011
- RFC 6401RSVP Extensions for Admission PriorityCurrent
October 2011
- RFC 6525Stream Control Transmission Protocol (SCTP) Stream ReconfigurationCurrent
March 2012
- RFC 6528Defending against Sequence Number AttacksObsoleted
February 2012
- RFC 6354Forward-Shifted RTP Redundancy Payload SupportCurrent
August 2011
- RFC 6562Guidelines for the Use of Variable Bit Rate Audio with Secure RTPCurrent
March 2012
- RFC 6335Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number RegistryCurrent
August 2011
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?