Tutorials Developer

Harald Alvestrand: Calling Without Installing Anything

By Infinite Creation · Profile

At a Glance

Making a video call used to mean installing something. WebRTC changed that by putting real-time media into the browser itself, specified openly and implemented by every major vendor. RFC 8825, the document that frames the whole architecture, was published in January 2021 with Alvestrand of Google as its sole author.

Lived: born 1959, Norwegian
Anchor year: 2021, WebRTC published as RFC 8825
Strand: overlooked

Career

The problem as it stood

Real-time communication on the web ran on plug-ins and proprietary clients. Each was a separate download, a separate security surface and a separate walled garden, and none of them talked to each other.

What he actually did

Alvestrand wrote the overview specification for browser-based real-time protocols and worked the standard through the IETF over a decade. An overview document is the piece that says how the other documents fit together, which is what makes a pile of specifications into an architecture.

How it worked

WebRTC is a stack rather than one protocol: media transport, encryption, congestion control, codec negotiation and connection establishment through firewalls. The browser implements it, so a page needs only JavaScript and permission from the user.

What it made possible

Every browser-based call, and the pandemic-era shift to video conferencing that assumed you could join a meeting from a link. Also broadcast contribution, remote production and low-latency streaming, which use the same transport for professional work.

Where the credit landed

WebRTC is the work of two standards bodies and dozens of engineers. RFC 8825 has one author on it, which understates the collective effort and overstates nothing about the individual: writing the document that holds an architecture together is a specific and demanding job.

Known For

Encryption is mandatory in WebRTC, not optional. That was a deliberate design decision.
The hard part is not media. It is getting a connection through two firewalls.
Browser implementation is why there is no download.

Knowledge Base

The Longer Answer

WebRTC is the point at which real-time media stops being a separate application.

Why an overview document matters

WebRTC is not one specification but a family of them, split across two standards bodies. Without a document explaining how they fit together, an implementer has no entry point and no way to know what is required. The overview is the least technical piece and often the most load-bearing.

Two bodies, one system

WebRTC is split between the IETF, which specifies the protocols on the wire, and the W3C, which specifies the interface a web page calls. Neither body could have produced it alone, and the division follows an old line: the network people define what travels, and the web people define what a document can ask for. Keeping those two halves aligned across a decade is most of what the work consisted of.

Where This Fits

WebRTC carries live calls in a browser, a modern transmission link in the chain followed in A History of Broadcast Technology.

FAQ

Q: Do I need a plug-in for WebRTC?
A: No. That is the point of it. The browser implements the media stack, so a page needs only JavaScript and the user's permission.

Q: Why is encryption mandatory?
A: Because it was specified that way. Making security optional means it is switched off under deadline pressure, so the standard removes the option.

Vocabulary

WebRTC A set of standards putting real-time voice, video and data into the browser without a plug-in. Specified jointly by the IETF for the protocols and the W3C for the browser interface, and implemented by every major browser.

Overview document A specification whose job is to explain how a family of other specifications fits together. It carries no protocol of its own and is often the only way a newcomer can enter a large standard at all.

Interactive connectivity establishment The procedure by which two devices behind firewalls find a path to each other, trying direct routes first and falling back to a relay. It is the least glamorous and most necessary part of any calling system.

Mandatory to implement A specification requirement that every conformant implementation must support, such as the Opus codec in WebRTC. It is how a standard guarantees that any two implementations can actually interoperate.

Sources

Every record below was fetched and read before it was cited here. Checked 26 August 2026.

RFC 8825, Overview: Real-Time Protocols for Browser-Based Applications. Standards Track, January 2021. The header names H. Alvestrand of Google as sole author. This is the document that frames the WebRTC architecture and points at the specifications that make it up.