An open standard at P2P and audio technology was published a few days ago by Jabber Software Foundation(JSF). It’s named Jingle, which is the background technology used within Google Talk, released in August 2005. From the beginning, we noticed that Google made its way into VoIP/IM market through a different way against Skype.
Basically the standard of Jingle is a set of extensions to the IETF’s Extensible Messaging and Presence Protocol (XMPP) for use in voice over IP (VoIP), video, and other peer-to-peer multimedia sessions.
JEP-0166: Jingle Signalling — The core technology for peer-to-peer session management, which enables communication through existing firewalls and can be extended to support a wide range of session types. (Authored by Scott Ludwig and Joe Beda of Google, Peter Saint-Andre of the JSF, and Joe Hildebrand of Jabber Inc.) JEP-0167: Jingle Audio — The session description format for Jingle audio sessions, enabling seamless one-to-one voice over IP (VoIP) between Jabber/XMPP users. (Authored by Scott Ludwig of Google and Peter Saint-Andre of the JSF.)
In addition to Google and Jabber Inc., the following companies and open-source projects have already pledged to support the Jingle protocols: Antepo, Cerulean Studios (Trillian), Coversant, Digium (Asterisk), Gaim, Jive Software, Novamens, Psi, SAPO, and Tipic. Support from additional vendors is expected in the near future.
Every software vendors and individual programmers can make use of Jingle with LibJingle library. LibJingle adopts a Berkeley-Style license, which is of the least restriction to the developers. Armed with the openness, interoperability and marketing capacity of Google, Jingle is expected to be a good competitor and even a replacement to SIP, SIMPLE, and P2P SIP. At the same time, the strength of Jingle is the weakness of Skype, although Skype has been dominating the IM/P2P VoIP market.
technorati tags: Skype, Google, Jabber, Jingle, GT