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

Re: [rtcweb] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.

From: Hrishikesh Kulkarni <rishi@turtleyogi.com>
Date: Tue, 23 Jul 2013 01:28:24 +0530
Message-ID: <CALFWOz4YL3wOC_03QBKrQ=NTBpZ_eW5pfHm+by9CL1sSVauqig@mail.gmail.com>
To: tim panton <thp@westhawk.co.uk>
Cc: Roman Shpount <roman@telurix.com>, XMPP Jingle <jingle@xmpp.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>, public-webrtc@w3.org
Yes. It took some effort on our server side for us to support Firefox with
DTLS (still incomplete) as compared to Chrome with vanilla signaling. I
believe we have long way to build interop in browsers: RTP, JS API and
maybe Signaling (with webserver). ScreenSharing policy is yet to be

I see this discussion is stuck at JS API vs JS SDP API, while equally
important standards like screensharing policy are in queue.


On Mon, Jul 22, 2013 at 11:49 PM, tim panton <thp@westhawk.co.uk> wrote:

> On 22 Jul 2013, at 18:45, Roman Shpount <roman@telurix.com> wrote:
> On Mon, Jul 22, 2013 at 1:00 PM, Philipp Hancke <fippo@goodadvice.pages.de
> > wrote:
>> I said this before, but since you insist on repeating your argument i'll
>> repeat mine: I have running code doing exactly that.
>> It's hard work and there are some points where this is PITA, I have
>> discovered numerous bugs in chrome (and the jingle spec) along the way, but
>> it's certainly not unfeasible.
> Out of curiosity, does the same code work with Firefox?
> As far as Phono is concerned - yes - but we had to do some work to make
> that happen, more
> work in fact than adding DTLS on the server side, which is (frankly)
> absurd.
> T.
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
Received on Thursday, 25 July 2013 10:44:16 UTC

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