< draft-ietf-impp-model-02.txt   draft-ietf-impp-model-03.txt >
INTERNET-DRAFT Mark Day INTERNET-DRAFT Mark Day
Expires February 23, 2000 Lotus Expires February 28, 2000 Lotus
Jonathan Rosenberg Jonathan Rosenberg
Bell Labs Bell Labs
Hiroyasu Sugano Hiroyasu Sugano
Fujitsu Fujitsu
A Model for Presence and Instant Messaging A Model for Presence and Instant Messaging
draft-ietf-impp-model-02.txt draft-ietf-impp-model-03.txt
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026. provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Task Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
skipping to change at line 244 skipping to change at line 245
online/offline/busy/away/do not disturb), an optional COMMUNICATION online/offline/busy/away/do not disturb), an optional COMMUNICATION
ADDRESS, and optional OTHER PRESENCE MARKUP. A COMMUNICATION ADDRESS ADDRESS, and optional OTHER PRESENCE MARKUP. A COMMUNICATION ADDRESS
includes a COMMUNICATION MEANS and a CONTACT ADDRESS. One type of includes a COMMUNICATION MEANS and a CONTACT ADDRESS. One type of
COMMUNICATION MEANS, and the only one defined by this model, is COMMUNICATION MEANS, and the only one defined by this model, is
INSTANT MESSAGE SERVICE. One type of CONTACT ADDRESS, and the only INSTANT MESSAGE SERVICE. One type of CONTACT ADDRESS, and the only
one defined by this model, is INSTANT INBOX ADDRESS. However, other one defined by this model, is INSTANT INBOX ADDRESS. However, other
possibilities exist: a COMMUNICATION MEANS might indicate some form of possibilities exist: a COMMUNICATION MEANS might indicate some form of
telephony, for example, with the corresponding CONTACT ADDRESS telephony, for example, with the corresponding CONTACT ADDRESS
containing a telephone number. containing a telephone number.
+--------------------------------+ +------------------------------------+
| PRESENCE INFORMATION |
+--------------------------------+ | PRESENCE INFORMATION |
| +--------------------------+ +------------------------------------+
=>| PRESENCE TUPLE | | +-------------------------------+
| +--------------------------+ =>| PRESENCE TUPLE |
| | +-------------------+ | +-------------------------------+
| =>| CONTACT ADDRESS | | | +-------------------------+
| | +-------------------+ | =>| STATUS |
| | +-------------------+ | | +-------------------------+
| =>| STATUS | | | +-------------------------+
| | +-------------------+ | =>| COMMUNICATION ADDRESS |
| | +-------------------+ | | +-------------------------+
| =>| OTHER MARKUP | | | | +-----------------+
| +-------------------+ | | =>| CONTACT MEANS |
| +--------------------------+ | | | +-----------------+
=>| PRESENCE TUPLE | | | | +-----------------+
| +--------------------------+ | | =>| CONTACT ADDRESS |
| | +-------------------+ | | +-----------------+
| =>| CONTACT ADDRESS | | | +-------------------------+
| | +-------------------+ | =>| OTHER MARKUP |
| | +-------------------+ | +-------------------------+
| =>| STATUS | | +-------------------------------+
| | +-------------------+ =>| PRESENCE TUPLE |
| | +-------------------+ | +-------------------------------+
| =>| OTHER MARKUP | | | +-------------------------+
| +-------------------+ | =>| STATUS |
| +--------------------------+ | | +-------------------------+
=>| PRESENCE TUPLE | | | +-------------------------+
+--------------------------+ | =>| COMMUNICATION ADDRESS |
| +-------------------+ | | +-------------------------+
=>| CONTACT ADDRESS | | | | +-----------------+
| +-------------------+ | | =>| CONTACT MEANS |
| +-------------------+ | | | +-----------------+
=>| STATUS | | | | +-----------------+
| +-------------------+ | | =>| CONTACT ADDRESS |
| +-------------------+ | | +-----------------+
=>| OTHER MARKUP | | | +-------------------------+
+-------------------+ | =>| OTHER MARKUP |
| +-------------------------+
| +-------------------------------+
=>| PRESENCE TUPLE |
| +-------------------------------+
| ...
Fig. 5: The structure of PRESENCE INFORMATION Fig. 5: The structure of PRESENCE INFORMATION
STATUS is further defined by the model to have at least two states STATUS is further defined by the model to have at least two states
that interact with INSTANT MESSAGE delivery -- OPEN, in which INSTANT that interact with INSTANT MESSAGE delivery -- OPEN, in which INSTANT
MESSAGES will be accepted, and CLOSED, in which INSTANT MESSAGES will MESSAGES will be accepted, and CLOSED, in which INSTANT MESSAGES will
not be accepted. OPEN and CLOSED may also be applicable to other not be accepted. OPEN and CLOSED may also be applicable to other
COMMUNICATION MEANS -- OPEN mapping to some state meaning "available" COMMUNICATION MEANS -- OPEN mapping to some state meaning "available"
or "open for business" while CLOSED means "unavailable" or "closed to or "open for business" while CLOSED means "unavailable" or "closed to
business." The model allows STATUS to include other values, which may business." The model allows STATUS to include other values, which may
skipping to change at line 663 skipping to change at line 679
This document has provided a model for a presence and instant This document has provided a model for a presence and instant
messaging system. The purpose of the model is to provide a common messaging system. The purpose of the model is to provide a common
vocabulary for the further work of defining and implementing vocabulary for the further work of defining and implementing
interoperable presence and instant messaging protocols. interoperable presence and instant messaging protocols.
7. Acknowledgements 7. Acknowledgements
This document has been improved by comments from Jesse Vincent and This document has been improved by comments from Jesse Vincent and
Colin Benson, by the participants in the Cambridge, MA meeting on June Colin Benson, by the participants in the Cambridge, MA meeting on June
11, 1999, and by Roy Salisbury, who contributed Figure 5. The authors 11, 1999, and by Roy Salisbury, who contributed the original version
gratefully acknowledge their assistance. of Figure 5. The authors gratefully acknowledge their assistance.
8. References 8. References
[ENVY] M. Day. ''HTTP Envy'' and Presence Information Protocols. [ENVY] M. Day. ''HTTP Envy'' and Presence Information Protocols.
Internet-Draft draft-day-envy-00.txt Internet-Draft draft-day-envy-00.txt
[PIPR] M. Calsyn, L. Dusseault. Presence Information Protocol [PIPR] M. Calsyn, L. Dusseault. Presence Information Protocol
Requirements. Internet-Draft draft-dusseault-pipr-00.txt Requirements. Internet-Draft draft-dusseault-pipr-00.txt
[PRESENCE] V. Saraswat, J. Malcolm, C. Apple. The Presence [PRESENCE] V. Saraswat, J. Malcolm, C. Apple. The Presence
 End of changes. 5 change blocks. 
44 lines changed or deleted 49 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/