W3C home > Mailing lists > Public > public-webrtc@w3.org > August 2012

RE: [rtcweb] Microsoft tells W3C and IETF what we are doing no signs of offering real world interoperability

From: Jim Barnett <Jim.Barnett@genesyslab.com>
Date: Tue, 7 Aug 2012 05:59:20 -0700
Message-ID: <E17CAD772E76C742B645BD4DC602CD81068E10E2@NAHALD.us.int.genesyslab.com>
To: "Alexey Aylarov" <alexey@zingaya.com>, "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Cc: <rtcweb@ietf.org>, <public-webrtc@w3.org>
It seems to me that this proposal is a continuation of a discussion that
the group has been having for a while over how much to bake into the
browser.  JSEP leaves more to the application than ROAP did, and now
this proposal suggests moving even more into the application.  It seems
to me that the trade-off is clear, and doesn't  involve "openness": the
less we bake into the browser, the more flexibility the app developer
has, and the more work he has to do.  (To link this back to another
discussion we've been having, it has been suggested that thoughtless
developers might miss-use constraints. It seems to me that a developer
who can't use constraints correctly is unlikely to code the ICE state
machine correctly. So, are we worried about that kind of developer or

Justin suggests that JSEP can provide the same flexibility that this
proposal does, at least to a sophisticated developer who understands how
to tweak it. Let's find out. I agree with Stefan that we should  draw up
a detailed list of differences and analyze them. At first glance, it
seems to me that many of the differences are independent of each other,
so that it is not a question of simply accepting or rejecting the entire
Microsoft proposal.

- Jim  

-----Original Message-----
From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf
Of Alexey Aylarov
Sent: Monday, August 06, 2012 1:11 PM
To: Cullen Jennings (fluffy)
Cc: rtcweb@ietf.org ; public-webrtc@w3.org
Subject: Re: [rtcweb] Microsoft tells W3C and IETF what we are doing no
signs of offering real world interoperability

It was easy to expect from company which tries to build its own
standards all the time instead of team work on open technologies. If
they want to live in their own universe - it's their choice. We need to
continue team work on the future of open web communications.

"Cullen Jennings (fluffy)" <fluffy@cisco.com> wrote:

>I see that Microsoft decided to wait until the W3C and IETF were close
to done before putting together a proposal that, if accepted, would
explode most the current works and create maximal delay on this work. 
rtcweb mailing list
Received on Tuesday, 7 August 2012 13:00:28 UTC

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