Presence and IntComm WG

[Steve Blair <>]

Candace:

 I agree with most of what is on this list. The one item I question is 
#13 Message silo storage. Storing instant messages for later retrieval 
seems contrary to the concept of instant messaging (at least to me).
How do other people feel about this?

-Steve


Candace Holman wrote:

> Dear PICers,
>
> This is the second and final time that I will send this out.  I've 
> made changes, so please re-read and reply with any additions or 
> clarifications.
>
> [ACTION] The PIC WG will evaluate what functions (e.g. group chat) 
> should be on our wish list for presence integrated communications 
> software.
>
> We would like 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 enumerate 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 and the community at large 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.  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. Authenticated IM and SP** (SPAM,SPIM,SPIT) prevention
>  4. XMPP, and also whatever the future XMPP is
>  5. Video, whiteboards, and other shared visuals
>  6. Group chat, such as Message Session Relay Protocol
>  7. Middleware support such as NAT, STUN, and ICE 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 accompanying methods 
>     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)
> 16. Shibboleth authentication integration
>
> Candace