Instant Messaging and Presence Protocol (impp)

This Working Group did not meet

In addition to this official charter maintained by the IETF Secretariat, there is additional information about this working group on the Web at:

       http://www.imppwg.org -- Additional IMPP PAGE
NOTE: This charter is a snapshot of the 58th IETF Meeting in Minneapolis, Minnesota USA. It may now be out-of-date.

Last Modified: 2003-11-03

Chair(s):
Mark Day <markday@cisco.com>
Derek Atkins <derek@ihtfp.com>
Applications Area Director(s):
Ned Freed <ned.freed@mrochek.com>
Ted Hardie <hardie@qualcomm.com>
Applications Area Advisor:
Ted Hardie <hardie@qualcomm.com>
Mailing Lists:
General Discussion: impp@iastate.edu
To Subscribe: impp-request@iastate.edu
Archive: http://www.imppwg.org
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

Goals and Milestones:
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
Done  Submit Common Presence and Instant Messaging document and Common Instant Message Format to IETF for consideration as Proposed Standard
Internet-Drafts:
  • - draft-ietf-impp-cpim-msgfmt-08.txt
  • - draft-ietf-impp-cpim-pidf-08.txt
  • - draft-ietf-impp-srv-04.txt
  • - draft-ietf-impp-pres-04.txt
  • - draft-ietf-impp-im-04.txt
    • Request For Comments:
    RFCStatusTitle
    RFC2778 I A Model for Presence and Instant Messaging
    RFC2779 I Instant Messaging / Presence Protocol Requirements
    RFC3339 PS Date and Time on the Internet: Timestamps

    Current Meeting Report

    None received.

    Slides

    None received.