Requirements for Presence and Instant Messaging
draft-day-rpim-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mark Day | ||
| Last updated | 1998-03-16 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document is an alternative approach to defining the requirements for a presence information protocol. It may be usefully compared and contrasted with ''Presence Information Protocol Requirements'' by Lisa Dusseault, draft-dusseault-pipr-00.txt. Although worthy in many respects, that document includes numerous desiderata, design considerations, and implementation concerns. This document attempts to define only requirements, and a minimal set of requirements at that. In addition, this document treats ''presence'' and ''instant messaging'' as distinct entities for the purpose of defining requirements. We leave open the possibility of a single protocol fulfilling both sets of requirements, without requiring it.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)