Germany NGN Interconnection...but where is IMS?

Interconnecting VoIP networks I thought was the job of IMS and related peering setup (IPX?).
Now it seems that XConnect is doing it in a partnership. And the XConnect I know has emerged from Internet VoIP technologies, connecting the Internet VoIP islands.
Definitely an interesting case to be followed. If we see more of these, it will change the world.


From the story:
The DE-CIX NGN service resolves these challenges by offering national and international network operators a secure hub for NGN interconnection, with benefits including:

• Multilateral NGN interconnection to multiple networks, by-passing the PSTN, and reducing the need to create and manage numerous commercially and technically onerous bilateral IP interconnects
• Improved Voice quality and support for higher-value multimedia services
• Number portability corrected routing via a Centralised Number Portability database (CDB) to ensure accurate call routing
• Policy control to define and manage the technical terms of each interconnection and support for different settlement models between operators
• Reduction of capital and operating expenses, transit charges, and resource requirements for creating and managing interconnects, from interoperability testing to implementation

WebRTC could be huge...but where is MS/Skype?

Today, September 5th, Nokia launched two new Windows8-handsets.
Instead of focusing on the devices themselves (which deservedly are getting attention elsewhere!) let's talk of an emerging Internet technology standard that could fundamentally change how we communicate: WebRTC.

Basically, WebRTC could revolutionise how we communicate.
Reason is that it will enable Web developers to include voice and video communications to the web page development.
Think how you retrieve information from the Web, from any www-site. The promise of WebRTC is that communications will become as friction-free.
Think of a hotel chain. They can embed a WebRTC call-to link in their web pages and enable consumers to talk to their agents.
No need to download a VoIP client, just do it from any browser.

Until now, the VoIP providers have in reality been isolated islands, but communications moving to the browser that could change.
Let's remember, VoIP-in-browser as such is a known solution, but here we are talking of a standard, meaning the user needs not install proprietary plugins.
While this sounds elementary, the VoIP and Web industry could change with the new transparency.

But we are not quite there yet. Summer was an interesting one for WebRTC.
The good news was Google promoting WebRTC in its IO conference.
Clearly, Google and the browser vendors are leading the way for WebRTC.

But what happened then?
Microsoft (remember, MS acquired Skype some time ago...) entered the stage.

They made a comprehensive proposal on how they see WebRTC.
The concern is that if MS has its way, the WebRTC will either change course or diverge.

The MS proposal could change radically the concept of WebRTC.
One issue is the need for lower level APIs they see. This would in turn require more functionality at javascript layer, meaning burden to the developers.

Also, it is interesting to see that MS wants IETF to take network conditions into consideration. That is what the mobile industry has argued for, while IETF has always developed their solutions to "generic IP networks", assuming their performance will be adequate.
Now the word in the industry is that MS wants to slow WebRTC down, simply because Skype is the dominant VoIP network, and a closed one. This is of course very logical. Meanwhile, Google (and browser vendors like Mozilla Firefox) want to move on.
So, the game is on.
But, Google Chrome supports WebRTC basic functionality early version today, and seems others will follow.

Then, how does all this impact Nokia? Well, many Nokia devices support wifi and LTE is around the corner. LTE is an excellent bitpipe for VoIP.
Question for Nokia is: will MS/Skype be left off the WebRTC train?