Skip to content


Jingle Progress

One of the high-priority items on our roadmap for 2007 is completing work on Jingle, the set of XMPP extensions for voice and video that we first published in late 2005. Although it’s taken us about 16 months, we are getting quite close to advancing the Jingle specifications to Draft status within our standards process. Jingle, originally based on the technology defined by Google Talk team, is now widely used in the One Laptop Per Child project as well as in the Nokia 770 and the Nokia 800. Today we updated five of the main Jingle specs:Jingle core, Jingle Audio via RTP, Jingle Video via RTP, Jingle ICE Transport, and Jingle Raw UDP Transport. These specs should be ready for Last Call very soon now, so stay tuned for further updates.

Posted in standards.


2 Responses

Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.

  1. Dhana says

    Is it good idea to wait for Jingle spec to be stanardized or go ahead with Google’s implementation and expect only minor changes and backward compatability?
    I ask this coz we are thinking of a SIP – XMPP gateway. Please put your thoughts.

    Thanks in advance.

  2. stpeter says

    The Jingle specs are very close to advancing to Draft in our standards process. We don’t know when Google will update their service to support the specs (“Jingle 1.0″) as opposed to their current protocol (“Jingle 0.9″), but the differences are small enough that you probably can use one codebase for the translation with compile-time options for Jingle 1.0 vs. Jingle 0.9. For details, feel free to ping me directly via IM (I’m stpeter@jabber.org) or ask on the JDEV discussion list.