RFC 8850: Controlling Multiple Streams for Telepresence (CLUE) Protocol Data Channel
In plain English — editorial summary, not part of the RFC
This document defines how to use the WebRTC data channel mechanism to realize a data channel, referred to as a Controlling Multiple Streams for Telepresence (CLUE) data channel, for transporting CLUE protocol messages between two CLUE entities.
Document record
- Document ID
- RFC8850
- Published
- January 2021
- Authors
- C. Holmberg
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- art
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8858Indicating Exclusive Support of RTP and RTP Control Protocol (RTCP) Multiplexing Using the Session Description Protocol (SDP)Current
January 2021
- RFC 8841Session Description Protocol (SDP) Offer/Answer Procedures for Stream Control Transmission Protocol (SCTP) over Datagram Transport Layer Security (DTLS) TransportCurrent
January 2021
- RFC 7345UDP Transport Layer (UDPTL) over Datagram Transport Layer Security (DTLS)Updated
August 2014
- RFC 8844Unknown Key-Share Attacks on Uses of TLS with the Session Description Protocol (SDP)Current
January 2021
- RFC 8843Negotiating Media Multiplexing Using the Session Description Protocol (SDP)Obsoleted
January 2021
- RFC 8842Session Description Protocol (SDP) Offer/Answer Considerations for Datagram Transport Layer Security (DTLS) and Transport Layer Security (TLS)Updated
January 2021
- RFC 8840A Session Initiation Protocol (SIP) Usage for Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (Trickle ICE)Updated
January 2021
- RFC 8865T.140 Real-Time Text Conversation over WebRTC Data ChannelsCurrent
January 2021
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?