Debian Codegraph @

rfc2778.html

raw
1 <pre>Network Working Group M. Day
2 Request for Comments: 2778 Lotus
3 Category: Informational J. Rosenberg
4 dynamicsoft
5 H. Sugano
6 Fujitsu
7 February 2000
8
9
10 <span class="h1">A Model for Presence and Instant Messaging</span>
11
12 Status of this Memo
13
14 This memo provides information for the Internet community. It does
15 not specify an Internet standard of any kind. Distribution of this
16 memo is unlimited.
17
18 Copyright Notice
19
20 Copyright (C) The Internet Society (2000). All Rights Reserved.
21
22 Abstract
23
24 This document defines an abstract model for a presence and instant
25 messaging system. It defines the various entities involved, defines
26 terminology, and outlines the services provided by the system. The
27 goal is to provide a common vocabulary for further work on
28 requirements for protocols and markup for presence and instant
29 messaging.
30
31 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
32
33 A presence and instant messaging system allows users to subscribe to
34 each other and be notified of changes in state, and for users to send
35 each other short instant messages. To facilitate development of a
36 suite of protocols to provide this service, we believe that it is
37 valuable to first develop a model for the system. The model consists
38 of the various entities involved, descriptions of the basic functions
39 they provide, and most importantly, definition of a vocabulary which
40 can be used to facilitate discussion.
41
42 We note that the purpose of this model is to be descriptive and
43 universal: we want the model to map reasonably onto all of the
44 systems that are informally described as presence or instant
45 messaging systems. The model is not intended to be prescriptive or
46 achieve interoperability: an element that appears in the model will
47 not necessarily be an element of an interoperable protocol, and may
48 not even be a good idea.
49
50
51
52 <span class="grey">Day, et al. Informational [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc2778">RFC 2778</a> A Model for Presence and Instant Messaging February 2000</span>
55
56
57 In this document, each element of the model appears in upper case
58 (e.g., PRESENCE SERVICE). No term in lower case or mixed case is
59 intended to be a term of the model.
60
61 The first part of this document is intended as an overview of the
62 model. The overview includes diagrams, and terms are presented in an
63 order that is intended to help the reader understand the relationship
64 between elements. The second part of the document is the actual
65 definition of the model, with terms presented in alphabetical order
66 for ease of reference.
67
68 The overview is intended to be helpful but is not definitive; it may
69 contain inadvertent differences from the definitions in the model.
70 For any such difference, the definition(s) in the model are taken to
71 be correct, rather than the explanation(s) in the overview.
72
73 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Overview</span>
74
75 The model is intended to provide a means for understanding,
76 comparing, and describing systems that support the services typically
77 referred to as presence and instant messaging. It consists of a
78 number of named entities that appear, in some form, in existing
79 systems. No actual implementation is likely to have every entity of
80 the model as a distinct part. Instead, there will almost always be
81 parts of the implementation that embody two or more entities of the
82 model. However, different implementations may combine entities in
83 different ways.
84
85 The model defines two services: a PRESENCE SERVICE and an INSTANT
86 MESSAGE SERVICE. The PRESENCE SERVICE serves to accept information,
87 store it, and distribute it. The information stored is
88 (unsurprisingly) PRESENCE INFORMATION. The INSTANT MESSAGE SERVICE
89 serves to accept and deliver INSTANT MESSAGES to INSTANT INBOXES.
90
91 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a> PRESENCE SERVICE</span>
92
93 The PRESENCE SERVICE has two distinct sets of "clients" (remember,
94 these may be combined in an implementation, but treated separately in
95 the model). One set of clients, called PRESENTITIES, provides
96 PRESENCE INFORMATION to be stored and distributed. The other set of
97 clients, called WATCHERS, receives PRESENCE INFORMATION from the
98 service.
99
100
101
102
103
104
105
106
107
108 <span class="grey">Day, et al. Informational [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc2778">RFC 2778</a> A Model for Presence and Instant Messaging February 2000</span>
111
112
113 +---------------------------+
114 | PRESENCE SERVICE |
115 | |
116 +---------------------------+
117 ^ |
118 | |
119 | v
120 +------------+ +------------+
121 | PRESENTITY | | WATCHER |
122 +------------+ +------------+
123
124
125 Fig. 1: Overview of Presence Service
126
127 There are two kinds of WATCHERS, called FETCHERS and SUBSCRIBERS. A
128 FETCHER simply requests the current value of some PRESENTITY's
129 PRESENCE INFORMATION from the PRESENCE SERVICE. In contrast, a
130 SUBSCRIBER requests notification from the PRESENCE SERVICE of
131 (future) changes in some PRESENTITY's PRESENCE INFORMATION. A
132 special kind of FETCHER is one that fetches information on a regular
133 basis. This is called a POLLER.
134
135 +----------------WATCHER---------------+
136 | |
137 | +----FETCHER---+ +--SUBSCRIBER--+ |
138 | | | | | |
139 | | +--POLLER--+ | | | |
140 | | | | | | | |
141 | | +----------+ | | | |
142 | +--------------+ +--------------+ |
143 +--------------------------------------+
144
145 Fig. 2: Varieties of WATCHER
146
147 The PRESENCE SERVICE also has WATCHER INFORMATION about WATCHERS and
148 their activities in terms of fetching or subscribing to PRESENCE
149 INFORMATION. The PRESENCE SERVICE may also distribute WATCHER
150 INFORMATION to some WATCHERS, using the same mechanisms that are
151 available for distributing PRESENCE INFORMATION.
152
153 Changes to PRESENCE INFORMATION are distributed to SUBSCRIBERS via
154 NOTIFICATIONS. Figures 3a through 3c show the flow of information as
155 a piece of PRESENCE INFORMATION is changed from P1 to P2.
156
157
158
159
160
161
162
163
164 <span class="grey">Day, et al. Informational [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc2778">RFC 2778</a> A Model for Presence and Instant Messaging February 2000</span>
167
168
169 +---------------------------+
170 | PRESENCE SERVICE |
171 | P1 |
172 +---------------------------+
173
174
175 +------------+ +------------+
176 | P1-&gt;P2 | | P1 |
177 | PRESENTITY | | SUBSCRIBER |
178 +------------+ +------------+
179
180 Fig. 3a: NOTIFICATION (Step 1)
181
182
183
184 +---------------------------+
185 | PRESENCE SERVICE |
186 | P1-&gt;P2 |
187 +---------------------------+
188 ^
189 |P2
190 +------------+ +------------+
191 | P2 | | P1 |
192 | PRESENTITY | | SUBSCRIBER |
193 +------------+ +------------+
194
195 Fig. 3b: NOTIFICATION (Step 2)
196
197
198
199 +---------------------------+
200 | PRESENCE SERVICE |
201 | P2 |
202 +---------------------------+
203 |P2
204 v
205 +------------+ +------------+
206 | P2 | | P1-&gt;P2 |
207 | PRESENTITY | | SUBSCRIBER |
208 +------------+ +------------+
209
210 Fig. 3c: NOTIFICATION (Step 3)
211
212 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a> INSTANT MESSAGE SERVICE</span>
213
214 The INSTANT MESSAGE SERVICE also has two distinct sets of "clients":
215 SENDERS and INSTANT INBOXES. A SENDER provides INSTANT MESSAGES to
216 the INSTANT MESSAGE SERVICE for delivery. Each INSTANT MESSAGE is
217
218
219
220 <span class="grey">Day, et al. Informational [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc2778">RFC 2778</a> A Model for Presence and Instant Messaging February 2000</span>
223
224
225 addressed to a particular INSTANT INBOX ADDRESS, and the INSTANT
226 MESSAGE SERVICE attempts to deliver the message to a corresponding
227 INSTANT INBOX.
228
229 +---------------------------+
230 | INSTANT MESSAGE SERVICE |
231 | |
232 +---------------------------+
233 ^ |
234 | |
235 | v
236 +------------+ +---------------+
237 | SENDER | | INSTANT INBOX |
238 +------------+ +---------------+
239
240 Fig. 4: Overview of Instant Message Service
241
242 <span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a> Protocols</span>
243
244 A PRESENCE PROTOCOL defines the interaction between PRESENCE SERVICE,
245 PRESENTITIES, and WATCHERS. PRESENCE INFORMATION is carried by the
246 PRESENCE PROTOCOL.
247
248 An INSTANT MESSAGE PROTOCOL defines the interaction between INSTANT
249 MESSAGE SERVICE, SENDERS, and INSTANT INBOXES. INSTANT MESSAGES are
250 carried by the INSTANT MESSAGE PROTOCOL.
251
252 In terms of this model, we believe that the IMPP working group is
253 planning to develop detailed requirements and specifications for the
254 structure and formats of the PRESENCE PROTOCOL, PRESENCE INFORMATION,
255 INSTANT MESSAGE PROTOCOL, and INSTANT MESSAGES.
256
257 <span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a> Formats</span>
258
259 The model defines the PRESENCE INFORMATION to consist of an arbitrary
260 number of elements, called PRESENCE TUPLES. Each such element
261 consists of a STATUS marker (which might convey information such as
262 online/offline/busy/away/do not disturb), an optional COMMUNICATION
263 ADDRESS, and optional OTHER PRESENCE MARKUP. A COMMUNICATION ADDRESS
264 includes a COMMUNICATION MEANS and a CONTACT ADDRESS. One type of
265 COMMUNICATION MEANS, and the only one defined by this model, is
266 INSTANT MESSAGE SERVICE. One type of CONTACT ADDRESS, and the only
267 one defined by this model, is INSTANT INBOX ADDRESS. However, other
268 possibilities exist: a COMMUNICATION MEANS might indicate some form
269 of telephony, for example, with the corresponding CONTACT ADDRESS
270 containing a telephone number.
271
272
273
274
275
276 <span class="grey">Day, et al. Informational [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc2778">RFC 2778</a> A Model for Presence and Instant Messaging February 2000</span>
279
280
281 +------------------------------------+
282 | PRESENCE INFORMATION |
283 +------------------------------------+
284 | +-------------------------------+
285 =&gt;| PRESENCE TUPLE |
286 | +-------------------------------+
287 | | +-------------------------+
288 | =&gt;| STATUS |
289 | | +-------------------------+
290 | | +-------------------------+
291 | =&gt;| COMMUNICATION ADDRESS |
292 | | +-------------------------+
293 | | | +-----------------+
294 | | =&gt;| CONTACT MEANS |
295 | | | +-----------------+
296 | | | +-----------------+
297 | | =&gt;| CONTACT ADDRESS |
298 | | +-----------------+
299 | | +-------------------------+
300 | =&gt;| OTHER MARKUP |
301 | +-------------------------+
302 | +-------------------------------+
303 =&gt;| PRESENCE TUPLE |
304 | +-------------------------------+
305 | | +-------------------------+
306 | =&gt;| STATUS |
307 | | +-------------------------+
308 | | +-------------------------+
309 | =&gt;| COMMUNICATION ADDRESS |
310 | | +-------------------------+
311 | | | +-----------------+
312 | | =&gt;| CONTACT MEANS |
313 | | | +-----------------+
314 | | | +-----------------+
315 | | =&gt;| CONTACT ADDRESS |
316 | | +-----------------+
317 | | +-------------------------+
318 | =&gt;| OTHER MARKUP |
319 | +-------------------------+
320 | +-------------------------------+
321 =&gt;| PRESENCE TUPLE |
322 | +-------------------------------+
323 | ...
324
325 Fig. 5: The structure of PRESENCE INFORMATION
326
327
328
329
330
331
332 <span class="grey">Day, et al. Informational [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc2778">RFC 2778</a> A Model for Presence and Instant Messaging February 2000</span>
335
336
337 STATUS is further defined by the model to have at least two states
338 that interact with INSTANT MESSAGE delivery -- OPEN, in which INSTANT
339 MESSAGES will be accepted, and CLOSED, in which INSTANT MESSAGES will
340 not be accepted. OPEN and CLOSED may also be applicable to other
341 COMMUNICATION MEANS -- OPEN mapping to some state meaning "available"
342 or "open for business" while CLOSED means "unavailable" or "closed to
343 business." The model allows STATUS to include other values, which may
344 be interpretable by programs or only by persons. The model also
345 allows STATUS to consist of single or multiple values.
346
347 <span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a> Presence and its effect on Instant Messages</span>
348
349 An INSTANT INBOX is a receptacle for INSTANT MESSAGES. Its INSTANT
350 INBOX ADDRESS is the information that can be included in PRESENCE
351 INFORMATION to define how an INSTANT MESSAGE should be delivered to
352 that INSTANT INBOX. As noted above, certain values of the STATUS
353 marker indicate whether INSTANT MESSAGES will be accepted at the
354 INSTANT INBOX. The model does not otherwise constrain the delivery
355 mechanism or format for instant messages. Reasonable people can
356 disagree about whether this omission is a strength or a weakness of
357 this model.
358
359 <span class="h3"><a class="selflink" id="section-2.6" href="#section-2.6">2.6</a> PRINCIPALS and their agents</span>
360
361 This model includes other elements that are useful in characterizing
362 how the protocol and markup work. PRINCIPALS are the people, groups,
363 and/or software in the "real world" outside the system that use the
364 system as a means of coordination and communication. It is entirely
365 outside the model how the real world maps onto PRINCIPALS -- the
366 system of model entities knows only that two distinct PRINCIPALS are
367 distinct, and two identical PRINCIPALS are identical.
368
369 A PRINCIPAL interacts with the system via one of several user agents
370 (INBOX USER AGENT; SENDER USER AGENT; PRESENCE USER AGENT; WATCHER
371 USER AGENT). As usual, the different kinds of user agents are split
372 apart in this model even though most implementations will combine at
373 least some of them. A user agent is purely coupling between a
374 PRINCIPAL and some core entity of the system (respectively, INSTANT
375 INBOX; SENDER; PRESENTITY; WATCHER).
376
377
378
379
380
381
382
383
384
385
386
387
388 <span class="grey">Day, et al. Informational [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc2778">RFC 2778</a> A Model for Presence and Instant Messaging February 2000</span>
391
392
393 +---------------------------+
394 | PRESENCE SERVICE |
395 +---------------------------+
396 ^ |
397 | PRESENCE PROTOCOL |
398 | v
399 +------------+ +------------+
400 | PRESENTITY | | WATCHER |
401 +------------+ +------------+
402 ^ ^
403 | |
404 | |
405 o +--------------+ +-------------+ o
406 /|\ --&gt;| PRESENCE UA | | WATCHER UA |&lt;-- /|\
407 X +--------------+ +-------------+ X
408
409 (PRINCIPAL) (PRINCIPAL)
410
411 Fig. 6: A presence system
412
413
414 +---------------------------+
415 | INSTANT MESSAGE SERVICE |
416 +---------------------------+
417 ^ |
418 IM| INSTANT MESSAGE |IM
419 | PROTOCOL v
420 +------------+ +---------------+
421 | SENDER | | INSTANT INBOX |
422 +------------+ +---------------+
423 ^ ^
424 | |
425 | |
426 o +-------------+ +------------------+ o
427 /|\ --&gt;| SENDER UA | | INBOX UA |&lt;-- /|\
428 X +-------------+ +------------------+ X
429
430 (PRINCIPAL) (PRINCIPAL)
431
432 Fig. 7: An instant messaging system
433
434
435
436
437
438
439
440
441
442
443
444 <span class="grey">Day, et al. Informational [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc2778">RFC 2778</a> A Model for Presence and Instant Messaging February 2000</span>
447
448
449 <span class="h3"><a class="selflink" id="section-2.7" href="#section-2.7">2.7</a> Examples</span>
450
451 A simple example of applying the model is to describe a generic
452 "buddy list" application. These applications typically expose the
453 user's presence to others, and make it possible to see the presence
454 of others. So we could describe a buddy list as the combination of a
455 PRESENCE USER AGENT and WATCHER USER AGENT for a single PRINCIPAL,
456 using a single PRESENTITY and a single SUBSCRIBER.
457
458 We could then extend our example to instant messaging and describe a
459 generic "instant messenger" as essentially a buddy list with
460 additional capabilities for sending and receiving instant messages.
461 So an instant messenger would be the combination of a PRESENCE USER
462 AGENT, WATCHER USER AGENT, INBOX USER AGENT, and SENDER USER AGENT
463 for a single PRINCIPAL, using a single PRESENTITY, single SUBSCRIBER,
464 and single INSTANT INBOX, with the PRESENTITY's PRESENCE INFORMATION
465 including an INSTANT INBOX ADDRESS that leads to the INSTANT INBOX.
466
467 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Model</span>
468
469 ACCESS RULES: constraints on how a PRESENCE SERVICE makes PRESENCE
470 INFORMATION available to WATCHERS. For each PRESENTITY's PRESENCE
471 INFORMATION, the applicable ACCESS RULES are manipulated by the
472 PRESENCE USER AGENT of a PRINCIPAL that controls the PRESENTITY.
473
474 Motivation: We need some way of talking about hiding presence
475 information from people.
476
477 CLOSED: a distinguished value of the STATUS marker. In the context of
478 INSTANT MESSAGES, this value means that the associated INSTANT
479 INBOX ADDRESS, if any, corresponds to an INSTANT INBOX that is
480 unable to accept an INSTANT MESSAGE. This value may have an
481 analogous meaning for other COMMUNICATION MEANS, but any such
482 meaning is not defined by this model. Contrast with OPEN.
483
484 COMMUNICATION ADDRESS: consists of COMMUNICATION MEANS and CONTACT
485 ADDRESS.
486
487 COMMUNICATION MEANS: indicates a method whereby communication can
488 take place. INSTANT MESSAGE SERVICE is one example of a
489 COMMUNICATION MEANS.
490
491 CONTACT ADDRESS: a specific point of contact via some COMMUNICATION
492 MEANS. When using an INSTANT MESSAGE SERVICE, the CONTACT ADDRESS
493 is an INSTANT INBOX ADDRESS.
494
495
496
497
498
499
500 <span class="grey">Day, et al. Informational [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc2778">RFC 2778</a> A Model for Presence and Instant Messaging February 2000</span>
503
504
505 DELIVERY RULES: constraints on how an INSTANT MESSAGE SERVICE
506 delivers received INSTANT MESSAGES to INSTANT INBOXES. For each
507 INSTANT INBOX, the applicable DELIVERY RULES are manipulated by
508 the INBOX USER AGENT of a PRINCIPAL that controls the INSTANT
509 INBOX.
510
511 Motivation: We need a way of talking about filtering instant
512 messages.
513
514 FETCHER: a form of WATCHER that has asked the PRESENCE SERVICE to for
515 the PRESENCE INFORMATION of one or more PRESENTITIES, but has not
516 asked for a SUBSCRIPTION to be created.
517
518 INBOX USER AGENT: means for a PRINCIPAL to manipulate zero or more
519 INSTANT INBOXES controlled by that PRINCIPAL.
520
521 Motivation: This is intended to isolate the core functionality of
522 an INSTANT INBOX from how it might appear to be manipulated by a
523 product. This manipulation includes fetching messages, deleting
524 messages, and setting DELIVERY RULES. We deliberately take no
525 position on whether the INBOX USER AGENT, INSTANT INBOX, and
526 INSTANT MESSAGE SERVICE are colocated or distributed across
527 machines.
528
529 INSTANT INBOX: receptacle for INSTANT MESSAGES intended to be read by
530 the INSTANT INBOX's PRINCIPAL.
531
532 INSTANT INBOX ADDRESS: indicates whether and how the PRESENTITY's
533 PRINCIPAL can receive an INSTANT MESSAGE in an INSTANT INBOX. The
534 STATUS and INSTANT INBOX ADDRESS information are sufficient to
535 determine whether the PRINCIPAL appears ready to accept the
536 INSTANT MESSAGE.
537
538 Motivation: The definition is pretty loose about exactly how any
539 of this works, even leaving open the possibility of reusing parts
540 of the email infrastructure for instant messaging.
541
542 INSTANT MESSAGE: an identifiable unit of data, of small size, to be
543 sent to an INSTANT INBOX.
544
545 Motivation: We do not define "small" but we seek in this
546 definition to avoid the possibility of transporting an arbitrary-
547 length stream labelled as an "instant message."
548
549
550
551
552
553
554
555
556 <span class="grey">Day, et al. Informational [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc2778">RFC 2778</a> A Model for Presence and Instant Messaging February 2000</span>
559
560
561 INSTANT MESSAGE PROTOCOL: The messages that can be exchanged between
562 a SENDER USER AGENT and an INSTANT MESSAGE SERVICE, or between an
563 INSTANT MESSAGE SERVICE and an INSTANT INBOX.
564
565 INSTANT MESSAGE SERVICE: accepts and delivers INSTANT MESSAGES.
566
567 -- May require authentication of SENDER USER AGENTS and/or INSTANT
568 INBOXES.
569
570 -- May have different authentication requirements for different
571 INSTANT INBOXES, and may also have different authentication
572 requirements for different INSTANT INBOXES controlled by a
573 single PRINCIPAL.
574
575 -- May have an internal structure involving multiple SERVERS
576 and/or PROXIES. There may be complex patterns of redirection
577 and/or proxying while retaining logical connectivity to a
578 single INSTANT MESSAGE SERVICE. Note that an INSTANT MESSAGE
579 SERVICE does not require having a distinct SERVER -- the
580 service may be implemented as direct communication between
581 SENDER and INSTANT INBOX.
582
583 -- May have an internal structure involving other INSTANT MESSAGE
584 SERVICES, which may be independently accessible in their own
585 right as well as being reachable through the initial INSTANT
586 MESSAGE SERVICE.
587
588 NOTIFICATION: a message sent from the PRESENCE SERVICE to a
589 SUBSCRIBER when there is a change in the PRESENCE INFORMATION
590 of some PRESENTITY of interest, as recorded in one or more
591 SUBSCRIPTIONS.
592
593 Motivation: We deliberately take no position on what part of
594 the changed information is included in a NOTIFICATION.
595
596 OPEN: a distinguished value of the STATUS marker. In the context of
597 INSTANT MESSAGES, this value means that the associated INSTANT
598 INBOX ADDRESS, if any, corresponds to an INSTANT INBOX that is
599 ready to accept an INSTANT MESSAGE. This value may have an
600 analogous meaning for other COMMUNICATION MEANS, but any such
601 meaning is not defined by this model. Contrast with CLOSED.
602
603 OTHER PRESENCE MARKUP: any additional information included in the
604 PRESENCE INFORMATION of a PRESENTITY. The model does not define
605 this further.
606
607 POLLER: a FETCHER that requests PRESENCE INFORMATION on a regular
608 basis.
609
610
611
612 <span class="grey">Day, et al. Informational [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc2778">RFC 2778</a> A Model for Presence and Instant Messaging February 2000</span>
615
616
617 PRESENCE INFORMATION: consists of one or more PRESENCE TUPLES.
618
619 PRESENCE PROTOCOL: The messages that can be exchanged between a
620 PRESENTITY and a PRESENCE SERVICE, or a WATCHER and a PRESENCE
621 SERVICE.
622
623 PRESENCE SERVICE: accepts, stores, and distributes PRESENCE
624 INFORMATION.
625
626 -- May require authentication of PRESENTITIES, and/or WATCHERS.
627
628 -- May have different authentication requirements for different
629 PRESENTITIES.
630
631 -- May have different authentication requirements for different
632 WATCHERS, and may also have different authentication
633 requirements for different PRESENTITIES being watched by a
634 single WATCHER.
635
636 -- May have an internal structure involving multiple SERVERS
637 and/or PROXIES. There may be complex patterns of redirection
638 and/or proxying while retaining logical connectivity to a
639 single PRESENCE SERVICE. Note that a PRESENCE SERVICE does not
640 require having a distinct SERVER -- the service may be
641 implemented as direct communication among PRESENTITY and
642 WATCHERS.
643
644 -- May have an internal structure involving other PRESENCE
645 SERVICES, which may be independently accessible in their own
646 right as well as being reachable through the initial PRESENCE
647 SERVICE.
648
649 PRESENCE TUPLE: consists of a STATUS, an optional COMMUNICATION
650 ADDRESS, and optional OTHER PRESENCE MARKUP.
651
652 PRESENCE USER AGENT: means for a PRINCIPAL to manipulate zero or more
653 PRESENTITIES.
654
655 Motivation: This is essentially a "model/view" distinction: the
656 PRESENTITY is the model of the presence being exposed, and is
657 independent of its manifestation in any user interface. In
658 addition, we deliberately take no position on how the PRESENCE
659 USER AGENT, PRESENTITY, and PRESENCE SERVICE are colocated or
660 distributed across machines.
661
662 PRESENTITY (presence entity): provides PRESENCE INFORMATION to a
663 PRESENCE SERVICE.
664
665
666
667
668 <span class="grey">Day, et al. Informational [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc2778">RFC 2778</a> A Model for Presence and Instant Messaging February 2000</span>
671
672
673 Motivation: We don't like to coin new words, but "presentity"
674 seemed worthwhile so as to have an unambiguous term for the entity
675 of interest to a presence service. Note that the presentity is not
676 (usually) located in the presence service: the presence service
677 only has a recent version of the presentity's presence
678 information. The presentity initiates changes in the presence
679 information to be distributed by the presence service.
680
681 PRINCIPAL: human, program, or collection of humans and/or programs
682 that chooses to appear to the PRESENCE SERVICE as a single actor,
683 distinct from all other PRINCIPALS.
684
685 Motivation: We need a clear notion of the actors outside the
686 system. "Principal" seems as good a term as any.
687
688 PROXY: a SERVER that communicates PRESENCE INFORMATION, INSTANT
689 MESSAGES, SUBSCRIPTIONS and/or NOTIFICATIONS to another SERVER.
690 Sometimes a PROXY acts on behalf of a PRESENTITY, WATCHER, or
691 INSTANT INBOX.
692
693 SENDER: source of INSTANT MESSAGES to be delivered by the INSTANT
694 MESSAGE SERVICE.
695
696 SENDER USER AGENT: means for a PRINCIPAL to manipulate zero or more
697 SENDERS.
698
699 SERVER: an indivisible unit of a PRESENCE SERVICE or INSTANT MESSAGE
700 SERVICE.
701
702 SPAM: unwanted INSTANT MESSAGES.
703
704 SPOOFING: a PRINCIPAL improperly imitating another PRINCIPAL.
705
706 STALKING: using PRESENCE INFORMATION to infer the whereabouts of a
707 PRINCIPAL, especially for malicious or illegal purposes.
708
709 STATUS: a distinguished part of the PRESENCE INFORMATION of a
710 PRESENTITY. STATUS has at least the mutually-exclusive values OPEN
711 and CLOSED, which have meaning for the acceptance of INSTANT
712 MESSAGES, and may have meaning for other COMMUNICATION MEANS.
713 There may be other values of STATUS that do not imply anything
714 about INSTANT MESSAGE acceptance. These other values of STATUS may
715 be combined with OPEN and CLOSED or they may be mutually-exclusive
716 with those values.
717
718
719
720
721
722
723
724 <span class="grey">Day, et al. Informational [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc2778">RFC 2778</a> A Model for Presence and Instant Messaging February 2000</span>
727
728
729 Some implementations may combine STATUS with other entities. For
730 example, an implementation might make an INSTANT INBOX ADDRESS
731 visible only when the INSTANT INBOX can accept an INSTANT MESSAGE.
732 Then, the existence of an INSTANT INBOX ADDRESS implies OPEN,
733 while its absence implies CLOSED.
734
735 SUBSCRIBER: a form of WATCHER that has asked the PRESENCE SERVICE to
736 notify it immediately of changes in the PRESENCE INFORMATION of
737 one or more PRESENTITIES.
738
739 SUBSCRIPTION: the information kept by the PRESENCE SERVICE about a
740 SUBSCRIBER's request to be notified of changes in the PRESENCE
741 INFORMATION of one or more PRESENTITIES.
742
743 VISIBILITY RULES: constraints on how a PRESENCE SERVICE makes WATCHER
744 INFORMATION available to WATCHERS. For each WATCHER's WATCHER
745 INFORMATION, the applicable VISIBILITY RULES are manipulated by
746 the WATCHER USER AGENT of a PRINCIPAL that controls the WATCHER.
747
748 Motivation: We need a way of talking about hiding watcher
749 information from people.
750
751 WATCHER: requests PRESENCE INFORMATION about a PRESENTITY, or WATCHER
752 INFORMATION about a WATCHER, from the PRESENCE SERVICE. Special
753 types of WATCHER are FETCHER, POLLER, and SUBSCRIBER.
754
755 WATCHER INFORMATION: information about WATCHERS that have received
756 PRESENCE INFORMATION about a particular PRESENTITY within a
757 particular recent span of time. WATCHER INFORMATION is maintained
758 by the PRESENCE SERVICE, which may choose to present it in the
759 same form as PRESENCE INFORMATION; that is, the service may choose
760 to make WATCHERS look like a special form of PRESENTITY.
761
762 Motivation: If a PRESENTITY wants to know who knows about it, it
763 is not enough to examine only information about SUBSCRIPTIONS. A
764 WATCHER might repeatedly fetch information without ever
765 subscribing. Alternately, a WATCHER might repeatedly subscribe,
766 then cancel the SUBSCRIPTION. Such WATCHERS should be visible to
767 the PRESENTITY if the PRESENCE SERVICE offers WATCHER INFORMATION,
768 but will not be appropriately visible if the WATCHER INFORMATION
769 includes only SUBSCRIPTIONS.
770
771 WATCHER USER AGENT: means for a PRINCIPAL to manipulate zero or more
772 WATCHERS controlled by that PRINCIPAL.
773
774
775
776
777
778
779
780 <span class="grey">Day, et al. Informational [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc2778">RFC 2778</a> A Model for Presence and Instant Messaging February 2000</span>
783
784
785 Motivation: As with PRESENCE USER AGENT and PRESENTITY, the
786 distinction here is intended to isolate the core functionality of
787 a WATCHER from how it might appear to be manipulated by a product.
788 As previously, we deliberately take no position on whether the
789 WATCHER USER AGENT, WATCHER, and PRESENCE SERVICE are colocated or
790 distributed across machines.
791
792 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
793
794 This document provides a model and vocabulary for systems with
795 certain intrinsic security issues. In particular, presence and
796 instant messaging systems must deal with "the three S's": STALKING,
797 SPOOFING, and SPAM. ACCESS RULES, VISIBILITY RULES, and WATCHER
798 INFORMATION are intended to deal with STALKING. The several kinds of
799 authentication mentioned for INSTANT MESSAGE SERVICE and PRESENCE
800 SERVICE are intended to deal with SPOOFING. DELIVERY RULES are
801 intended to deal with SPAM.
802
803 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Conclusion</span>
804
805 This document has provided a model for a presence and instant
806 messaging system. The purpose of the model is to provide a common
807 vocabulary for the further work of defining and implementing
808 interoperable presence and instant messaging protocols.
809
810 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgements</span>
811
812 This document has been improved by comments from Jesse Vincent and
813 Colin Benson, by the participants in the Cambridge, MA meeting on
814 June 11, 1999, and by Roy Salisbury, who contributed the original
815 version of Figure 5. The authors gratefully acknowledge their
816 assistance.
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836 <span class="grey">Day, et al. Informational [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc2778">RFC 2778</a> A Model for Presence and Instant Messaging February 2000</span>
839
840
841 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Authors' Addresses</span>
842
843 Mark Day
844 SightPath, Inc.
845 135 Beaver Street
846 Waltham, MA 02452
847 USA
848
849 EMail: [email protected]
850 (Formerly [email protected])
851
852
853 Jonathan Rosenberg
854 dynamicsoft
855 200 Executive Drive
856 Suite 120
857 West Orange, NJ 07046
858
859 Email: [email protected]
860
861
862 Hiroyasu Sugano
863 Fujitsu Laboratories Ltd.
864 64 Nishiwaki, Ohkubo-cho
865 Akashi 674-8555
866 Japan
867
868 EMail: [email protected]
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892 <span class="grey">Day, et al. Informational [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc2778">RFC 2778</a> A Model for Presence and Instant Messaging February 2000</span>
895
896
897 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Full Copyright Statement</span>
898
899 Copyright (C) The Internet Society (2000). All Rights Reserved.
900
901 This document and translations of it may be copied and furnished to
902 others, and derivative works that comment on or otherwise explain it
903 or assist in its implementation may be prepared, copied, published
904 and distributed, in whole or in part, without restriction of any
905 kind, provided that the above copyright notice and this paragraph are
906 included on all such copies and derivative works. However, this
907 document itself may not be modified in any way, such as by removing
908 the copyright notice or references to the Internet Society or other
909 Internet organizations, except as needed for the purpose of
910 developing Internet standards in which case the procedures for
911 copyrights defined in the Internet Standards process must be
912 followed, or as required to translate it into languages other than
913 English.
914
915 The limited permissions granted above are perpetual and will not be
916 revoked by the Internet Society or its successors or assigns.
917
918 This document and the information contained herein is provided on an
919 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
920 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
921 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
922 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
923 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
924
925 Acknowledgement
926
927 Funding for the RFC Editor function is currently provided by the
928 Internet Society.
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948 Day, et al. Informational [Page 17]
949 </pre>