Re: [dispatch] RTCWEB I-D with thoughts on the framework

Hi Jonathan,

I pretty much share the interoperability concerns other have raised regarding mandatory usage of STUN.

I do understand the concern you describe, with downloading a JavaScript that triggers the sending of malicious media. However, assume you download a legitimate JavaScript SIP stack. The JavaScript itself is not going to trigger any media to be sent. The media will be sent once you've used SIP to establish a session, and then the media is sent based on the negotiated SDP. Of course, the remote SDP could also be malicious, but that is valid for any SIP implementation - browser based or not :)

Regards,

Christer

-----Original Message-----
From: dispatch-bounces@ietf.org [mailto:dispatch-bounces@ietf.org] On Behalf Of Jonathan Rosenberg
Sent: 8. helmikuuta 2011 16:49
To: 'DISPATCH list'
Subject: [dispatch] RTCWEB I-D with thoughts on the framework

Some of my colleagues from Skype and I have put together a draft which gives our thoughts on the scope of the protocols and functionality for enabling browser RTC. I've just submitted the draft, which you can find
here:

http://www.ietf.org/id/draft-rosenberg-rtcweb-framework-00.txt

Some of the key points:

* keep it minimal
* APIs for controlling behaviors of the various media components, with defaults for those that dont care
* no SIP or Jingle; leave that to proprietary over websockets/HTTP
* no ICE - just STUN. ICE can be a javascript library.

Thanks,
Jonathan R.
-- 
Jonathan D. Rosenberg, Ph.D.                   SkypeID: jdrosen
Skype Chief Technology Strategist
jdrosen@skype.net                              http://www.skype.com
jdrosen@jdrosen.net                            http://www.jdrosen.net

_______________________________________________
dispatch mailing list
dispatch@ietf.org
https://www.ietf.org/mailman/listinfo/dispatch