Presence and IntComm WG

["Ben Chinowsky" <>]

*Action Items as of May 24*

(high priority)
[ACTION] (5/17) Ben will draft paragraph-length versions of package 
descriptions
one and zero, with a variety of sentence-length use cases for each, and work
them into the draft PIC.edu survey.
[ACTION] (5/10) All will review the use cases at
https://wiki.internet2.edu/confluence/display/picwg/PIC+Use+Cases
with a view toward including some of them in the PIC.edu survey at
https://wiki.internet2.edu/confluence/display/picwg/PIC+Project+Proposal+Survey
[ACTION] (5/3) Deke will ask Mark when he expects to be able to revise the
features list, adding XMPP items to the "Protocol Specific" section, and 
making
the "User Features" and "Security and Privacy" sections protocol-agnostic.
[ACTION] (4/12) Jonathan and Deke will look for a permanent chair for the PIC
working group.
[ACTION] (3/22) Jonathan will look for PIC.edu resources at Radvision, 
Tandberg,
and Polycom.
[ACTION] (3/22) Dennis will see if PIC.edu resources are available in Europe.
[ACTION] (3/8) Jonathan will find out what's going on with presence in the
Access Grid community, and if there is interest in PIC.edu there.
[ACTION] (3/1) Dennis will recruit someone from Google to join a call to 
discuss
how they might be able to participate in PIC.edu.

(medium priority)
[ACTION] (1/4) Prashant will send out some links on how XMPP relates to
federations.
[ACTION] (12/14) Rodger and Prashant will further discuss how CampusEAI could
participate in PIC.

(low priority)
[ACTION] (9/7) Mark will Applescript-enable his presence agent and post the 
code
on the web.
[ACTION] (8/31) Dennis will contact Skyhook for more information.
[ACTION] (8/24 - in progress) Mark will see if he can find interest in the
presence-agent project on the Psi developers' list.
[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/18) Mark will evaluate prospects for modifying the calendar-
integration code written by Ben T.'s 2005 SoC student, to drive XMPP presence.
[ACTION] (in progress) Rodger and Joe will write up some use cases
for enterprise federations.

*Attendees*

Deke Kassabian (interim chair) - Penn
Tim Callahan - Michigan
Candace Holman - independent
Neal McBurnett - Internet2
Michael Gettes - Internet2
Jonathan Tyman - Internet2
Ben Chinowsky (scribe) - Internet2

*Discussion*

The group continued its discussion of the PIC use cases at
https://wiki.internet2.edu/confluence/display/picwg/PIC+Use+Cases .
Tim suggested developing a general enterprise collaboration use case; Ben
suggested structuring this as a general use case with specific sub-cases
like virtual study groups and technical support.

There was general agreement that we need to present the use cases in two
versions: a version for a package of technologies that can be deployed
right now (an interoperable way to deploy text-based IM with rudimentary
presence -- "package description zero") and a version for a package that
could build on this and deploy soon (using JINGLE to add voice, and adding
a way to indicate which means of communication an individual is available to
use -- "package description one".) Michael observed that implementing package
description zero would be mostly a matter of documenting already available
technologies and good practices.

Ben argued that trying to pick winning use cases doesn't play to the key
strength of the technologies under consideration: these technologies have
many uses, some of which users will discover for themselves. [ACTION] Ben will
draft paragraph-length versions of package descriptions one and zero, with a
variety of sentence-length use cases for each, and work them into the draft
PIC.edu survey.

Michael noted privacy concerns with the "FindMe" use case; there was general
agreement that, for now at least, the PIC WG should not promote deployment of
possibly privacy-threatening technologies. Tim noted that Michigan is getting
ready to implement controller-based wireless systems, most of which implement
location tracking; he has industry contacts PIC could tap when it decides to
take up location tracking again.