 |
 |
 |
 |
|
 |
|
 |
|
 |
|
 |
Folks ---- I would like to draw your attention to the IMPP Working Group (http://www.ietf.org/html.charters/impp-charter.html) of the Internet Engineering Task Force (IETF, http://www.ietf.org), and encourage you to participate. To participate, get onto the mailing list, browse through the archive, understand the issues currently being discussed, and contribute. The group is currently considering an Internet drafts formalizing the requirements for an Internet-wide protocol for Instant Messaging and Presence Notification: http://www.ietf.org/internet-drafts/draft-ietf-impp-model-00.txt http://www.ietf.org/internet-drafts/draft-ietf-impp-reqts-00.txt (In addition, an email message summarizing possible architectures that have come up during consideration has been circulated by Jim Malcolm.) The WG will meet at the IETF meeting in Oslo; in addition a meeting has been called by Mark Day of Lotus in Boston on June 11 to obtain feedback on the requirements document. Again, details are in the archives. If you wish to attend, write to Mark at Mark_Day/CAM/Lotus@lotus.com before June 4. If you are new to the IETF, please spend some time familiarizing yourself with the IETF; see in particular http://www.ietf.org/tao.html. Please let me know if you have questions. Best regards, Vijay Saraswat -- Try http://intercom.att.com! Home-page: http://www.research.att.com/~vjTitle: Instant Messaging and Presence Protocol (impp) Charter
|
|
|
|
|
|
|
|
|
|
|
|
Last Modified:
26-Feb-99
Chair(s):
Vijay Saraswat <vj@research.att.com>
Dave Marvit <dave@marvit.org>
Applications Area Director(s):
Keith Moore <moore@cs.utk.edu>
Patrik Faltstrom <paf@swip.net>
Applications Area Advisor:
Patrik Faltstrom <paf@swip.net>
Mailing Lists:
General Discussion:impp@iastate.edu
To Subscribe: impp-request@iastate.edu
Archive: http://lists.fsck.com/cgi-bin/wilma/pip
Description of Working Group:
This working group will eventually define protocols and data formats
necessary to build an internet-scale end-user presence awareness,
notification and instant messaging system. Its initial task is to
determine specific design goals and requirements for such a service.
The design goals document will be submitted for IETF-wide review,
and based on that review, the group's charter will be extended.
Background:
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.
Goals:
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.
Non-goals:
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:
- PRESENCE
- INSTANT MESSAGING
- SHARED
- NAMING
- AUTHENTICATION
- ACCESS CONTROL
- SCALABILITY
Deliverables:
The working group plans to deliver the following document:
- Requirements for Instant Messaging and Presence
| May 99 | Submit Internet-Draft of Design Goals for Instant Messaging and Presence Information | |
| Jul 99 | Submit design goals Internet-Draft to IESG for publication as an RFC |
Return to working group directory.