W3C home > Mailing lists > Public > public-webrtc@w3.org > December 2013

Re: What is missing for building "real" services?

From: Hutton, Andrew <andrew.hutton@unify.com>
Date: Fri, 27 Dec 2013 09:05:34 +0000
To: Victor Pascual <victor.pascual.avila@gmail.com>
CC: Emil Ivov <emcho@jitsi.org>, Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <03CC6A5B-FFAE-4B3F-BE80-EEAC1B09B580@siemens-enterprise.com>

I will be putting some effort in to trying to resolve the issues in the IETF that resulted in little progress in this area in 2013.

Mostly it is an IETF issue but it is for me one of the most pressing issues and one that has to be part of any so called WebRTC 1.0.


On 24 Dec 2013, at 09:32, "Victor Pascual" <victor.pascual.avila@gmail.com<mailto:victor.pascual.avila@gmail.com>> wrote:

Firewall/http-middlebox traversal -- we're experiencing issues in many enterprise deployments

Sent from my iPad

On Dec 22, 2013, at 11:41 AM, Emil Ivov <emcho@jitsi.org<mailto:emcho@jitsi.org>> wrote:

* stable multi-stream support (this is mostly for firefox and the android version of Chrome)
* support in IE, iOS and Safari

are the main issues that we've been seeing as adoption blockers.

--sent from my mobile

On 22 Dec 2013 08:52, "Stefan Håkansson LK" <stefan.lk.hakansson@ericsson.com<mailto:stefan.lk.hakansson@ericsson.com>> wrote:
During the telechat last Thursday some persons said that WebRTC is
sufficient to do demos, but not sufficient for building a "real" service
on top of.

I would really like to know more. If you can't build a service on top
off WebRTC I think we have failed. Would anyone care to expand a bit on
what is missing/wrongly designed? And explain the context/use-case.

Stefan (speaking for himself only)
Received on Friday, 27 December 2013 09:05:57 UTC

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