One area of application is WebRTC, the work to enable real-time communications services in web pages. One approach that has been discussed in both the IETF and W3C is to use Websockets to open a new connection between the browser and web server, and run a signaling, presence, or instant messaging protocol over it. For example, it had been proposed to run SIP, Session Initiation Protocol, this way.
A few months ago I blogged about WebRTC and SIP, and argued that SIP should not be standardized by WebRTC, as had been proposed back then. I still believe this is correct, and recent work in the IETF has centered around instead standardizing some kind of offer/answer media negotiating protocol, but leave the choice of signaling protocol open.
Recently a new Internet Draft was submitted on a Websocket transport for Session Initiation Protocol. I think this is a potentially useful approach and could be a good way to utilize SIP in conjunction with WebRTC. The draft is still in it’s early days, and has not yet been adopted by the SIPCORE Working Group yet, but I think it is a great start. SIP developers who are interested in the WebRTC effort should read this draft and support this work.
In the meantime, it is great to see WebSocket finally published as an RFC, something I hope to see happen to a few of my Internet Drafts in the new year!
If you are interested in WebRTC, you might like my new book “WebRTC: PIs and RTCWEB Protocols of the HTML5 Real-Time Web”