CurrentPROPOSED STANDARDIETF stream

RFC 8260: Stream Schedulers and User Message Interleaving for the Stream Control Transmission Protocol

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

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.

Document record

Document ID
RFC8260
Published
November 2017
Authors
R. Stewart; M. Tuexen; S. Loreto; R. Seggelmann
Status
PROPOSED STANDARD
Stream
IETF
Area
wit
Pages
23
Also known as

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/8260-stream-schedulers-and-user-message-interleaving-for-the-stream-control-transmiss