INTERNET-DRAFT                                        Hiroyasu Sugano
Expires December 27, 1999                                     Fujitsu

Diagrams for the IMPP Model

draft-sugano-diagrams-00.txt

STATUS OF THIS MEMO

This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026.

Internet-Drafts are working documents of the Internet Engineering Task Force
(IETF), its areas, and its working groups.  Note that other groups may also
distribute working documents as Internet-Drafts.  Internet-Drafts are draft
documents valid for a maximum of six months and may be updated, replaced, or
obsoleted by other documents at any time.  It is inappropriate to use
Internet-Drafts as reference material or to cite them other than as "work in
progress."

The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.


1.      Abstract

This is a graphical representation of the Model Document proposed by Day and
Rosenberg for the IMPP Working Group (draft-ietf-impp-model-01.txt).
2.      Diagrams

      +-------------------------------------------------+
      |                PRESENCE SERVICE                 |
      |    +---------------+      +----------------+    |
      |      | WATCHER INFO  |      | PRESENCE INFO  |    |
      |      +---------------+      +----------------+    |
      +-------------------------------------------------+
          |     |   |               ^      ^   ^
          |     |   | PRESENCE            |   |   |
          v     |   | INFO          |    |   | PRESENCE
     +---------+ |   |           +------------+    |   | INFO
     | WATCHER | |   |           | PRESENTITY |    |   |
     +---------+ v   |           +------------+    |   |
         +---------+ |               +------------+ |
         | WATCHER | |               | PRESENTITY | |
         +---------+ v               +------------+ |
              +---------+                +------------+
              | WATCHER |                | PRESENTITY |
              +---------+                +------------+

         +------------+              +-------------+
      | WATCHER UA |               | PRESENCE UA |
      +------------+               +-------------+

WATCHER UA:  WATCHER USER AGENT
PRESENCE UA: PRESENCE USER AGENT
Fig 1: Basic Model for Presence Service

      +-------------------------------------------------+
      |            INSTANT MESSAGE SERVICE              |
      |                                          |
      +-------------------------------------------------+
            ^     ^            |     |
            |    | INSTANT              |        | INSTANT
            |     | MESSAGE                    v        | MESSAGE
      +-------+   |            +---------------+  |
      | IMUA  |   |            | INSTANT INBOX |  |
      +-------+   |            +---------------+  v
            +-------+               +---------------+
            | IMUA  |               | INSTANT INBOX |
            +-------+               +---------------+

         +----------+             +----------+
      | ???????  |            | INBOX UA |
      +----------+            +----------+

IMUA: INSTANT MESSAGE USER AGENT
Fig 2: Basic Model for Instant Message Service
When sending an IM, the sender must be an entity because an INSTANT MESSAGE
SERVICE might need to authenticate the sender. At the implementation level,
the sender will usually coincide with a PRESENTITY. So, here we propose to
introduce a notion of SENDER in the model.

      +-------------------------------------------------+
      |            INSTANT MESSAGE SERVICE              |
      |                                          |
      +-------------------------------------------------+
            ^      ^                |       |
            |     | INSTANT             |         | INSTANT
            |      | MESSAGE        v         | MESSAGE
      +--------+   |            +---------------+  |
      | SENDER |   |            | INSTANT INBOX |  |
      +--------+   |            +---------------+  v
            +--------+               +---------------+
            | SENDER |               | INSTANT INBOX |
            +--------+               +---------------+

         +--------+               +----------+
         |  IMUA  |           | INBOX UA |
      +--------+              +----------+

IMUA:     INSTANT MESSAGE USER AGENT
INBOX UA: INBOX USER AGENT
Fig 2: Basic Model for Instant Message Service

     +-----------------+
     |    WATCHER      |           +------------------+
     | +------------+  | REQUEST/RESPONSE    | PRESENCE SERVICE |
     | | SUBSCRIBER |--|-------------------> |                  |
     | |            |<-|-------------------- |                  |
     | +------------+  |    NOTIFICATION     | (PRESENCE INFO)  |
     |                     |                  |                  |
     | +------------+  |                     | (PRESENCE INFO)  |
     | | FETCHER    |  | REQUEST/RESPONSE    |                  |
     | |            |--|-------------------> | (PRESENCE INFO)  |
     | | +--------+ |  |                |                  |
     | | | POLLER | |  | REQUEST/RESPONSE    |                  |
     | | |        |-|--|--------------->->-> |                  |
     | | +--------+ |  |                     +------------------+
     | +------------+  |
     +-----------------+

Fig 3: Categories of Watchers
3.      Author's Address

Hiroyasu Sugano
Fujitsu Laboratories Ltd.
64 Nishiwaki, Ohkubo-cho
Akashi 674-8555, Japan
suga@flab.fujitsu.co.jp