SIP has finally come to the browser! You can now run VoIP using SIP inside your browser by using HTML5 JavaScript tools. And we have WebRTC to thank for that to some extent.

Users don't care about security although they should. Someone should do it for them and that is the role of developers and product managers - now more than ever.

while I am an advocate of WebRTC, it still have a way to go until it matures enough. Until then, most of the things you will see with it are demos and hype. Where is it still lacking and what needs to be done to improve it?

Net neutrality is like a lot of things. Mainly because its exact definition is somewhat elusive. Here are a few comparisons of net neutrality to other "things" that I found on the net.

There are a lot of ways in which services can be launched these days: from stitching a bunch of existing web services to building everything on a dedicated data center. How do these compare to each other?

There is no fragmentation problem in Android. There is an iteration issue that needs to be improved. Once improved, this is going to threaten Apple in a real way.

WebRTC will affect the mobile web as well. It will disrupt wireless telephony as well as the way we think about native and web apps.

People often mistake the signaling protocol with the ability to achieve better media quality. I think it is time to put things straight: SIP or any other signaling protocol has nothing to do with media quality.

WebRTC is a new technology, which means a valid question to ask is will it still be here a few years from now? The immediate answer is yes - and for some very good reasons.

I am now writing for one of Amdocs blogs: Amdocs Voices. You are invited to follow me there as well!