Optimizing Notifications for Presence Network Agents

Document Type Expired Internet-Draft (individual)
Last updated 2008-02-18
Stream (None)
Intended RFC status (None)
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


In large presence systems deployed in multiservice networks, presence information is often known by the network in addition to, or instead of the presentity's devices (endpoints). Examples of such information include location and availability for various kinds of session establishment. Even if devices know the information, the network often has more bandwidth and better scale to keep the presence server up to date. A Presence Network Agent (PNA) can publish presence information to a Presence Server(PS). When done large scale, the basic publish operation can be inefficient. When the network has millions of subscribers, only some of which have watchers, blind Publish operations are unecessary. WINFO can be used to determine watchers, but the efficiency of maintaining WINFO per subscriber, and the size of the messages involved, make that solution unattractive. The PNA would prefer to have the Presence Server simply tell it when there was at least one watcher. This document describes an XML document stored on the PS by which the PNA maintains a list of subscribers it can provide presence for as a SIP event package that tells the PNA when the number of watchers for a presentity on the list (or a specific presence element for a presentity) goes from 0 to at least 1 or from 1 to 0.


Brian Rosen (br@brianrosen.net)
Salvatore Loreto (Salvatore.Loreto@ericsson.com)
Krisztian Kiss (krisztian.kiss@nokia.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)