RFC 8848: Session Signaling for Controlling Multiple Streams for Telepresence (CLUE)
In plain English — editorial summary, not part of the RFC
This document is about Controlling Multiple Streams for Telepresence (CLUE) signaling. It specifies how the CLUE protocol and the CLUE data channel are used in conjunction with each other and with existing signaling mechanisms, such as SIP and the Session Description Protocol (SDP), to produce a telepresence call.
Document record
- Document ID
- RFC8848
- Published
- January 2021
- Authors
- R. Hanton; P. Kyzivat; L. Xiao; C. Groves
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- art
- Pages
- 29
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8849Mapping RTP Streams to Controlling Multiple Streams for Telepresence (CLUE) Media CapturesCurrent
January 2021
- RFC 8847Protocol for Controlling Multiple Streams for Telepresence (CLUE)Current
January 2021
- RFC 8850Controlling Multiple Streams for Telepresence (CLUE) Protocol Data ChannelCurrent
January 2021
- RFC 8846An XML Schema for the Controlling Multiple Streams for Telepresence (CLUE) Data ModelCurrent
January 2021
- RFC 8845Framework for Telepresence Multi-StreamsCurrent
January 2021
- RFC 8851RTP Payload Format RestrictionsCurrent
January 2021
- RFC 8844Unknown Key-Share Attacks on Uses of TLS with the Session Description Protocol (SDP)Current
January 2021
- RFC 8852RTP Stream Identifier Source Description (SDES)Current
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?