Presence and IntComm WG

["Ben Chinowsky" <>]

*Action Items as of August 9*

(high priority)
[ACTION] (8/3) Rodger will launch an email discussion of if and how to fix 
pals
and pals-dev.
[ACTION] (8/3) Rodger will recruit Peter to provide an update on recent
developments in the Jabber community, in particular 1) developments at OSCON
and 2) the status of Jingle for Gaim.
[ACTION] (8/3) Rodger will send out pointers to an assortment of XMPP-client
feature-comparison matrices, highlighting items of particular interest or
concern to the group.
[ACTION] (8/3) Rodger will revise his Gaim setup instructions.
[ACTION] (5/18) Ben T. will post the calendar-integration code (written by his
2005 SoC student) on the Penn XMPP server; Mark will evaluate prospects for
modifying it to drive XMPP presence.

(medium priority)
[ACTION] (8/3) Joe will update the group on work in IETF SIMPLE, after he
talks to Jon Peterson at VON.
[ACTION] (8/3) Rodger will put a discussion of current vendor offerings in the
location-services space on the agenda for a future call.
[ACTION] (5/11 - on hold for the summer) Ben T. will look for students active
in Place Lab to work with PIC.
[ACTION] (pre-12/8 - in progress) Rodger and Joe will write up some use cases
for enterprise federations.

*Attendees*

Rodger Will (chair) - Ford
Joe Rork - Ford
Deke Kassabian - Penn
Mark Sirota - Penn
Steve Blair - Penn
Candace Holman - Harvard
Dennis Baron - MIT
Neal McBurnett - Internet2
Ben Chinowsky (scribe) - Internet2

*Discussion*

After pruning and revising the list of action items (see above), the group
discussed the division of tasks between clients and servers in XMPP. When
speaking of "the server", it is necessary to distinguish clearly between 
hardware and software, as an XMPP client can run on the same machine with 
the XMPP server it's logged into. Neal compared this to the deployment of 
HTTP client software like wget on server hardware in enterprises.

Mark pointed out that it's the server software that asserts presence
information. These assertions may be based on instructions from the client.
This enables users to have the server assert "absence" information -- "when
I'm not logged in, assert the following information."