Presence and IntComm WG

["Ben Chinowsky" <>]

*Action Items as of June 23*

- new action items -
[AI] All will review the extensive June 21-22 list discussion in preparation
for the June 24 call.
[AI] All will review their assignments for Austin and recruit others to help
them.
[AI] Joe will maintain a list of Austin demo goals and assignments on the PIC
web site.
[AI] Joe will look into NIST SIP (http://www-x.antd.nist.gov/proj/iptel/).

- old action items -
[AI] If he has time, Joe will analyze the statistics on portal traffic.
[AI] On a future PIC call, the group will discuss putting together a report
on experiences with the PIC trials so far.
[AI] Larry will arrange a conference with the Cisco location-technologies
expert, bearing in mind that the PIC working group can't do NDA.
[AI] Ben T. will seek support for SIP.edu click-to-dial directories at the
June 16 SIP.edu workshop.
[AI] Ben T. will arrange regular contacts with vendors interested in
participating in the demo (new Internet2 member Avaya in particular).
[AI] All will send Ben T. any information they have on vendors interested in
participating in the demo.
[AI] Jeremy will formally register the PIC demo with the Austin meeting
planners, noting its special character as one of an ongoing series, and as
something that's woven into the meeting as whole.
[AI] Ben T. will get contacts for the buildout for Austin, and in particular
find out when information on the physical layout of the meeting will be
available.
[AI] Jeremy will send the people on this call an Internet2 draft document on
next steps for presence; all will send comments to him (NOT to the author of 
the
document).
[AI] Joe will send Ben T. specifics on the problem he's having with mail 
missing
from the archive; Ben T. will take this up with the mail admin.

*Attendees*

Jeremy George (chair) - Yale
Joe Rork - Ford
Steve Blair - Penn
Art Gaylord - Woods Hole
Dennis Baron - MIT
Candace Holman - Harvard
Xiaotao Wu - Columbia
Ben Chinowsky (scribe) - Internet2

*Discussion*

The group reviewed Joe's list of areas of work for Austin, with the following
results. This summary incorporates recent email responses as well. [AI] All 
will
review their assignments for Austin and recruit others to help them.

- H.350 - Ben T. is leading; the H.350 principals are on board.
- SIP.edu - Ben T. will lead.

- Per-room session-based IM chat rooms - Jamey will lead.
- Per-room audio conferences with session-based IM - Jamey will lead.
- Per-organization chat rooms - Jamey will lead.
- SIMPLE/Jabber gateway - The group agreed to drop this one for Austin.

- Web UA - Candace noted that she has no expertise here. Joe offered to help 
out
if Candace can take the lead.
- Location specific resources shown on portal - Candace and Steve will lead,
contacting Jamey as necessary.

The "public interface group". Joe would like to have good posters and handouts
for these.
- Walk up Kiosk - Joe will lead.
- Map Kiosk - Joe will lead, Jeremy will help.
- Transfer call to/from SIP kiosk based on location - Joe will lead.

Everyone who's helping recruit client vendors will work to ensure:
- Client support for iLBC
- Client support for location presence fuzzing
- Support for small devices
- Client support for session-based IM
- Push-to-talk

The group discussed priorities for Austin. The biggest concerns were stability
and usability.

Stability: The group agreed to retain the approach of not making a priority of
things the network doesn't handle well (voice and video). Nevertheless, it was
agreed to reach for the low-hanging fruit where these higher-bandwidth means
of communication are concerned: 1) include iLBC, and 2) provide tools that let
the user know what means of communications are available (e.g., "no voice
available from here, do you want to IM?")

Usability: Joe noted that user configuration was the big obstacle to 
usability.
This time we want to tackle that via 1) kiosks, 2) web UA, and 3) H.350. Joe
stressed that having kiosks and a Web UA doesn't mean downplaying other UAs,
just providing alternatives to them.

[AI] Joe will look into NIST SIP (http://www-x.antd.nist.gov/proj/iptel/).