RFC 8260
Stream Schedulers and User Message Interleaving for the Stream Control Transmission Protocol, November 2017
- File formats:
- Status:
- PROPOSED STANDARD
- Authors:
- R. Stewart
M. Tuexen
S. Loreto
R. Seggelmann - Stream:
- IETF
- Source:
- tsvwg (wit)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8260
Discuss this RFC: Send questions or comments to the mailing list tsvwg@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8260
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.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.