Instant messaging differs from email primarily in that its primary focus is immediate end-user delivery. Presence information was readily accessible on internet-connected systems years ago; when a user had an open session to a well-known multi-user system, his friends and colleagues could easily tell where he was connected from and whether he was using his computer. Since that time, computing infrastructure has become increasingly distributed and a given user may be consistently available," but has no standard way to make this information known to her peers. This working group will design a system to address this need.
The working group will develop an architecture for simple instant messaging and presence awareness/notification. It will specify how authentication, message integrity, encryption and access control are integrated. It is desirable, but not required, for the working group to develop a solution that works well for awareness of and communication with entities other than human users.
Providing a general notification mechanism for data other than user presence information and instant messages.
The following keywords describe the scope for the working group. Details are to be developed in the architecture document which is the output of this working group:
- INSTANT MESSAGING
- ACCESS CONTROL
The working group plans to deliver the following document:
- Requirements for Instant Messaging and Presence
|Done||  ||Submit Internet-Draft of Design Goals for Instant Messaging and Presence Information|
|Done||  ||Submit design goals Internet-Draft to IESG for publication as an RFC|
|Done||  ||Submit I-D on common instant message format|
|Done||  ||Meet at 50th IETF in Minneapolis|
|Apr 01||  ||Submit Common Presence and Instant Messaging document and Common Instant Message Format to IETF for consideration as Proposed Standard|
|May 01||  ||Upon publication of RFCs, close group.|
|RFC2778||A Model for Presence and Instant Messaging|
|RFC2779||Instant Messaging / Presence Protocol Requirements|