Re: [rtcweb] "20 lines" (Re: RTCWeb default signaling protocol [was RE: About defining a signaling protocol for WebRTC (or not)])

[Saúl Ibarra Corretgé <[e-mail]>]

On Sep 23, 2011, at 2:58 AM, Jozsef Vass wrote:

> I am in support of having some basic mechanism in the browser as part of rtcweb to enable developers to quickly and easily setup media between participants. Furthermore, if an API is too complex or too hard to use, people will not use it or misuse it. I can only see a handful of companies developing advanced calling feature on top of rtcweb, most people just want to have something simple to work without caring too much about the details.
> 
> Maybe it would be advantages to specify such a very basic use case, e.g., targeting gaming. It must work behind NATs using peer-to-peer media transport (but fallback to media relay may not be required). Since it is targeting closed community, there is no need for interoperability, there is no need for SIP, Jingle, etc. At the minimum, this would require a simple service for ip address lookup and to aid NAT and firewall traversal.
> 

This is a no go. What "closed community" are you talking about? Interoperability is a MUST here, even if I'm in favor of not having any default signaling protocol specified. We need to be able to communicate with other protocols without building gateways. This can be achieved with both SIP and XMPP, so I see no need for reinventing the wheel. Lets let developers use whatever protocol they like and just use RTCweb for the media part.

> For example, when a user registers with this service, he/she is assigned an identifier or blob. In order to communicate with another party, all they need to do is to exchange this information (this can be done using websocket, etc.) and setup media channel. There should be no need for parsing SDP, etc.
> 

What service? Who would host a server?

--
Saúl Ibarra Corretgé
AG Projects