A room, its relay and its room service.
- The public room: up to four people publish their camera and microphone while others watch, and a viewer seeks back through the last fifteen minutes and checks what it fetches as it checks what arrives live.
- The relay: Media over QUIC Transport at drafts 22, 18 and 16, over QUIC, WebTransport or a WebSocket binding. It fans each object out with its receipts, and forwards the receipts of the objects it drops.
- The room service: it signs the room's descriptor and its lifecycle on the room's clock, and issues grants over HTTP, each for a key that never leaves the visitor's device.
Answering now at wai.transaction.science
-
The public room
https://wai.transaction.science/room/Open it in a browser to publish your camera and microphone, or to watch.
-
The relay
wss://wai.transaction.science/moqMedia over QUIC over the WebSocket binding, subprotocol moqt-22.
-
The room service
https://wai.transaction.science/room-api/GET room gives the signed room; POST grant, with your page's Ed25519 public key, gives a grant for it.
Open the room, or call its service.
-
Open the public room and allow the camera and microphone, or join as a viewer.
-
Read the room from the room service: its signed descriptor, its composition and the grants of the people in it.
curl https://wai.transaction.science/room-api/room -
Read the room service's HTTP interface, and the relay's transports and receipts.
The open components it is built from.
Each is in the WAI standard, with its reference implementation in the open-standards repository; its notes are the WAI status page's.
-
Rooms: a signed descriptor that fixes a room and its roles, and grants under which each participant takes part, exchanged on the room clock, revoked through the key log and honoured only beside a proof of their key.
Notes How a principal obtains a grant, and how a ceiling is held while a session runs, are the deployment's. Several of its bindings follow Internet-Drafts, which may still change.
-
Media over QUIC Transport, drafts 22, 18 and 16, chosen per session: a relay that fans each object out in priority order with its receipts, a room service, and a browser client that checks every object against its receipt before it decodes it.
Notes Drafts do not interoperate with each other, so a session is one draft from its first byte to its last; the relay maps drafts 23, 18 and 16 onto draft 22's model and names what one draft can say and another cannot, and the extension's envelopes, receipts and catalog fields are the same on each. Runs against other implementations' relays and clients are recorded, with their date and every result, in the codec's README. The browser client speaks draft 22 unless a page asks it for draft 23, and the public room reaches its relay over the WebSocket binding.
-
Live events: every cue, chat message, reaction, poll, marker, caption, decision and lifecycle change is one record, signed by its sender and chained to that sender's previous one.
Notes An event's time is its author's claim: a verifier checks that one author's times never go back. Events are signed, not encrypted.
-
WHIP into a room's tracks and WHEP out of them, each frame an envelope on a MoQ track and every object verified against its receipt.
-
Composition as an integer function of a signed descriptor, so every viewer's device lays the room out the same way and a server compositor's output can be checked.
Notes The layout fixes rectangles, not pixels: how a renderer scales a source into its rectangle is its own.
-
Live captions that carry their origin: typed by a person, made by a machine, or made and reviewed.
-
A participant's full-quality recording bound to the room while it is captured, so its upload proves it is one continuous take.
Notes A take commits to its bytes, whatever codec and container they hold. Its C2PA live video provenance is the live provenance extension's, which writes it.
-
Recordings of a session as one package, and clips that carry a proof that their bytes are exactly those of a take.
-
Seeking back in a live room: a window of the room's tracks kept on the relay with their receipts, fetched only under a grant with the seek power, and every object in it checked as a live one is.
Notes The public demonstration room keeps a fifteen-minute window.
-
A review policy signed by the room authority, and decisions that withhold an item, never replace it.
Notes How a moderator or a classifier reaches a verdict, and how a notice reaches the room authority, are outside the text.
-
Admission by an age threshold without identity: a token says only that its holder is at or over the room's age, and the relay serves each rated track by it.
Notes Where a regime asks for a lawful basis, the operator states it. Its scope over MoQ follows an Internet-Draft, which may still change.
-
A record signed by every hop of what it carried and dropped and its energy with its acquisition class, and a room-session receipt that a verifier recomputes from those records.
Notes The reference relay signs its record with the unmetered marker. Prices, billing and holding a ceiling while a session runs are the deployment's.
-
Steering each client to the pathway with the fewest joules per delivered byte within the operator's limits, decided from the hops' signed records and recomputable by anyone who holds them.
Notes A steering server's network service is described only by its inputs and its output.
-
End-to-end encrypted rooms: every media object sealed by its publisher, keyed from one MLS group per room whose membership follows the room's grants.
Notes Members run natively in the reference crates and, built for WebAssembly, in a browser page, and the reference room service carries a room's MLS messages. Events, catalogs and receipts stay in the clear. The secure-objects and MLS keying texts it follows are Internet-Drafts, the keying one an individual draft, which may still change. The construction the specification named before this revision is withdrawn.
-
End-to-end encrypted rooms in the browser: a page is a member of the room's group, every key in the page's memory and nowhere else.
-
Relay preservation: envelopes and receipts forwarded byte for byte, with no transcoding, rewriting or re-signing.
Notes A relay attests in a separate, parallel receipt.