W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2014

Server-oriented stack (Was: Summary (updated)...)

From: Emil Ivov <emcho@jitsi.org>
Date: Wed, 29 Jan 2014 15:35:36 +0100
Message-ID: <CAPvvaaLu37XgUQN8cHPCbxgmw0idUULQyi_GsFO5yM6BxcuQeg@mail.gmail.com>
To: Justin Uberti <juberti@google.com>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
Hey all,

On Wed, Jan 29, 2014 at 3:25 AM, Justin Uberti <juberti@google.com> wrote:
>
> Missing server-oriented version of WebRTC
> Multiparty, recording, broadcast

I was wondering if we had a plan as to how exactly we were going to
take on these two (if at all). The reason I am asking is because I
think we might already have most of the components in place within the
Jitsi community (FOSS):

* media stack and srtp support with libjitsi (with DTLS from bouncycastle)
* ICE support with ice4j.org
* a video router (SFU) with Jitsi Videobridge

The one part that's currently missing is recording ... but we
shouldn't be long...

None of the above components rely on any part of the existing
webrtc.org stack, which should also address the interoperability
concerns that otherwise arise with the dominance of  single RI.

(FWIW, I do agree that working on formally specifying any part of the
server-side APIs here would be rather out of scope)

Emil

--
https://jitsi.org
Received on Wednesday, 29 January 2014 14:36:25 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:38 UTC