-
Notifications
You must be signed in to change notification settings - Fork 15
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
Multicast Receive API proposal #44
Comments
The DORMS proposal is quite interesting. Just to give an idea about a proposal we had years back is here. |
See follow-up discussion on the Chromium net-dev mailing list here. |
This work is continuing in the new Multicast Community Group, see the Charter . If this topic is of interest to you, please join the group. Details of an initial CG meeting on 23 June were posted here. |
Here are the minutes from the first Multicast CG meeting: https://www.w3.org/2021/06/23-multicast-minutes.html |
Jake (@GrumpyOldTroll) announced in October 2022 that he's stepping down from chairing the Multicast CG: https://lists.w3.org/Archives/Public/public-multicast/2022Oct/0000.html. This means no-one is currently driving this work. If there is interest to continue. please comment here and we'll follow up. But for now, I'll close this issue. |
I have just seen this Chromium Intent to Prototype. The proposal is for a source-specific multicast receive API, where large scale live video distribution is one of the primary use cases. Please refer to the Explainer for details. There is also a WICG Discourse Thread (from 2019).
This issue tracks a media-related issue/proposal/work item/discussion
The text was updated successfully, but these errors were encountered: