Presence and IntComm WG

["Ben Chinowsky" <>]

*Action Items as of July 12*

The date the item was originally assigned is in brackets.

[08-Jul-04] If there is a fix to the iLBC/GSM issue from Cisco, Dennis will
report it on the SIP.edu list, and let Jeremy know if it works with his 
gateway.
[08-Jul-04] On the July 15 call, the group will discuss 1) goals and next 
steps
for including click-to-dial directories of SIP.edu-enabled schools in the 
Austin
demo, and 2) the Stony Brook proposal for SIP.edu metadirectories.
[08-Jul-04] Ben T. will give Joe write access to the PIC web site.
[08-Jul-04] Joe will move this item to the web UA subgroup: [ACTION] Joe will
look into NIST SIP (http://www-x.antd.nist.gov/proj/iptel/).
[08-Jul-04] Starting on the July 15 call, Joe will have each subgroup give a
short informal update on its progress, and raise any issues that require the
attention of the full PIC working group.
[08-Jul-04] Joe will contact Steve Blair about web UA issues.
[08-Jul-04] Jamey will contact Samir Chatterjee, maintainer of CGU's SIP UA, 
to
see if we can use it to do session-based messaging.

[01-Jul-04] Ben T. will contact vendors about providing a PSTN gateway.
[01-Jul-04] Ben T. will follow up with the x10 folks on Austin participation.

[24-Jun-04] Joe and Jeremy will launch a PSTN gateway subgroup.

[17-Jun-04] Joe will maintain a list of Austin demo goals and assignments on 
the
PIC web site. (See details in the discussion below.)
[17-Jun-04] All will review their assignments for Austin and recruit others to
help them.

[03-Jun-04] Ben T. will arrange regular contacts with vendors interested in
participating in the demo (new Internet2 member Avaya in particular).
[03-Jun-04] All will send Ben T. any information they have on vendors 
interested
in participating in the demo.
[03-Jun-04] 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.

*Attendees*

Jeremy George (chair) - Yale
Dennis Baron - MIT
Joe Rork - Ford
Jamey Hicks - HP
Ben Chinowsky (scribe) - Internet2

*Discussion*

The group reviewed action items:

[01-Jul-04] Dennis will test the xlite iLBC codec with a Cisco gateway.
- Done; it doesn't work. Dennis noted that GSM has the same problem, and 
there's
a Cisco trouble ticket open on that. In both cases the Cisco offers G.711 and
the call completes properly. This isn't particularly a PIC issue; [ACTION] If
there is a fix to the iLBC/GSM issue from Cisco, Dennis will report it on the
SIP.edu list, and let Jeremy know if it works with his gateway.

[01-Jul-04] Ben T. will contact vendors about providing a PSTN gateway.
- In process.

[01-Jul-04] Dennis and Ben T. will pursue click-to-dial support on the SIP.edu
list.
[01-Jul-04] Ben T. will work with the Stony Brook folks on a spec for SIP.edu
metadirectories.
- It was agreed to replace these items with [ACTION] On the July 15 call, the
group will discuss 1) goals and next steps for including click-to-dial
directories of SIP.edu-enabled schools in the Austin demo, and 2) the Stony
Brook proposal for SIP.edu metadirectories.

[01-Jul-04] Ben T. will follow up with the x10 folks on Austin participation.
- Still to do.

[24-Jun-04] Joe and Jeremy will launch a PSTN gateway subgroup.
- In process.

[17-Jun-04] Joe will maintain a list of Austin demo goals and assignments on 
the
PIC web site.
- Joe still doesn't have access. [ACTION] Ben T. will give Joe write access to
the PIC web site. As appropriate, Joe will move action items from the running
list in the minutes to lists for the various subgroups on the web site. The
group agreed that the the Austin priorities statement from the June 17 minutes
should be included with the list of subgroups and subgroup tasks:

"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."

[17-Jun-04] All will review their assignments for Austin and recruit others to
help them.
- In process.

[17-Jun-04] Joe will look into NIST SIP
(http://www-x.antd.nist.gov/proj/iptel/).
- [ACTION] Joe will move this item to the web UA subgroup.

[03-Jun-04] Ben T. will arrange regular contacts with vendors interested in
participating in the demo (new Internet2 member Avaya in particular).
- Jeremy noted that this is in process with Avaya.

[03-Jun-04] All will send Ben T. any information they have on vendors 
interested
in participating in the demo.
- Ongoing. Jeremy doesn't know of any new vendors yet.

[03-Jun-04] 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.
- In process.

[29-Apr-04] If he has time, Joe will analyze the statistics on portal traffic.
- Joe's not going to have time, so this item is being deleted.

[01-Apr-04] Larry will arrange a conference with the Cisco 
location-technologies
expert, bearing in mind that the PIC working group can't do NDA.
- Larry hasn't been on the calls lately, so this item is being deleted.

Other discussion:

- [ACTION] Starting on the July 15 call, Joe will have each subgroup give a
short informal update on its progress, and raise any issues that require the
attention of the full PIC working group.
- [ACTION] Joe will contact Steve Blair about web UA issues.
- Jamey noted that he's been looking into a session-based messaging server.
[ACTION] Jamey will contact Samir Chatterjee, maintainer of CGU's SIP UA, to 
see
if we can use it to do session-based messaging.