Closed steely-glint closed 3 years ago
Yep, will do. I’ll add slides in the next couple of days
Thanks! T.
On 25 Nov 2020, at 19:01, Bernard Aboba notifications@github.com wrote:
Can you present the PR at the December 2 virtual interim? Slides are here:https://docs.google.com/presentation/d/17Z_vR4pOXn-9wthiqbM9GC7JE7vfbdNffEedBPqj1Mw/ https://docs.google.com/presentation/d/17Z_vR4pOXn-9wthiqbM9GC7JE7vfbdNffEedBPqj1Mw/ — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/w3c/webrtc-nv-use-cases/pull/68#issuecomment-733895299, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFODYDQ3EXLHVMZWCC4ZADSRVIBPANCNFSM4UCQ3ZRA.
No need to drop the millicast reference if we keep the use case and do not speak about specific implementation . I.e drop “datachannel”
Sent from my iPhone
On 3 Dec 2020, at 00:37, Tim Panton notifications@github.com wrote:
@steely-glint commented on this pull request.
In index.html:
NXX Ability to reuse DRM assets streamed over the data channels NXX Ability to reuse subtitle assets streamed over the data channels - Experience: Both |pipe| and millicast have built systems of this sort.
+ Thanks for the clarification. What I'm trying to indicate is that there is demand for this usecase, which we can't yet satisfy using the webRTC 1.0 spec. Both |pipe| and Millicast have (somewhat) solved these problems based on the current spec, albeit in a less than perfect way. Happy to drop the Millicast reference if you like.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
Can you present the PR at the December 2 virtual interim? Slides are here: https://docs.google.com/presentation/d/17Z_vR4pOXn-9wthiqbM9GC7JE7vfbdNffEedBPqj1Mw/