RFC 7478: Web Real-Time Communication Use Cases and Requirements
In plain English — editorial summary, not part of the RFC
This document describes web-based real-time communication use cases. Requirements on the browser functionality are derived from the use cases. This document was developed in an initial phase of the work with rather minor updates at later stages. It has not really served as a tool in deciding features or scope for the WG's efforts so far. It is being published to record the early conclusions of the WG. It will not be used as a set of rigid guidelines that specifications and implementations will be held to in the future.
Document record
- Document ID
- RFC7478
- Published
- March 2015
- Authors
- C. Holmberg; S. Hakansson; G. Eriksson
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 28
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7667RTP TopologiesCurrent
November 2015
- RFC 7675Session Traversal Utilities for NAT (STUN) Usage for Consent FreshnessCurrent
October 2015
- RFC 7201Options for Securing RTP SessionsCurrent
April 2014
- RFC 7875Additional WebRTC Audio Codecs for InteroperabilityCurrent
May 2016
- RFC 8828WebRTC IP Address Handling RequirementsCurrent
January 2021
- RFC 8829JavaScript Session Establishment Protocol (JSEP)Obsoleted
January 2021
- RFC 8860Sending Multiple Types of Media in a Single RTP SessionCurrent
January 2021
- RFC 9134RTP Payload Format for ISO/IEC 21122 (JPEG XS)Current
October 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?