Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RtpTransport #13

Open
aboba opened this issue Jul 9, 2024 · 2 comments
Open

RtpTransport #13

aboba opened this issue Jul 9, 2024 · 2 comments
Labels
session Breakout session proposal track: Real-time Web

Comments

@aboba
Copy link

aboba commented Jul 9, 2024

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.

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

Links to calendar

Meeting materials

@aboba aboba added the session Breakout session proposal label Jul 9, 2024
@tpac-breakout-bot
Copy link
Collaborator

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 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.

@fideltian
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
session Breakout session proposal track: Real-time Web
Projects
Status: No status
Development

No branches or pull requests

4 participants