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

[Cullen Jennings <[e-mail]>]

On Oct 4, 2011, at 12:19 PM, Bernard Aboba wrote:

> [BA]  I think this is the main point.   If we finish RTCWEB 1.0 expeditiously, this will in all likelihood
> spawn a number of browser-independent signaling libraries, as well as developing a wealth of experience
> with the limitations of RFCWEB 1.0, to inform future efforts. 
> 
> The alternative is to "load up the camel" until it collapses under the weight of (largely irrelevant) use
> cases.  Since the realtime web has been around for over a decade, we have a pretty good idea of what
> native realtime capabilities would be used for -- and PSTN connectivity has never been high on the list.

So uh, you are right we have a lot of experience with real time communications on the internet. Things that come to mind over the last ten years include Microsoft Voice.NET, Vonage, Dialpad, Telio, CBeyond, Skype, Yahoo Messenger, Fring, Google Voice, Webex. That's not a systematic sample but just some random things that came to my mind. Oddly, they all seem to connect with the PSTN. What are the things you are thinking of that decided that PSTN connectivity was not high on the list? Perhaps we can look at which ones ended up being successful.