Presence and IntComm WG

[Xiaotao Wu <>]

On Thu, 30 Oct 2003, Jiri Kuthan wrote:

> What is "profile" between PUA and Presentity?

Maybe we can use the terms in the location services:

Location Generator (LG): HP server serves as this entity. LG may use
   different means to send the location information to the
   Location Server (LS). In SIP way, the method will be PUBLISH,
 (http://www.ietf.org/internet-drafts/draft-ietf-sip-publish-01.txt)
  with pidf-lo
 (http://www.ietf.org/internet-drafts/draft-peterson-geopriv-pidf-lo-02.txt)
   in the content. There could be other ways for the LG to publish the
   information to the LS. If the HP server can send the location
   information in the DHCP option,
 (http://www.ietf.org/internet-drafts/draft-ietf-geopriv-dhcp-civil-00.txt)
   the end device can act as the LG with using a DHCP client retrieving
   the location information. The end device (like sipc) can PUBLISH the
   location information to the LS and send NOTIFY to the watchers.
   (Location Generator roughly equals to Presence User Agent)

Location Server (LS): The SIP proxy we are using can act as the location
   server. It gathers location information sent from LG.
   (In the case the end device cannot get the location information, like
    in our architecture, the end device may SUBSCRIBE to LS for his own
    location information. Using SUBSCRIBE/NOTIFY to get the location
    information seems better than polling the information from the web)
   (Location Server equals to Presence Agent)

Location Receiver (LR): The watcher who SUBSCRIBEs for the location
    information.
   (Location Receiver equals to Watcher)

 The basic arch is like

  LG -- PUBLISH --> LS -- NOTIFY --> LR

-Xiaotao

>
> I suppose that what you identify is Presentity is a publishing PUA,
> i.e., the element which changes presence state. (presentity refers
> merely to the presence identifier rather than  to an element).
> I guess my terminology is not 100% aligned with today's presence
> terminology either.
>
> it is worth mentioning that the publishing element does not need
> SIP. (there is no standard in the IETF anyhow) It may publish
> the presence document through some local interface to the presence
> server.
>
> -jiri
>
> In general, I think that presentities may publish
>
> At 03:58 PM 10/30/2003, Jeremy George wrote:
>
> >  I have two agenda items for today's call.  If anyone wants to add more,
> >please send me a note, or just speak up on the call.
> >
> >  1) Alan Whinery, U. Hawaii, has agreed to join us as a liaison
> >for the JointTechs project.  Perhaps we can walk through some of the
> >deployment issues and give Alan a handle on what we need.
> >
> >  2) As I mentioned before I promised Henning that we'd do our homework
> >in advance of the Columbia meeting and arrive with a schematic showing
> >our current understanding of RP/ALS interactions.  Something like the
> >stick figure below but as filled in as we can get it and a lot more
> >sophisticated.  Let's see if we can agree on the process for constructing
> >such a document.  Comments, ideas, criticism are all welcome.
> >
> >                    --------------
> >                    | Persistent |
> >                    | Storage    |
> >                    --------------
> >              /---------- | --------------------------\
> >             /----------- | -------------\             \
> >    --------/---    ----------------    --\---------   -\----------
> >    | Presence |    | Proxy        |    | Presence |   | Location |
> >    | Agent    |----| Redirect     |    | User     |   | Server   |
> >    ------------    | Registration |    | Agent    |   ------------
> >          |         | Server       |    ------------           |
> >          |         ----------------               \           |  beacon
> >          |                        \___             |        \___/
> >           \ Subscribe/      Register  \    Profile |        |___|
> >            \ Notify                    \           |     ____/
> >             \                           \          |    /
> >             ________                     \    ________ /
> >            /       /                        /       /
> >           /_______/                        /_______/
> >           |       |  Watcher               |       |  Presentity
> >           |       |                        |       |
> >           |_______|                        |_______|
> >
> >
> >- Jeremy
> >
> >--
> >
>
> --
> Jiri Kuthan            http://iptel.org/~jiri/
>
>


----------------------------------------------------------------wg-pic-+
For list utilities, archives, subscribe, unsubscribe, etc. please visit the
ListProc web interface at 

    http://archives.internet2.edu/

----------------------------------------------------------------wg-pic--