W3C home > Mailing lists > Public > public-webrtc@w3.org > June 2018

Re: To Stream or not to Stream

From: Peter Thatcher <pthatcher@google.com>
Date: Mon, 18 Jun 2018 01:59:21 -0700
Message-ID: <CAJrXDUF9EiK+fvX2Xu8+f5uQsQdnymkRtfwcuS5VvGCEkCYPyw@mail.gmail.com>
To: Alexandre GOUAILLARD <agouaillard@gmail.com>
Cc: Göran Eriksson AP <goran.ap.eriksson@ericsson.com>, Bernard Aboba <Bernard.Aboba@microsoft.com>, youenn fablet <yfablet@apple.com>, Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Thanks for the info.  I'll add millicast.com as an example to the uses
cases slides.

Will you be at the f2f?  It would be nice to have someone that can speak in
detail about this use case.

Lastly, could you give a few requirements?   So far I have the following,
but it seems incomplete:

- Media protocol is easy to terminate on a server.  Ideally, allow app to
control the wire format and transport to match existing server
infrastructure
- App has advanced control over retransmissions and FEC
- App has advanced control over jitter buffer


On Mon, Jun 18, 2018 at 6:48 AM Alexandre GOUAILLARD <agouaillard@gmail.com>
wrote:

> if there is enough interest,
> we (cosmo) can provide feedback during the meting about "millicast.com",
> a webrtc-based platform for "live broadcast".
> we did a state of the art of existing solutions, spoke with HLS authors
> from Apple, limelight CDN, akamai, centurylong, venison digital (ex edge
> cast CDN) and so on and so forth.
>
> two blog posts about webrtc in real-time streaming:
>
> http://webrtcbydralex.com/index.php/2018/05/15/streaming-protocols-and-ultra-low-latency-including-webrtc/
>
> http://webrtcbydralex.com/index.php/2018/06/08/using-webrtc-as-a-replacement-for-rtmp/
>
> On Sat, Jun 16, 2018 at 12:04 AM, Göran Eriksson AP <
> goran.ap.eriksson@ericsson.com> wrote:
>
>>
>>
>>
>>
>> Den 2018-06-15 23:57 skrev "Bernard Aboba" <Bernard.Aboba@microsoft.com>
>> följande:
>>
>>
>>
>>     "The place where convergence is more likely to be important is with
>> live broadcasts since that's closer to needing "real-time"."
>>
>>
>>
>> +1.
>>
>>
>>
>> I just want to also mention the 1-way webrtc usages out there as well
>> today, such as screen sharing but also Iot cases such as drones with
>> cameras and surveillance systems.
>>
>>
>>
>> Here the requirements on delay is not as stringent as person-to-person
>> communication (often at least) and the added delay induced by a custom
>> component may well be worthwhile given the added value that component
>> provide. Here a QUIC based transport option in WebRTC.NV for upstreaming
>> media would be nice to have.
>>
>>
>>
>
>
> --
> Alex. Gouaillard, PhD, PhD, MBA
>
> ------------------------------------------------------------------------------------
> President - CoSMo Software Consulting, Singapore
>
> ------------------------------------------------------------------------------------
> sg.linkedin.com/agouaillard
>
>    -
>
>
Received on Monday, 18 June 2018 08:59:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:42 UTC