RFC 7205: Use Cases for Telepresence Multistreams
In plain English — editorial summary, not part of the RFC
Telepresence conferencing systems seek to create an environment that gives users (or user groups) that are not co-located a feeling of co-located presence through multimedia communication that includes at least audio and video signals of high fidelity. A number of techniques for handling audio and video streams are used to create this experience. When these techniques are not similar, interoperability between different systems is difficult at best, and often not possible. Conveying information about the relationships between multiple streams of media would enable senders and receivers to make choices to allow telepresence systems to interwork. This memo describes the most typical and important use cases for sending multiple streams in a telepresence conference.
Document record
- Document ID
- RFC7205
- Published
- April 2014
- Authors
- A. Romanow; S. Botzko; M. Duckworth; R. Even
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- art
- Pages
- 17
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7206Requirements for an End-to-End Session Identification in IP-Based Multimedia Communication NetworksCurrent
May 2014
- RFC 7198Duplicating RTP StreamsCurrent
April 2014
- RFC 7197Duplication Delay Attribute in the Session Description ProtocolCurrent
April 2014
- RFC 7195Session Description Protocol (SDP) Extension for Setting Audio and Video Media Streams over Circuit-Switched Bearers in the Public Switched Telephone Network (PSTN)Current
May 2014
- RFC 7239Forwarded HTTP ExtensionCurrent
June 2014
- RFC 7243RTP Control Protocol (RTCP) Extended Report (XR) Block for the Bytes Discarded MetricCurrent
May 2014
- RFC 7244RTP Control Protocol (RTCP) Extended Report (XR) Blocks for Synchronization Delay and Offset Metrics ReportingCurrent
May 2014
- RFC 7245An Architecture for Media Recording Using the Session Initiation ProtocolCurrent
May 2014
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?