Stream Schedulers and User Message Interleaving for the Stream Control Transmission Protocol
RFC 8260, “Stream Schedulers and User Message Interleaving for the Stream Control Transmission Protocol”, is a Proposed Standard document published in November 2017 by R. Stewart, M. Tuexen, S. Loreto, R. Seggelmann. The canonical text is published by the RFC Editor.
Abstract
The Stream Control Transmission Protocol (SCTP) is a message-oriented transport protocol supporting arbitrarily large user messages. This document adds a new chunk to SCTP for carrying payload data. This allows a sender to interleave different user messages that would otherwise result in head-of-line blocking at the sender. The interleaving of user messages is required for WebRTC data channels.
Whenever an SCTP sender is allowed to send user data, it may choose from multiple outgoing SCTP streams. Multiple ways for performing this selection, called stream schedulers, are defined in this document. A stream scheduler can choose to either implement, or not implement, user message interleaving.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8260 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8259 The JavaScript Object Notation Data Interchange Format
- RFC 8261 Datagram Transport Layer Security Encapsulation of SCTP Packets
- RFC 8258 Generalized SCSI: A Generic Structure for Interface Switching Capability Descriptor Switching Capability Specific Information
- RFC 8262 Content-ID Header Field in the Session Initiation Protocol
- RFC 8257 Data Center TCP : TCP Congestion Control for Data Centers
- RFC 8263 Group Domain of Interpretation GROUPKEY-PUSH Acknowledgement Message
- RFC 8256 Requirements for Hitless MPLS Path Segment Monitoring
- RFC 8264 PRECIS Framework: Preparation, Enforcement, and Comparison of Internationalized Strings in Application Protocols