Presence and IntComm WG

["Ben Chinowsky" <>]

*Action Items as of January 11*

(high priority)
[ACTION] (1/5) Rodger will look for carrier reps to present perspectives on 
IMS.
[ACTION] (1/5) Rodger will ask Ben T. for a PIC-DEV status update ahead of the
January 12 call.
[ACTION] (12/15) All will respond to Candace's Dec. 8 email, "PIC-SER Feature
Requests #1". [see below]
[ACTION] (12/15) Steve will send out some Spring Member Meeting suggestions
from Deke.
[ACTION] (12/15 - in progress) Rodger will follow up with potential VoIP
panelists; Dennis will suggest further potential panelists.
[ACTION] (12/8) On the next well-attended call, the group will consider 
whether
to adopt a call schedule covering PIC-SER and SIP/XMPP on alternating weeks.
[ACTION] (12/8 - in progress) Dennis will schedule Megan Pengelly to summarize
Columbia's PIC-SER experience on a future call.
[ACTION] (12/8) All will give some thought to ideas for PIC activities at the
Spring MM.
[ACTION] (pre-12/8) Ben T. will ask Steve Kirk to suggest someone from Nortel 
to
present on a PIC call.
[ACTION] (pre-12/8) Rodger will try to reach his contact at Barracuda 
Networks.
[ACTION] (pre-12/8) Rodger will contact Erik Lagerway.
[ACTION] (pre-12/8) Rodger will ask Jeremy to present on privacy on a future
call.
[ACTION] (pre-12/8) Rodger and Joe will write up some use cases for 
federations.
[ACTION] (pre-12/8) Rodger will try to organize a call with CounterPath 
sometime
in the next few weeks.

(medium priority)
[ACTION] (pre-12/8 - in progress) Steve will schedule Cullen Jennings as a 
guest
speaker on a joint PIC/SIP.edu conference call.
[ACTION] (pre-12/8 - in progress) Candace will add a Wiki document on strict 
vs.
loose routing.

(low priority)
[ACTION] (pre-12/8) Candace and Jamey will initiate an email discussion of 
their
proposal to modify the SER PA module so it can do presence via SUBSCRIBE and
NOTIFY, to accommodate clients that don't do PUBLISH.
[ACTION] (pre-12/8) Jamey will enable eyeBeam to use presence info to decide
whether messages should go straight to voicemail.
[ACTION] (pre-12/8) Jamey will update the interface requirements document.
[ACTION] (pre-12/8) People will research skiff-like offerings from various
companies:
- Dennis - Newbury
- Rodger - Airespace (now part of Cisco)
- Jeremy - Eckehau (via Walt Magnussen)
[ACTION] (pre-12/8) Candace will look into Tyler Johnson's H.350-enabled 
version
of the NIST client.
[ACTION] (pre-12/8) Ben T. will write a short document describing the 
motivation
for the paths-in-the-snow approach to PIC development.

*Attendees*

Rodger Will (chair) - Ford
Dennis Baron - MIT
Steve Blair - Penn
Candace Holman - Harvard
Ben Chinowsky (scribe) - Internet2

*Discussion*

The group discussed possible topics for future PIC calls. Rodger noted that 
many
carriers seem to see IMS as the way to get involved in the IP space in a big
way. [ACTION] Rodger will look for carrier reps to present perspectives on 
IMS.
Another topic could be how new VoIP technologies can be used to improve
campuses' bargaining power with carriers. Candace noted that Cisco has started
talking publicly about an IMS offering.

Candace noted that PALS-DEV is operational, but without the latest fixes.
[ACTION] Rodger will ask Ben T. for a PIC-DEV status update ahead of the
January 12 call.

The group continued its discussion of plans for a VoIP panel at the Spring
Internet2 Member Meeting. Candace is interested in hearing from institutions
who've done low-budget deployments, and in particular in finding out about
support and maintenance issues arising from this decision. Penn and Woods Hole
are possibilities here. Another possible topic is the changes in 
organizational
culture needed for VoIP deployments to succeed; Rodger suggested that each
presenter be asked to touch on this. The group agreed to plan on four 
15-minute
presentations plus a panel discussion.


=====


----- Original Message ----- 
From: "Candace Holman" 
<>
To: 
<>;
 
<>
Sent: Thursday, December 08, 2005 5:43 PM
Subject: PIC-SER Feature Requests #1

> Dear PICers,
>
> [ACTION] The PIC WG will evaluate what functions (e.g. group chat) should be
> added to the next version of the PIC-SER package.
>
> As noted above, one of our outstanding action items is to come up with a
> list of features that we think are worthwhile to request in SER PA
> module, and to have this list available for a variety of reasons:
>
>     * to hone in on direction and drivers for WG projects,
>       presentations, and other activities
>     * to form initial consensus on the protocols, platforms, and systems
>       this WG endorses
>     * to be prepared next time a developer is seeking a project idea, or
>       there is another similar outstanding opportunity such as Google's
>       Summer of Code
>     * to evaluate for our local groups what are the important real time
>       communications features
>
> To that end, I would like to cordially invite you to help build the
> first draft list by adding to the list below.  Once we have a longer
> list we can then use it to debate the value and priority of each feature
> request.  Some of these were spawned by conversations with PIC-SER
> participants, some are old action items, and some have been mentioned in
> previous discussions on the conference calls.
>
>    1. Benchmark basic functionality with a single client
>    2. Benchmark basic functionality and interoperability with several
>       clients
>    3. IM/SPAM prevention
>    4. Jabber gateway, and also whatever the new Jabber is in the future
>    5. Video, whiteboards, and other shared visuals
>    6. Group chat, such as Message Session Relay Protocol
>    7. BEHAVE support such as NAT, STUN, and other protocols to soothe
>       end-to-end demons like firewalls and session border controllers
>    8. Presence updates via SUBSCRIBE/NOTIFY for clients that don't
>       implement PUBLISH
>    9. Secure updates, such as via encryption and authenticated
>       subscribes, notifies(?), and identities
>   10. Privacy measures, such as anonymous IM, and the method for client
>       controls
>   11. Optimized updates, such as partial presence updates
>   12. Automatic presence and capabilities updates, such as recognition
>       of added USB device or idle time
>   13. Message silo storage while you're offline or updates are
>       undeliverable
>   14. Ability to login from multiple locations but choose which session
>       is valid (UCB)
>   15. Enhanced capabilities detection, such as customizable scripts that
>       describe resources (MIT)
>
> Candace
>