Miscellaneous

Identity and Privacy are a growing concern on the Internet nowadays, and there have been different attempts to solve this. One of the most recent ones is BrowserID. The XSF believes however, that building upon the strengths of XMPP would be a great way forward for the BrowserID concept, due to its inherent federation, proven Internet-wide scalability, and decentralised architecture. This is why the XSF has decided to support projects that demonstrate the use of XMPP for BrowserID purposes.[Read More]

Microsoft has announced that it is adding support for XMPP to its Windows Live APIs, enabling any application or IM network to interoperate with Windows Live Messenger.

Details are available at liveside.net and dev.live.com.

Skype has added support for XMPP to its latest Windows beta, according to Phil Wolff of Skype Journal. Janko Roettgers provides further analysis at GigaOM.

This is yet another demonstration of the power of open standards.

Jingle (XEP-0166 and XEP-0167) is the voice and media signalling protocol developed by Google, Collabora, Yate, Tandberg and Jabber Inc (the latter two now part of Cisco), and standardized within the XSF. Seen by many as key for an open-standard consumer VOIP system to compete with Skype and others, the specifications moved from Experimental to Draft status two years ago, and have been implemented in a large number of clients, including desktop and mobile handset environments.[Read More]

The XSF has issued a Last Call on XEP-0262, which describes implementation considerations related to audio codecs for use in Jingle RTP sessions, and recommends PCMU and PCMA (G.711) as mandatory-to-implement technologies to provide a baseline for interoperability.

If you have feedback, please post to the jingle@xmpp.org or standards@xmpp.org discussion list before July 8, 2011.

Earlier today, the XSF advanced XEP-0262 from Experimental to Draft in our standards process. This specification defines how to use ZRTP with Jingle for end-to-end encryption of audio and video sessions, thus supplementing the existing SRTP method defined in XEP-0167.

Special thanks to the Jitsi team for providing implementation feedback.

FYI, if you’re a fan of Strophe.js and/or libstrophe then you need to make sure to update your bookmarks as the site has moved. You can now find all of the Strophe goodness at strophe.im.

UPDATE: The hsxmpp project has moved too, the new site is http://חנוך.se/hsxmpp/.

As you might recall from our Brussels trip report a few months ago, the XMPP community has a bit of work to do on internationalization. It’s not that XMPP messages or addresses can’t include non-ASCII characters, because we’ve had that capability since 1999. The problem comes from our dependence on a technology called stringprep (RFC 3454), which we use to compare JabberIDs for tasks like authentication and authorization of users and servers.[Read More]

A reminder from Ludovic Bocquet that May 19th, 2011 is Open Discussion Day. From their wiki page: Since 2006, on May 19^th^, we celebrate the Open Discussion Day, a day to promote open communication systems and protocols. Imagine an internet where it is only possible to send emails to people who used the same email provider as you, or only view websites that are hosted on your internet provider’s servers. Naturally, these barriers go against the principles of the internet, and thankfully those days are long gone.[Read More]

The RFC Editor has announced that RFC 6120 (Extensible Messaging and Presence Protocol (XMPP): Core), RFC 6121 (Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence) and RFC 6122 (Extensible Messaging and Presence Protocol (XMPP): Address Format) are now official RFC documents produced by the IETF! This is a huge milestone for the XSF because it means that the core specifications for XMPP have been updated to incorporate years of implementation and deployment experience with our technologies.[Read More]