- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Fri, 5 Jul 2013 09:49:56 -0700
- To: Martin Steinmann <martin@ezuce.com>
- Cc: Parthasarathi R <partha@parthasarathi.co.in>, cowwoc <cowwoc@bbs.darktech.org>, Christer Holmberg <christer.holmberg@ericsson.com>, Iñaki Baz Castillo <ibc@aliax.net>, Robin Raymond <robin@hookflash.com>, Roman Shpount <roman@telurix.com>, Adam Bergkvist <adam.bergkvist@ericsson.com>, Ted Hardie <ted.ietf@gmail.com>, "piranna_gmail.com" <piranna@gmail.com>, "public-webrtc_w3.org" <public-webrtc@w3.org>, Eric Rescorla <ekr@rtfm.com>
On 5 July 2013 09:41, Martin Steinmann <martin@ezuce.com> wrote: > If you abstract from proprietary solutions, can you make a list of what else is used other than SIP and XMPP? We are talking about a standard here, aren't we? That's an excellent question. Most Web applications don't need and really don't want a standard when it comes to signaling. It's too restrictive. And most of the examples I've seen don't use any sort of standardized signaling. That list includes almost every WebRTC example in existence, with the exception of a small few. That's why we explicitly state that signaling is out of scope for rtcweb and WebRTC.
Received on Friday, 5 July 2013 16:50:23 UTC