Using CPIM with IMP
Jabber
Outdated PIM
Session Model
rfc3428
draft-ietf-simple-presence
draft-ietf-simple-winfo-format
draft-ietf-simple-winfo-package
draft-ietf-sipping-reg-event
rfc3265
draft-ietf-simple-presencelist-package
draft-campbell-simple-cpimmsg-sessions
draft-rosenberg-simple-message-session
draft-rosenberg-simple-components
draft-rosenberg-simple-data-req
rfc3428.txt  | Session Initiation Protocol (SIP) Extension for Instant Messaging |
| Author(s) | B. Campbell, Ed., J. Rosenberg, H. Schulzrinne, C. Huitema, D. Gurle |
| Organization | ietf |
| State | proposed standard |
| Size | 41475 bytes |
| Abstract | Instant Messaging (IM) refers to the transfer of messages between users in near real-time. These messages are usually, but not required to be, short. IMs are often used in a conversational mode, that is, the transfer of messages back and forth is fast enough for participants to maintain an interactive conversation. This document proposes the MESSAGE method, an extension to the Session Initiation Protocol (SIP) that allows the transfer of Instant Messages. Since the MESSAGE request is an extension to SIP, it inherits all the request routing and security features of that protocol. MESSAGE requests carry the content in the form of MIME body parts. MESSAGE requests do not themselves initiate a SIP dialog; under normal usage each Instant Message stands alone, much like pager messages. MESSAGE requests may be sent in the context of a dialog initiated by some other SIP request. |
| draft-ietf-simple-presence-10.txt | A Presence Event Package for the Session Initiation Protocol (SIP) |
| Author(s) | Jonathan Rosenberg |
| Organization | ietf |
| Working group | simple |
| State | unknown |
| Date | 2003-01-31 |
| Size | 64256 bytes |
| Abstract | This document describes the usage of the Session Initiation Protocol (SIP) for subscriptions and notifications of presence. Presence is defined as the willingness and ability of a user to communicate with other users on the network. Historically, presence has been limited to "on-line" and "off-line" indicators; the notion of presence here is broader. Subscriptions and notifications of presence are supported by defining an event package within the general SIP event notification framework. This protocol is also compliant with the Common Presence Profile (CPP) framework. Table of Contents |
| draft-ietf-simple-winfo-format-04.txt | An Extensible Markup Language (XML) Based Format for Watcher Information |
| Author(s) | Jonathan Rosenberg |
| Organization | ietf |
| Working group | simple |
| State | unknown |
| Date | 2003-01-31 |
| Size | 28361 bytes |
| Abstract | Watchers are defined as entities that request (i.e., subscribe to) information about a resource. There is fairly complex state associated with these subscriptions. The union of the state for all subscriptions to a particular resource is called the watcher information for that resource. This state is dynamic, changing as subscribers come and go. As a result, it is possible, and indeed useful, to subscribe to the watcher information for a particular resource. In order to enable this, a format is needed to describe the state of watchers on a resource. This specification describes an XML document format for such state. Table of Contents 1 Introduction ........................................ 3 2 Terminology ......................................... 3 3 Structure of Watcher Information .................... 3 4 Computing Watcher Lists from the Document ........... 5 5 Example ............................................. 6 6 XML Schema .......................................... 7 7 Security Considerations ............................. 9 8 IANA Considerations ................................. 9 8.1 application/watcherinfo+xml MIME Registration ....... 9 8.2 URN Sub-Namespace Registration for urn:ietf:params:xml:ns:watcherinfo ............................. 10 9 Contributors ........................................ 11 10 Acknowledgements .................................... 12 11 Authors Addresses ................................... 12 12 Normative References ................................ 12 13 Informative References .............................. 13 |
| draft-ietf-simple-winfo-package-05.txt | A Watcher Information Event Template-Package for the Session Initiation Protocol (SIP) |
| Author(s) | Jonathan Rosenberg |
| Organization | ietf |
| Working group | simple |
| State | unknown |
| Date | 2003-01-31 |
| Size | 45479 bytes |
| Abstract | This document defines the watcher information template-package for the SIP event framework. Watcher information refers to the set of users subscribed to a particular resource within a particular event package. Watcher information changes dynamically as users subscribe, unsubscribe, are approved, or are rejected. A user can subscribe to this information, and therefore learn about changes to it. This event package is a template-package because it can be applied to any event package, including itself. Table of Contents |
| draft-ietf-sipping-reg-event-00.txt | A Session Initiation Protocol (SIP) Event Package for Registrations |
| Author(s) | Jonathan Rosenberg |
| Organization | ietf |
| Working group | sipping |
| State | unknown |
| Date | 2002-10-31 |
| Size | 53738 bytes |
| Abstract | This document defines a Session Initiation Protocol (SIP) event package for registrations. Through its REGISTER method, SIP allows a user agent to create, modify, and delete registrations. Registrations can also be altered by administrators in order to enforce policy. As a result, these registrations represent a piece of state in the network that can change dynamically. There are many cases where a user agent would like to be notified of changes in this state. This event package defines a mechanism by which those user agents can request and obtain such notifications. Table of Contents |
| rfc3265.txt | Session Initiation Protocol (SIP)-Specific Event Notification |
| Author(s) | A. B. Roach |
| Organization | ietf |
| State | proposed standard |
| Size | 89005 bytes |
| obsoletes | rfc2543.txt |
| updates | rfc3261.txt |
| Abstract | This document describes an extension to the Session Initiation Protocol (SIP). The purpose of this extension is to provide an extensible framework by which SIP nodes can request notification from remote nodes indicating that certain events have occurred. Concrete uses of the mechanism described in this document may be standardized in the future. Note that the event notification mechanisms defined herein are NOT intended to be a general-purpose infrastructure for all classes of event subscription and notification. |
| draft-ietf-simple-presencelist-package-01.txt
|
| draft-campbell-simple-cpimmsg-sessions-00.txt | Instant Message Transport Sessions using the CPIM Message Format |
| Author(s) | Ben Campbell |
| Organization | ietf |
| State | unknown |
| Date | 2002-10-28 |
| Size | 26956 bytes |
| Abstract | Instant Messaging (IM) refers to the transfer of messages between users in near real-time. These messages are usually, but not required to be, short. IMs are often used in a conversational mode, that is, the transfer of messages back and forth is fast enough for participants to maintain an interactive conversation. Each message can be sent independently using the SIP MESSAGE method, or messages can be associated into sessions that are initiated using SIP. The first approach is often referred to as pager-mode messaging, due to its similarity to the behavior of two way pager devices. The second approach is often called session-mode messaging, or simply message sessions. This document describes a message session mechanism based on the Common Presence and Instant Messaging message format. |
| draft-rosenberg-simple-message-session-01.txt
|
| draft-rosenberg-simple-components-01.txt
|
| draft-rosenberg-simple-data-req-01.txt%
|