-
"An Extensible Markup Language (XML) Document Format for Indicating A Change in XML Configuration Access Protocol (XCAP) Resources", Jonathan Rosenberg, Jari Urpalainen, 30-Jun-09. ( 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.
-
"Presence Interdomain Scaling Analysis for SIP/SIMPLE", Avshalom Houri, Edwin Aoki, Sriram Parameswar, Tim Rang, Vishal Singh, Henning Schulzrinne, 23-Jun-09. ( 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 Chat Using the Message Session Relay Protocol (MSRP)", Aki Niemi, Miguel Garcia, Geir Arne Sandbakken, 9-Mar-09. ( 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 chat sessions, or chat rooms,
using MSRP.
-
"SIMPLE made Simple: An Overview of the IETF Specifications for Instant Messaging and Presence using the Session Initiation Protocol (SIP)", Jonathan Rosenberg, 9-Mar-09. ( 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.
-
"Models for Intra-Domain Presence and Instant Messaging (IM) Bridging", Jonathan Rosenberg, Avshalom Houri, Colm Smyth, Francois Audet, 9-Mar-09. ( bytes)
- Presence and Instant Messaging (IM) bridging involves the sharing of
presence information and exchange of IM across multiple systems
within a single domain. As such, it is a close cousin to presence
and IM federation, which involves the sharing of presence and IM
across differing domains. Presence and IM bridging 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 presence and IM bridging. It is
meant to provide a framework for defining requirements and
specifications for presence and IM bridging.
-
"An Alternative Connection Model for the Message Session Relay Protocol (MSRP)", Christer Holmberg, Staffan Blau, 30-Jan-09. ( bytes)
- This document defines an alternative connection model for MSRP UAs.
The model differs from the standard MSRP model, as defined in RFC4975
and RFC4976 in the following ways: it uses COMEDIA for TCP connection
establishment, and it allows the usage of SDP in a more conventional
way for conveying endpoint address information. Because of this, the
model also allows for the usage of generic mainstream mechanisms for
NAT traversal, instead of using MSRP relays.
IETF Secretariat - Please send questions, comments, and/or
suggestions to ietf-web@ietf.org.
Return to Internet-Draft directory.
Return to IETF home page.