Instant Messaging / Presence Protocol Requirements
RFC 2779
| Document | Type |
RFC - Informational
(February 2000; No errata)
Was draft-ietf-impp-reqts (impp WG)
|
|
|---|---|---|---|
| Authors | Sonu Aggarwal , Gordon Mohr , Mark Day , Jesse Vincent | ||
| Last updated | 2013-03-02 | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 2779 (Informational) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
Network Working Group M. Day
Request for Comments: 2779 Lotus
Category: Informational S. Aggarwal
Microsoft
G. Mohr
Activerse
J. Vincent
Into Networks
February 2000
Instant Messaging / Presence Protocol Requirements
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2000). All Rights Reserved.
Abstract
Presence and Instant Messaging have recently emerged as a new medium
of communications over the Internet. Presence is a means for
finding, retrieving, and subscribing to changes in the presence
information (e.g. "online" or "offline") of other users. Instant
messaging is a means for sending small, simple messages that are
delivered immediately to online users.
Applications of presence and instant messaging currently use
independent, non-standard and non-interoperable protocols developed
by various vendors. The goal of the Instant Messaging and Presence
Protocol (IMPP) Working Group is to define a standard protocol so
that independently developed applications of instant messaging and/or
presence can interoperate across the Internet. This document defines
a minimal set of requirements that IMPP must meet.
Day, et al. Informational [Page 1]
RFC 2779 Instant Messaging/Presence Protocol February 2000
Table of Contents
1. Terminology................................................... 3
2. Shared Requirements........................................... 4
2.1. Namespace and Administration............................... 5
2.2. Scalability................................................ 5
2.3. Access Control............................................. 6
2.4. Network Topology........................................... 6
2.5. Message Encryption and Authentication...................... 7
3. Additional Requirements for PRESENCE INFORMATION.............. 7
3.1. Common Presence Format..................................... 7
3.2. Presence Lookup and Notification........................... 8
3.3. Presence Caching and Replication........................... 8
3.4. Performance................................................ 9
4. Additional Requirements for INSTANT MESSAGES.................. 9
4.1. Common Message Format...................................... 9
4.2. Reliability................................................ 10
4.3. Performance................................................ 10
4.4. Presence Format............................................ 10
5. Security Considerations....................................... 11
5.1. Requirements related to SUBSCRIPTIONS...................... 11
5.2. Requirements related to NOTIFICATION....................... 12
5.3. Requirements related to receiving a NOTIFICATION........... 13
5.4. Requirements related to INSTANT MESSAGES................... 13
6. References.................................................... 14
7. Authors' Addresses............................................ 15
8. Appendix: Security Expectations and Deriving Requirements..... 16
8.1. Presence Information....................................... 16
8.1.1. Subscription............................................ 16
8.1.2. Publication............................................. 19
8.1.3. Publication for Notification............................ 19
8.1.4. Receiving a Notification................................ 20
8.2. Instant Messaging.......................................... 21
8.2.1. Named Instant Messaging................................. 21
8.2.2. Anonymous Instant Messaging............................. 23
8.2.3. Administrator Expectations.............................. 24
Full Copyright Statement......................................... 26
Day, et al. Informational [Page 2]
RFC 2779 Instant Messaging/Presence Protocol February 2000
1. Terminology
The following terms are defined in [RFC 2778] and are used with those
definitions in this document:
ACCESS RULES
CLOSED
FETCHER
INSTANT INBOX
INSTANT MESSAGE
NOTIFICATION
OPEN
POLLER
PRESENCE INFORMATION
PRESENCE SERVICE
PRESENTITY
Show full document text