Low-level RTC Transport API

[tonyherre]

Session description

The WebRTC APIs have long enabled sending and receiving realtime media peer-to-peer with a streamlined control interface, but with limited ability to tune how media is encoded and interacts with the network. While APIs such as WebCodecs have begun to allow users low-level access to the browser's built-in encoders and decoders, there is still no API to allow similar levels of access to the low-latency peer-to-peer network transports like those used within an RTCPeerConnection.

The RtcTransport API aims to enable applications to directly utilize peer-to-peer datagram based transport for realtime media, controlling the details of congestion control and allowing arbitrary media encodings and formats. The current proposal is an evolution of the RTP-focussed transport discussed in a breakout session at TPAC 2024.

Session goal

To describe the goals of the RtcTransport API, and to solicit feedback on developer needs and use cases.

Additional session chairs (Optional)

@pthatcher, @alvestrand

Who can attend

Anyone may attend (Default)

Instructions for meeting planners (Optional)

No response

IRC channel (Optional)

#rtc-transport

Agenda for the meeting.

1. Introduction to the RtcTransport API
2. Use cases
3. Developer feedback

Scheduling conflicts to avoid (For meeting planners only)

No response

Links to calendar

• Wednesday, 11:15 - 12:15

[tpac-breakout-bot]

Thank you for proposing a session!

You may update the session description as needed and at any time before the meeting, but please keep in mind that tooling relies on issue formatting: follow the instructions and leave all headings and other formatting intact in particular.

Bots and W3C TPAC breakouts organizers may update the description at any time, to fix formatting issues or add links and other relevant information. Please do not revert these changes. Feel free to use comments to raise questions.

Do not expect formal approval; W3C TPAC breakouts organizers endeavor to schedule all proposed sessions that are in scope for a breakout. Actual scheduling should take place shortly before the meeting.