{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2026,4,29]],"date-time":"2026-04-29T22:33:26Z","timestamp":1777502006871,"version":"3.51.4"},"reference-count":27,"publisher":"Association for Computing Machinery (ACM)","issue":"1","license":[{"start":{"date-parts":[[2021,2,28]],"date-time":"2021-02-28T00:00:00Z","timestamp":1614470400000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/www.acm.org\/publications\/policies\/copyright_policy#Background"}],"content-domain":{"domain":["dl.acm.org"],"crossmark-restriction":true},"short-container-title":["Queue"],"published-print":{"date-parts":[[2021,2,28]]},"abstract":"<jats:p>In this time of pandemic, the world has turned to Internet-based, RTC (realtime communication) as never before. The number of RTC products has, over the past decade, exploded in large part because of cheaper high-speed network access and more powerful devices, but also because of an open, royalty-free platform called WebRTC. WebRTC is growing from enabling useful experiences to being essential in allowing billions to continue their work and education, and keep vital human contact during a pandemic. The opportunities and impact that lie ahead for WebRTC are intriguing indeed.<\/jats:p>","DOI":"10.1145\/3454122.3457587","type":"journal-article","created":{"date-parts":[[2021,3,16]],"date-time":"2021-03-16T22:05:24Z","timestamp":1615932324000},"page":"77-93","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":11,"title":["WebRTC - Realtime Communication for the Open Web Platform"],"prefix":"10.1145","volume":"19","author":[{"given":"Niklas","family":"Blum","sequence":"first","affiliation":[{"name":"Google"}]},{"given":"Serge","family":"Lachapelle","sequence":"additional","affiliation":[{"name":"Google"}]},{"given":"Harald","family":"Alvestrand","sequence":"additional","affiliation":[{"name":"Google"}]}],"member":"320","published-online":{"date-parts":[[2021,3,16]]},"reference":[{"key":"e_1_2_1_1_1","series-title":"April 1","volume-title":"Improving audio quality in Duo with WaveNetEQ. Google AI Blog","author":"Barrera P.","year":"2020","unstructured":"Barrera, P., Stimberg, F. 2020. Improving audio quality in Duo with WaveNetEQ. Google AI Blog (April 1); https:\/\/ai.googleblog.com\/2020\/04\/improving-audio-quality-in-duo-with.html."},{"key":"e_1_2_1_2_1","doi-asserted-by":"crossref","unstructured":"Baugher M. McGrew D. Naslund M. Carrara E. Norrman K. 2004. The Secure Real-time Transport Protocol (SRTP) IETF RFC 3711; https:\/\/tools.ietf.org\/html\/rfc3711.","DOI":"10.17487\/rfc3711"},{"key":"e_1_2_1_3_1","series-title":"December 8","volume-title":"WebRTC technologies prove to be essential during pandemic. IETF interview with Adam Roach","author":"Gross G.","unstructured":"Gross, G. 2020. WebRTC technologies prove to be essential during pandemic. IETF interview with Adam Roach (December 8); https:\/\/www.ietf.org\/blog\/webrtc-pandemic\/."},{"key":"e_1_2_1_4_1","unstructured":"Holmer S. Lundin H. Carlucci G. De Cicco L. Mascolo S.; H. Alvestrand ed. 2015. A Google congestion control algorithm for real-time communication; https:\/\/tools.ietf.org\/html\/draft-alvestrand-rmcat-congestion-03."},{"key":"e_1_2_1_5_1","unstructured":"IETF. Real-time communication in Web-browsers (RTCWeb) working group; https:\/\/datatracker.ietf.org\/wg\/rtcweb\/documents\/."},{"key":"e_1_2_1_6_1","unstructured":"IETF. 2021. WebTransport (webtrans); https:\/\/datatracker.ietf.org\/wg\/webtrans\/about\/."},{"key":"e_1_2_1_7_1","volume-title":"The E-model: a computational model for use in transmission planning","author":"International Telecommunication Union T.","year":"2015","unstructured":"International Telecommunication Union-T. 2015. G.107: The E-model: a computational model for use in transmission planning; https:\/\/www.itu.int\/rec\/T-REC-G.107-201506-I\/en."},{"key":"e_1_2_1_8_1","unstructured":"Ivov E. 2020. This is what end-to-end encryption should look like! (April 12. Jitsi blog; https:\/\/jitsi.org\/blog\/e2ee\/."},{"key":"e_1_2_1_9_1","doi-asserted-by":"crossref","unstructured":"Petit-Huguenin M. Salgueiro G. Rosenberg J. Wing D. Mahy R. Matthews P. 2020. Session Traversal Utilities for NAT (STUN). IETF RFC 8489; https:\/\/tools.ietf.org\/html\/rfc8489.","DOI":"10.17487\/RFC8489"},{"key":"e_1_2_1_10_1","volume-title":"Google Meet noise cancellation is rolling out now?here's how it works. VentureBeat (June 8); https:\/\/venturebeat.com\/2020\/06\/08\/google-meet-noise-cancellation-ai-cloud-denoiser-g-suite\/.","author":"Protalinski E.","year":"2020","unstructured":"Protalinski, E. 2020. Google Meet noise cancellation is rolling out now?here's how it works. VentureBeat (June 8); https:\/\/venturebeat.com\/2020\/06\/08\/google-meet-noise-cancellation-ai-cloud-denoiser-g-suite\/."},{"key":"e_1_2_1_11_1","unstructured":"Reddy T. Johnston A. Matthews P. Rosenberg J. 2020. Traversal using relays around NAT (TURN): Relay extensions to session traversal utilities for NAT (STUN) IETF RFC 8656; https:\/\/tools.ietf.org\/html\/rfc8656."},{"key":"e_1_2_1_12_1","doi-asserted-by":"crossref","unstructured":"Rescorla E. N. Modadugu N. 2012. Datagram Transport Layer Security version 1.2. IETF RFC 6347; https:\/\/tools.ietf.org\/html\/rfc6347.","DOI":"10.17487\/rfc6347"},{"key":"e_1_2_1_13_1","doi-asserted-by":"crossref","unstructured":"Roach A. B. 2016. WebRTC video processing and codec requirements. IETF RFC 7742; https:\/\/tools.ietf.org\/html\/rfc7742.","DOI":"10.17487\/RFC7742"},{"key":"e_1_2_1_14_1","volume-title":"Workshop. 2010; http:\/\/rtc-web.alvestrand.com\/.","author":"Web","unstructured":"RTC-Web Workshop. 2010; http:\/\/rtc-web.alvestrand.com\/."},{"key":"e_1_2_1_15_1","doi-asserted-by":"crossref","unstructured":"Stewart R. Ed. 2007. Stream Control Transmission Protocol. IETF RFC 4960; https:\/\/tools.ietf.org\/html\/rfc4960.","DOI":"10.17487\/rfc4960"},{"key":"e_1_2_1_16_1","unstructured":"Valin J. M. Bran C. 2016. WebRTC audio codec and processing requirements. IETF RFC 7874; https:\/\/tools.ietf.org\/html\/rfc7874."},{"key":"e_1_2_1_17_1","series-title":"September 19","volume-title":"What is WebRTC?","author":"Web 0.","unstructured":"WebRTC for the Curious. 2020. What is WebRTC? (September 19); https:\/\/webrtcforthecurious.com\/docs\/01-what-why-and-how\/."},{"key":"e_1_2_1_18_1","unstructured":"WebRTC.org implementation. Google Git; https:\/\/webrtc.googlesource.com\/src\/."},{"key":"e_1_2_1_19_1","unstructured":"W3C. 2016. Streams API (November 29); https:\/\/www.w3.org\/TR\/streams-api\/."},{"key":"e_1_2_1_20_1","series-title":"December 15","volume-title":"Peer-to-peer Data API","unstructured":"W3C. 2020. Peer-to-peer Data API (December 15); https:\/\/www.w3.org\/TR\/webrtc\/#peer-to-peer-data-api."},{"key":"e_1_2_1_21_1","series-title":"December 15","volume-title":"RTCPeerConnection interface","unstructured":"W3C. 2020. RTCPeerConnection interface (December 15); https:\/\/www.w3.org\/TR\/webrtc\/#rtcpeerconnection-interface."},{"key":"e_1_2_1_22_1","unstructured":"W3C. 2020. WebCodecs (December 8); https:\/\/wicg.github.io\/web-codecs\/."},{"key":"e_1_2_1_23_1","series-title":"December 15","volume-title":"Real-time communication between browsers. W3C Proposed Recommendation","author":"Web 0","unstructured":"W3C. 2020. WebRTC 1.0: Real-time communication between browsers. W3C Proposed Recommendation (December 15); https:\/\/www.w3.org\/TR\/webrtc\/."},{"key":"e_1_2_1_24_1","series-title":"September 1","volume-title":"WebRTC insertable media using Streams","unstructured":"W3C. 2020. WebRTC insertable media using Streams (September 1); https:\/\/w3c.github.io\/webrtc-insertable-streams\/."},{"key":"e_1_2_1_25_1","series-title":"November 30","volume-title":"WebRTC Next Version use cases","unstructured":"W3C. 2020. WebRTC Next Version use cases (November 30); https:\/\/www.w3.org\/TR\/webrtc-nv-use-cases\/."},{"key":"e_1_2_1_26_1","unstructured":"W3C. 2020. WebTransport (December 9); https:\/\/w3c.github.io\/webtransport\/."},{"key":"e_1_2_1_27_1","unstructured":"W3C. 2021. Web Real-Time Communications working group; https:\/\/www.w3.org\/groups\/wg\/webrtc."}],"container-title":["Queue"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/3454122.3457587","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/3454122.3457587","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,17]],"date-time":"2025-06-17T20:47:51Z","timestamp":1750193271000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/3454122.3457587"}},"subtitle":["What was once a way to bring audio and video to the web has expanded into more use cases we could ever imagine."],"short-title":[],"issued":{"date-parts":[[2021,2,28]]},"references-count":27,"journal-issue":{"issue":"1","published-print":{"date-parts":[[2021,2,28]]}},"alternative-id":["10.1145\/3454122.3457587"],"URL":"https:\/\/doi.org\/10.1145\/3454122.3457587","relation":{},"ISSN":["1542-7730","1542-7749"],"issn-type":[{"value":"1542-7730","type":"print"},{"value":"1542-7749","type":"electronic"}],"subject":[],"published":{"date-parts":[[2021,2,28]]},"assertion":[{"value":"2021-03-16","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}