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

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

Hi,

> You misunderstood me; I meant "if you use an optional SIP module, you'll
> need to have a SIP proxy on your server".  WebRTC in general presumes some sort
> of server architecture to solve the discovery/invitation problem.  There *are*
> some possible uses of WebRTC that might not use a central server(s).   The simplest
> would be the "phone-tag" server, where you and the person you want to talk to
> exchange IP addresses and external port numbers over the phone, and type them into
> the web app, which then opens a default-configured PeerConnection and re-negotiates
> to the actual configuration.
> 

Still, you need this "phone-tag" server, so who will provide it? I don't see a way for 2 parties to communicate without help from outside the browser, thus, I wouldn't define any sort of protocol, even if we could simplify one.

My 2 cents,

--
Saúl Ibarra Corretgé
AG Projects