Presence and IntComm WG

[Peter Saint-Andre <>]

Ben Chinowsky wrote:
> *Action Items as of July 13*
> 
> (high priority)
> [ACTION] (6/29) Mark will find out if jabberd 1.x supports roster push.

If by roster push you mean what's defined in RFC 3921, then yes.

> [ACTION] (6/15) Rodger will look into the status of Jingle for Gaim.

I can poke the Gaim developers about that at OSCON.

> [ACTION] (5/4) Rodger will send the PIC WG a matrix of XMPP clients to try.
> [ACTION] (5/4) Rodger will send notes to assorted mailing lists, asking for
> input on PIC's XMPP plan.

Let me know if you'd like input on these.

> (medium priority)
> [ACTION] (5/11 - on hold for the summer) Ben T. will look for students 
> active
> in Place Lab to work with PIC.
> [ACTION] (4/13) Rodger, Joe, Ben T., Steve, and Candace will continue 
> testing
> Gaim SIMPLE against pals.
> [ACTION] (3/2) Joe will ask Jon Peterson to join a PIC call to talk about 
> work
> in IETF SIMPLE.

If Jon is too busy (he's on the IESG now), you could perhaps rope in
Robert Sparks or Hisham Khartabil (co-chairs of the SIMPLE WG).

> *Discussion*

The discussion summary looks accurate to me. Work on the Jingle specs
has restarted with the aim of getting the core specs stable by the end
of the summer (with concomitant updates to the various open source
libraries).

> Peter Saint-Andre joined the call to bring the group up to date on Jabber.
> Peter has been involved with Jabber since 1999 and has written most of
> the JEPs (http://www.jabber.org/jeps/).
> 
> The group discussed the publish/subscribe model for rich presence in Jabber.
> JEP-0060 defines the protocol; JEP-0163 describes how to use it for personal
> eventing. Candace noted the tutorial at
> http://www.pubsub.com/docs/pubsub_xmpp_draft.html. Peter contrasted the
> pubsub approach with the SIP/SIMPLE approach. In SIP/SIMPLE there is a
> PIDF document that has all your presence info, and information you don't 
> want
> to share has to be filtered out per-recipient. With pubsub, everything is
> atomic -- "little bits of XML that are never put into one big document" -- 
> and you tell the server who gets to see which ones; they are never combined
> into one large privacy-threatening document. Ben T. asked if presence
> fuzzing would require a different document for each level of detail; Peter
> replied that you could do it that way, but as pubsub has yet to be fully
> implemented, no one has done this yet. The Wildfire server and the Psi 
> client
> seem to be closest to implementing pubsub.
> 
> Peter gave a quick Jingle status update. Google Talk uses Jingle 0.9; 
> progress
> toward 1.0 has been stalled for the last couple of months. Jingle uses a
> pluggable model, so (for example) you can do your signaling with Asterisk. 
> For
> NAT traversal, Jingle uses ICE, which in turn uses STUN and TURN. Peter 
> noted
> that there is lots of interest in the Jabber community in using Jingle for
> things other than voice, e.g. whiteboarding, shared editing, and distributed
> musical performance.
> 
> JEP-0142 defines limited workgroup functionality for Jabber. While it 
> doesn't
> provide a way to aggregate information across identities (everything in the
> Jabber world revolves around the individual identifier), it does provide a 
> way
> to address the "I need someone in this workgroup, I don't care who" use 
> case,
> e.g. for technical support. Peter noted that automated buddy lists have been
> implemented in some of the commercial servers; he recommends using LDAP for
> further implementations.
> 
> Finally Peter gave an overview of some of the open-source Jabber code bases.
> The original jabberd code base was significantly rewritten for 1.4; work on 
> 1.5
> is ongoing. jabberd2 is a separate code base, launched with the goal of 
> making
> the code easier to understand, but the key people have left and no one is
> currently driving it forward. ejabberd is written in Erlang, which is 
> obscure,
> but because there are so few Erlang projects it attracts coders interested 
> in
> the language. Jabber.org uses ejabberd with about 200,000 users. Wildfire is
> written in Java. Peter noted that Wildfire and ejabberd both have people
> getting paid to work on them, so those are the open-source implementations
> that he recommends.
> 
> Peter encouraged the group to contact him with any further questions. His
> contact information is at http://www.jabber.org/people/stpeter.shtml, and
> he has joined the PIC list.
>

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature