"Session Initiation Protocol (SIP) extension for Partial Notification of Presence Information", Mikko Lonnfors, Jose Costa-Requena, Eva Leppanen, Hisham Khartabil, 21-Jan-08. ( bytes)

By default, presence delivered using the Presence Event Package for the Session Initiation Protocol (SIP) is represented in the Presence Information Data Format (PIDF). A PIDF document contains a set of elements, each representing a different aspect of the presence being reported. When any subset of the elements change, even just a single element, a new document containing the full set of elements is delivered. This memo defines an extension allowing delivery of only the presence data that has actually changed.

"Presence Information Data format (PIDF) Extension for Partial Presence", Mikko Lonnfors, Eva Leppanen, Hisham Khartabil, Jari Urpalainen, 19-Nov-07. ( bytes)

The Presence Information Document Format (PIDF) specifies the baseline XML based format for describing presence information. One of the characteristic of the PIDF is that the document always needs to carry all presence information available for the presentity. In some environments where low bandwidth and high latency links can exist it is often beneficial to limit the amount of transported information over the network. This document introduces a new MIME type which enables transporting of either only the changed parts or the full PIDF based presence information.

"Session Initiation Protocol (SIP) User Agent Capability Extension to Presence Information Data Format (PIDF)", Mikko Lonnfors, Krisztian Kiss, 14-May-08. ( bytes)

Presence Information Data Format (PIDF) defines a common presence data format for Common Profile for Presence (CPP) compliant Presence protocols. This memo defines an extension to represent SIP User Agent capabilities in the Presence Information Document Format (PIDF) compliant presence documents.

"Publication of Partial Presence Information", Aki Niemi, Mikko Lonnfors, Eva Leppanen, 20-Feb-08. ( bytes)

The Session Initiation Protocol (SIP) Extension for Event State Publication describes a mechanism with which a presence user agent is able to publish presence information to a presence agent. Using the Presence Information Data Format (PIDF), each presence publication contains full state, regardless of how much of that information has actually changed since the previous update. As a consequence, updating a sizeable presence document with small changes bears a considerable overhead and is therefore inefficient. Especially with low bandwidth and high latency links, this can constitue a considerable burden to the system. This memo defines a solution that aids in reducing the impact of those constraints and increases transport efficiency by introducing a mechanism that allows for publication of partial presence information.

"An Extensible Markup Language (XML) Document Format for Indicating A Change in XML Configuration Access Protocol (XCAP) Resources", Jonathan Rosenberg, Jari Urpalainen, 5-May-08. ( bytes)

This specification defines a document format that can be used to indicate that a change has occurred in a document managed by the Extensible Markup Language (XML) Configuration Access Protocol (XCAP). This format indicates the document that has changed and its former and new entity tags. It also can indicate the specific change that was made in the document, using an XML patch format. This format allows also indications of element and attribute content of an XML document. XCAP diff documents can be delivered to clients using a number of means, including a Session Initiation Protocol (SIP) event package.

"An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors", Jari Urpalainen, 16-Nov-07. ( bytes)

Extensible Markup Language (XML) documents are widely used as containers for the exchange and storage of arbitrary data in today's systems. In order to send changes to an XML document, an entire copy of the new version must be sent, unless there is a means of indicating only the portions that have changed. This document describes an XML patch framework utilizing XML Path language (XPath) selectors. These selector values and updated new data content constitute the basis of patch operations described in this document. In addition to them, with basic , and directives a set of patches can then be applied to update an existing XML document.

"Instant Message Disposition Notification", Eric Burger, Hisham Khartabil, 1-Apr-08. ( bytes)

Instant Messaging (IM) refers to the transfer of messages between users in real-time. This document provides a mechanism whereby endpoints can request Instant Message Disposition Notifications (IMDN), including delivery, processing, and read notifications, for page-mode instant messages. The Common Profile for Instant Messaging (CPIM) data format specified in RFC 3862 is extended with new header fields that enable endpoints to request IMDNs. A new message format is also defined to convey IMDNs. This document also describes how SIP entities behave using this extension.

"Presence Interdomain Scaling Analysis for SIP/SIMPLE", Avshalom Houri, Edwin Aoki, Sriram Parameswar, Tim Rang, Vishal Singh, Henning Schulzrinne, 25-Feb-08. ( bytes)

The document analyzes the traffic that is generated due to presence subscriptions between domains. It is shown that the amount of traffic can be extremely big. In addition to the very large traffic the document also analyzes the affects of a large presence system on the memory footprint and the CPU load. Current approved and in work optimizations to the SIP protocol are analyzed with the possible impact on the load. Separate documents contain the requirements for optimizations and suggestions for new optimizations.

"Multi-party Instant Message (IM) Sessions Using the Message Session Relay Protocol (MSRP)", Aki Niemi, Miguel Garcia-Martin, Geir Arne Sandbakken, 4-Feb-08. ( bytes)

The Message Session Relay Protocol (MSRP) defines a mechanism for sending instant messages within a peer-to-peer session, negotiated using the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP). This document defines the necessary tools for establishing multi-party instant messaging (IM) sessions, or chat rooms, with MSRP.

"SIMPLE made Simple: An Overview of the IETF Specifications for Instant Messaging and Presence using the Session Initiation Protocol (SIP)", Jonathan Rosenberg, 24-Feb-08. ( bytes)

The IETF has produced many specifications related to Presence and Instant Messaging with the Session Initiation Protocol (SIP). Collectively, these specifications are known as SIMPLE - SIP for Instant Messaging and Presence Leveraging Extensions. This document serves as a guide to the SIMPLE suite of specifications. It breaks them up into categories and explains what each is for and how they relate to each other.

"Optimizing Federated Presence with View Sharing", Jonathan Rosenberg, Steve Donovan, Kathleen McMurry, 21-Feb-08. ( bytes)

Presence federation refers to the exchange of presence information between systems. One of the primary challenges in presence federation is scale. With a large number of watchers in one domain obtaining presence for many presentities in another, the amount of notification traffic is large. This document describes an extension to the Session Initiation Protocol (SIP) event framework, called view sharing. View sharing can substantially reduce the amount of traffic, but requires a certain level of trust between domains. View sharing allows the amount of presence traffic between domains to achieve the theoretical lower bound on information exchange in any presence system.

"Models for Intra-Domain Presence Federation", Jonathan Rosenberg, Avshalom Houri, 21-Feb-08. ( bytes)

Presence federation involves the sharing of presence information across multiple presence systems. Most often, presence federation is assumed to be between different organizations, such as between two enterprises or between and enterprise and a service provider. However, federation can occur within a single organization or domain. This can be the result of a multi-vendor network, or a consequence of a large organization that requires partitioning. This document examines different use cases and models for intra-domain federation.

Return to Internet-Draft directory.

Return to IETF home page.