|Original author(s)||Justin Uberti|
1.0 / May 4, 2018
WebRTC (Web Real-Time Communication) is a free and open-source project providing web browsers and mobile applications with real-time communication (RTC) via simple application programming interfaces (APIs). It allows audio and video communication to work inside web pages by allowing direct peer-to-peer communication, eliminating the need to install plugins or download native apps. Supported by Apple, Google, Microsoft, Mozilla, and Opera, WebRTC specifications have been published by the World Wide Web Consortium (W3C) and the Internet Engineering Task Force (IETF).
According to the webrtc.org website, the purpose of the project is to "enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols".
In May 2010, Google bought Global IP Solutions or GIPS, a VoIP and videoconferencing software company that had developed many components required for RTC, such as codecs and echo cancellation techniques. Google open-sourced the GIPS technology and engaged with relevant standards bodies at the IETF and W3C to ensure industry consensus. In May 2011, Google released an open-source project for browser-based real-time communication known as WebRTC. This has been followed by ongoing work to standardize the relevant protocols in the IETF and browser APIs in the W3C.
In January 2011, Ericsson Labs built the first implementation of WebRTC using a modified WebKit library. In October 2011, the W3C published its first draft for the spec. WebRTC milestones include the first cross-browser video call (February 2013), first cross-browser data transfers (February 2014), and as of July 2014 Google Hangouts was "kind of" using WebRTC.
The W3C draft API was based on preliminary work done in the WHATWG. It was referred to as the ConnectionPeer API, and a pre-standards concept implementation was created at Ericsson Labs. The WebRTC Working Group expects this specification to evolve significantly based on:
- Outcomes of ongoing exchanges in the companion RTCWEB group at IETF to define the set of protocols that, together with this document, define real-time communications in web browsers. While no one signaling protocol is mandated, SIP over WebSockets (RFC 7118) is often used partially due to the applicability of SIP to most of the envisaged communication scenarios as well as the availability of open-source software such as JsSIP.
- Privacy issues that arise when exposing local capabilities and local streams
- Technical discussions within the group, on implementing data channels in particular
- Experience gained through early experimentation
- Feedback from other groups and individuals
In November 2017, the WebRTC 1.0 specification transitioned from Working Draft to Candidate Recommendation.
getUserMediaacquires the audio and video media (e.g., by accessing a device's camera and microphone).
RTCPeerConnectionenables audio and video communication between peers. It performs signal processing, codec handling, peer-to-peer communication, security, and bandwidth management.
RTCDataChannelallows bidirectional communication of arbitrary data between peers. It uses the same API as WebSockets and has very low latency.
The WebRTC API also includes a statistics function:
getStatsallows the web application to retrieve a set of statistics about WebRTC sessions. These statistics data are being described in a separate W3C document.
The WebRTC API includes no provisions for signaling, that is discovering peers to connect to and determine how to establish connections among them. Applications use Interactive Connectivity Establishment for connections and somehow manage sessions, possibly relying on any of Session Initiation Protocol, Extensible Messaging and Presence Protocol, Message Queuing Telemetry Transport, Matrix, or another protocol. Signaling may depend on one or more servers.
RFC 7874 requires implementations to provide PCMA/PCMU (RFC 3551), Telephone Event as DTMF (RFC 4733), and Opus (RFC 6716) audio codecs as minimum capabilities. The PeerConnection, data channel and media capture browser APIs are detailed in the W3C.
W3C is developing ORTC (Object Real-Time Communications) for WebRTC.
Although initially developed for web browsers, WebRTC has applications for non-browser devices, including mobile platforms and IoT devices. Examples include browser-based VoIP telephony, also called cloud phones or web phones, which allow calls to be made and received from within a web browser, replacing the requirement to download and install a softphone.
WebRTC is supported by the following browsers:
- Desktop PC
- Google Chrome 28+ (enabled by default since 29)
- Mozilla Firefox 24+
- Opera Mobile 12+
- Chrome OS
- Firefox OS
- BlackBerry 10
- MobileSafari/WebKit (iOS 11+)
- Tizen 3.0
In January 2015, TorrentFreak reported a serious security flaw in browsers that support WebRTC, saying that it compromised the security of VPN tunnels by exposing the true IP address of a user. The IP address read requests are not visible in the browser's developer console, and they are not blocked by most ad blocking/privacy/security add-ons, enabling online tracking by advertisers and other entities despite precautions (however the uBlock Origin add-on can fix this problem). As of September 2019, this WebRTC flaw still surfaces on Firefox 69.x and still by default exposes the user's internal IP address to the web.
- Global IP Solutions (GIPS)
- Real-time Transport Protocol (RTP)
- Session Description Protocol (SDP)
- WebRTC Gateway
- "WebRTC 1.0: Real-time Communication Between Browsers". World Wide Web Consortium. 27 September 2018. Retrieved 25 March 2019.
- "Src/webrtc - Git at Google".
- How WebRTC Is Revolutionizing Telephony. Blogs.trilogy-lte.com (2014-02-21). Retrieved on 2014-04-11.
- "Web Real-Time Communications (WebRTC) transforms the communications landscape as it becomes a World Wide Web Consortium (W3C) Recommendation and Internet Engineering Task Force (IETF) standards". World Wide Web Consortium. 26 Jan 2021. Retrieved 27 Jan 2021.
- "Rtcweb Status Pages". tools.ietf.org. Retrieved 2021-02-18.
- "WebRTC". WebRTC. Archived from the original on 9 January 2018. Retrieved 6 February 2018.
- "Are the WebRTC components from Google's acquisition of Global IP Solutions?". WebRTC. Retrieved 6 February 2018.
- Wauters, Robin (18 May 2010). "Google makes $68.2 million cash offer for Global IP Solutions". TechCrunch. Retrieved 6 February 2018.
- Harald Alvestrand (2011-05-31). "Google release of WebRTC source code". email@example.com. Retrieved 2012-09-12.
- Charter of the Real-Time Communication in WEB-browsers (rtcweb) working group
- "WebRTC 1.0: Real-time Communication Between Browsers". W3.org. Retrieved 2012-09-12.
- "Beyond HTML5: Peer-to-Peer Conversational Video". Ericsson Research blog. Labs.ericsson.com. 25 January 2011. Archived from the original on 25 February 2017. Retrieved 21 March 2021.
- Stefan Håkansson; Stefan Ålund (26 May 2011). "Beyond HTML5: Experiment with Real-Time Communication in a Browser". Ericsson Research blog. Retrieved 6 February 2018.
- "WebRTC 1.0: Real-time Communication Between Browsers (W3C Working Draft 27 October 2011)". World Wide Web Consortium. 27 October 2011. Retrieved 6 February 2018.
- Nowak, Szymon. "WebRTC: So Much More Than Videoconferencing". GitHub. Retrieved 6 February 2018.
- "Introduction — HTML Standard". Whatwg.org. Retrieved 2012-09-12.
- "Rtcweb Status Pages". Tools.ietf.org. Retrieved 2012-09-12.
- "draft-jesup-rtcweb-data-protocol-00 - WebRTC Data Channel Protocol". Tools.ietf.org. Retrieved 2012-09-12.
- "WebRTC 1.0: Real-time Communication Between Browsers (W3C Candidate Recommendation 02 November 2017)". 2 November 2017.
- "Media Capture and Streams: getUserMedia". W3C. 2013-09-03. Retrieved 2014-01-15.
- "WebRTC: RTCPeerConnection Interface". W3C. 2013-09-10. Retrieved 2014-01-15.
- "WebRTC: RTCDataChannel". W3C. 2013-09-10. Retrieved 2014-01-15.
- "Identifiers for WebRTC's Statistics API". W3C. 2014-09-29.
- Tsahi Levent-Levi (13 April 2020). "WebRTC Server: What is it exactly?". BlogGeek.me.
- Tsahi Levent-Levi (13 November 2014). "Matrix.org and WebRTC: An Interview with Matthew Hodgson". BlogGeek.me.
- "W3C ORTC (Object Real-time Communications) Community Group".
- "Catch the Babelfish: Irish telco devises a new kind of cloud phone". November 2017.
- "ORTC API is now available in Microsoft Edge". Microsoft. 2015-09-18.
- Firefox Notes - Desktop. Mozilla.org (2013-06-25). Retrieved on 2014-04-11.
- "Safari 11.0". Apple Inc. Retrieved 6 June 2017.
- Opera News. blogs.opera.com (2013-11-19). Retrieved on 2015-09-17.
- Firefox Notes - Desktop. Mozilla.org (2013-09-17). Retrieved on 2014-08-04.
- "GStreamer 1.14 release notes". gstreamer.freedesktop.org. Retrieved 2019-12-19. since version 1.14
- Huge Security Flaw Leaks VPN Users’ Real IP-addresses TorrentFreak.com (2015-01-30). Retrieved on 2015-02-21.
- STUN IP Address requests for WebRTC Retrieved on 2015-02-21.
- Raymond Hill (26 March 2016). "Prevent WebRTC from leaking local IP address". uBlock Origin documentation. Retrieved 1 Sep 2016.
- Proust, S., ed. (May 2016). Additional WebRTC Audio Codecs for Interoperability. IETF. doi:10.17487/RFC7875. RFC 7875. Retrieved 2016-10-12.
- Valin, J. M.; Bran, C. (May 2016). WebRTC Audio Codec and Processing Requirements. IETF. doi:10.17487/RFC7874. RFC 7874. Retrieved 2016-10-12.
- Roach, A. B. (March 2016). WebRTC Video Processing and Codec Requirements. IETF. doi:10.17487/RFC7742. RFC 7742. Retrieved 2016-10-12.
- Perumal, M.; Wing, D.; Ravindranath, R.; Reddy, T.; Thomson, M. (October 2015). Session Traversal Utilities for NAT (STUN) Usage for Consent Freshness. IETF. doi:10.17487/RFC7675. RFC 7675. Retrieved 2016-10-12.
- Holmberg, C.; Hakansson, S.; Eriksson, G. (March 2015). Web Real-Time Communication Use Cases and Requirements. IETF. doi:10.17487/RFC7478. RFC 7478. Retrieved 2016-10-12.