You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While WebCodecs provides low-level access to the browser's native encoders and decoders, today there is no API to transport media peer-to-peer using the Real-time Transport Protocol (RTP), defined in RFC 3550.
The goal of the RtpTransport API is to enable applications to utilize peer-to-peer RTP transport, as well as to send and respond to feedback using the Real-time Control Protocol (RTCP).
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 meeting organizers may also update the description, 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 meeting organizers endeavor to schedule all proposed sessions that are in scope for a breakout. Actual scheduling should take place shortly before the meeting.
RtpTransport is a great idea to let others to do customization.
What is the differences between RtpTransport and WebTransport from the transportation layer. If Congestion control algorithm could be injected.
Session description
While WebCodecs provides low-level access to the browser's native encoders and decoders, today there is no API to transport media peer-to-peer using the Real-time Transport Protocol (RTP), defined in RFC 3550.
The goal of the RtpTransport API is to enable applications to utilize peer-to-peer RTP transport, as well as to send and respond to feedback using the Real-time Control Protocol (RTCP).
The following use cases are being developed:
See:
Session goal
To describe the goals of the RtpTransport API, and to solicit feedback on developer needs and use cases.
Additional session chairs (Optional)
@pthatcher, @sprangerik
Who can attend
Anyone may attend (Default)
IRC channel (Optional)
#rtp-transport
Other sessions where we should avoid scheduling conflicts (Optional)
No response
Instructions for meeting planners (Optional)
Request scheduling at 10:00 (for remote attendees in Europe)
Large room capacity (e.g. 48, California A ) if possible
Remote participation should be supported (Peter Thatcher and Bernard Aboba will be remote).
Agenda for the meeting.
Links to calendar
Meeting materials
The text was updated successfully, but these errors were encountered: