Presence and IntComm WG

[Candace Holman <>]

Thanks - I posted it to the wiki based on feedback from today's call.  
Posting to the wiki means that this is open for editing.  See PIC 
Technologies - PIC-WG Features List at

https://wiki.internet2.edu/confluence/display/picwg/Home

Candace


Deke Kassabian wrote:
> I certainly support that idea.
>
> If it's mainly for us, then wiki.  If there's value in having it visible
> to other parties, like developers and vendors who are not PIC (yet), then
> main web site.  At least that's my notion.  Others?
>
> ^Deke
>
> --On Wednesday, April 12, 2006 7:06 PM -0400 Candace Holman 
> <> wrote:
>
> > Hi -
> >
> > Can we discuss posting this list to the main web site, or is this
> > something more suitable for the wiki?  I'd like to put it somewhere
> > before it gets lost.
> >
> > thanks,
> > Candace
> >
> > -------- Original Message --------
> > Subject:     [wg-pic] PIC WG Feature Requests - Final
> > Date:     Wed, 22 Feb 2006 18:11:42 -0500
> > From:     Candace Holman 
> > <>
> > Reply-To:     
> >
> > To:     wg-pic 
> > <>
> >
> >
> >
> > (Thanks to all who responded.  I have reorganized and updated the
> > list quite a bit with additions, so please review and reply to the
> > list with strong objections.  Otherwise, this list can be posted as
> > is as a new document on the website.  The original list is archived:
> > https://mail.internet2.edu/wws/arc/wg-pic/2006-02/msg00003.html)
> >
> > The PIC WG has composed a feature list for presence integrated
> > communications software.  The list is grouped by categories, but
> > neither categories nor features are in priority order and may
> > conflict.
> >
> > This list serves a variety of purposes:
> >
> > * to hone in on direction and drivers for WG projects,
> > presentations, and other activities
> > * to be prepared to furnish feature requests to developers and
> > organizations
> > * to evaluate presence integrated communications features for our
> > local groups and Internet2
> >
> > User Features
> >
> > * Calendaring, location tracking, personal status/availability/mood,
> > and other rich presence
> > * Voice, conferencing, voice mail, and other audio
> > * Instant messaging and other shared text
> > * Video, whiteboards, and other shared visuals
> > * Default configuration to provide a modicum of privacy and easy
> > introductions to all features
> > * Client control of presence capabilities and notification features
> > * Automatic presence and capabilities updates, such as recognition
> > of added USB device or updates based on idle time
> > * Enhanced capabilities detection, such as customizable scripts that
> > describe resources (MIT)
> > * Ability to login from multiple locations but choose which session
> > is valid (UCB)
> > * Message silo storage and call-me-back's queued while you're
> > offline, with interactive bot agent notification
> > * Separate the message composition from delivery method (SMS, MMS,
> > etc)
> >
> > Protocol Specific
> >
> > * Traversal techniques such as TURN, STUN, and ICE to make
> > SIP/SIMPLE behave with NAT, firewalls, and SBCs
> > * IPv6 implementations
> > * Group chat, such as Message Session Relay Protocol
> > * Optimized updates, such as partial presence updates
> > * Presence updates via SUBSCRIBE/NOTIFY for clients that don't
> > implement PUBLISH
> > * Human readable client/server or client/client transactions to
> > assist troubleshooting
> >
> > Security and Privacy
> >
> > * Authenticated instant messaging and SP** (SPAM,SPIM,SPIT)
> > prevention
> > * Secure updates, such as via encryption and authenticated
> > transactions and identities
> > * Privacy measures, such as anonymous IM, and accompanying methods
> > for client controls
> > * Shibboleth authentication integration
> >
> > Standardization
> >
> > * Protocol-agnostic (SIMPLE, XMPP, hybrids, and future protocols
> > that show forward progress in building and demonstrating working
> > models)
> > * Devise/implement a benchmark for basic functionality with a single
> > client
> > * Devise/implement a benchmark basic functionality and
> > interoperability with several clients
>
>
>
> -------
> Deke Kassabian,  Senior Technology Director
> Information Systems and Computing, University of Pennsylvania