RFC 8845: Framework for Telepresence Multi-Streams
In plain English — editorial summary, not part of the RFC
This document defines a framework for a protocol to enable devices in a telepresence conference to interoperate. The protocol enables communication of information about multiple media streams so a sending system and receiving system can make reasonable decisions about transmitting, selecting, and rendering the media streams. This protocol is used in addition to SIP signaling and Session Description Protocol (SDP) negotiation for setting up a telepresence session.
Document record
- Document ID
- RFC8845
- Published
- January 2021
- Authors
- M. Duckworth; A. Pepperell; S. Wenger
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 61
- 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 8847Protocol for Controlling Multiple Streams for Telepresence (CLUE)Current
January 2021
- RFC 8850Controlling Multiple Streams for Telepresence (CLUE) Protocol Data ChannelCurrent
January 2021
- RFC 8866SDP: Session Description ProtocolCurrent
January 2021
- RFC 8870Encrypted Key Transport for DTLS and Secure RTPCurrent
January 2021
- RFC 8871A Solution Framework for Private Media in Privacy-Enhanced RTP Conferencing (PERC)Current
January 2021
- RFC 8723Double Encryption Procedures for the Secure Real-Time Transport Protocol (SRTP)Current
April 2020
- RFC 9185DTLS Tunnel between a Media Distributor and Key Distributor to Facilitate Key ExchangeCurrent
April 2022
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?