RFC 8847: Protocol for Controlling Multiple Streams for Telepresence (CLUE)
In plain English — editorial summary, not part of the RFC
The Controlling Multiple Streams for Telepresence (CLUE) protocol is an application protocol conceived for the description and negotiation of a telepresence session. The design of the CLUE protocol takes into account the requirements and the framework defined within the IETF CLUE Working Group. A companion document, RFC 8848, delves into CLUE signaling details as well as the SIP / Session Description Protocol (SDP) session establishment phase. CLUE messages flow over the CLUE data channel, based on reliable and ordered SCTP-over-DTLS transport. ("SCTP" stands for "Stream Control Transmission Protocol".) Message details, together with the behavior of CLUE Participants acting as Media Providers and/or Media Consumers, are herein discussed.
Document record
- Document ID
- RFC8847
- Published
- January 2021
- Authors
- R. Presta; S P. Romano
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- art
- Pages
- 62
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8846An XML Schema for the Controlling Multiple Streams for Telepresence (CLUE) Data ModelCurrent
January 2021
- RFC 6518Keying and Authentication for Routing Protocols (KARP) Design GuidelinesCurrent
February 2012
- RFC 8845Framework for Telepresence Multi-StreamsCurrent
January 2021
- RFC 8850Controlling Multiple Streams for Telepresence (CLUE) Protocol Data ChannelCurrent
January 2021
- RFC 8833Application-Layer Protocol Negotiation (ALPN) for WebRTCCurrent
January 2021
- RFC 8907The Terminal Access Controller Access-Control System Plus (TACACS+) ProtocolUpdated
September 2020
- RFC 8924Service Function Chaining (SFC) Operations, Administration, and Maintenance (OAM) FrameworkCurrent
October 2020
- RFC 8999Version-Independent Properties of QUICUpdated
May 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?