IETF Proceedings

IETF-85 Proceedings

Introduction | Area, Working Goup & BoF Reports | Plenaries | Training | Internet Research Task Force

SIP for Instant Messaging and Presence Leveraging Extensions (simple) (WG)

Minutes | Audio Archives | Jabber Logs | Mailing List Archives

Additional information is available at tools.ietf.org/wg/simple

Chair(s):

Real-time Applications and Infrastructure Area Area Director(s):

Real-time Applications and Infrastructure Area Advisor

Robert Sparks

Technical Advisor(s)

Jon Peterson

Meeting Slides:

No Slides Present

Internet-Drafts:

Request for Comments:

A Presence Event Package for the Session Initiation Protocol (SIP) (RFC 3856) (62956 bytes)
An Extensible Markup Language (XML) Based Format for Watcher Information (RFC 3858) (26416 bytes)
A Watcher Information Event Template-Package for the Session Initiation Protocol (SIP) (RFC 3857) (46221 bytes)
Indication of Message Composition for Instant Messaging (RFC 3994) (27472 bytes)
RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF) (RFC 4480) (74026 bytes)
CIPID: Contact Information for the Presence Information Data Format (RFC 4482) (22157 bytes)
Timed Presence Extensions to the Presence Information Data Format (PIDF) to Indicate Status Information for Past and Future Time Intervals (RFC 4481) (15549 bytes)
A Data Model for Presence (RFC 4479) (88399 bytes)
A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists (RFC 4662) (82778 bytes)
Functional Description of Event Notification Filtering (RFC 4660) (63886 bytes) updated by RFC 6665
An Extensible Markup Language (XML)-Based Format for Event Notification Filtering (RFC 4661) (48890 bytes)
The Extensible Markup Language (XML) Configuration Access Protocol (XCAP) (RFC 4825) (166627 bytes)
Extensible Markup Language (XML) Formats for Representing Resource Lists (RFC 4826) (68850 bytes)
An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Usage for Manipulating Presence Document Contents (RFC 4827) (22896 bytes)
The Message Session Relay Protocol (MSRP) (RFC 4975) (144254 bytes)
Relay Extensions for the Message Sessions Relay Protocol (MSRP) (RFC 4976) (84244 bytes)
Presence Authorization Rules (RFC 5025) (65880 bytes)
Session Initiation Protocol (SIP) User Agent Capability Extension to Presence Information Data Format (PIDF) (RFC 5196) (58488 bytes)
Presence Information Data Format (PIDF) Extension for Partial Presence (RFC 5262) (28527 bytes)
An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors (RFC 5261) (78036 bytes)
Session Initiation Protocol (SIP) Extension for Partial Notification of Presence Information (RFC 5263) (32556 bytes)
Publication of Partial Presence Information (RFC 5264) (30594 bytes)
Instant Message Disposition Notification (IMDN) (RFC 5438) (83723 bytes)
An Extensible Markup Language (XML) Document Format for Indicating a Change in XML Configuration Access Protocol (XCAP) Resources (RFC 5874) (49509 bytes)
An Alternative Connection Model for the Message Session Relay Protocol (MSRP) (RFC 6135) (17262 bytes)
Connection Establishment for Media Anchoring (CEMA) for the Message Session Relay Protocol (MSRP) (RFC 6714) (50543 bytes)

Charter (as of 2001-03-08):

This working group focuses on the application of the Session Initiation
Protocol (SIP, RFC 3261) to the suite of services collectively known as
instant messaging and presence (IMP). The IETF has committed to
producing an interoperable standard for these services compliant to
the requirements for IM outlined in RFC 2779 (including the security
and privacy requirements there) and in the Common Profile for Instant
Messaging (CPIM) specification, developed within the IMPP working
group. As the most common services for which SIP is used share quite a
bit in common with IMP, the adaptation of SIP to IMP seems a natural
choice given the widespread support for (and relative maturity of) the
SIP standard.

This group has completed the majority of its primary goals and will
focus on the remaining tasks documented here and concluding. Any
proposed new work will require a recharter.

The primary remaining work of this group will be to complete:

1. The MSRP proposed standard mechanism for transporting sessions of
messages initiated using the SIP, compliant to the requirments of RFC
2779, CPIM and BCP 41.

2. The XCAP framework for representing and carrying configuration and
policy information in SIMPLE systems.

3. A mechanism for representing partial changes (patches) to XML
documents and extensions to the SIMPLE publication and notification
mechanisms to convey these partial changes.

4. A mechanism for initiating and managing Instant Message group chat.

5. An annotated overview of the SIMPLE protocol definition documents.

Any SIP extensions proposed in the course of this development will,
after a last call process, be transferred to the SIP WG for
consideration as formal SIP extensions.

Any mechanisms created for managing Instant Message group chat are
intended to provide a bridge to the conferencing protocols that will
be defined in XCON. They will be limited in scope to address only
simple Instant Message chat with nicknames and will not attempt
to address complex conferencing concepts such as sidebars. Their
design must anticipate operating in conjunction with the conferencing
protocols XCON is working towards.

The working group will work within the framework for presence and IM
described in RFC 2778. The extensions it defines must also be
compliant with the SIP processes for extensions. The group cannot
modify baseline SIP behavior or define a new version of SIP for IM and
presence. If the group determines that any capabilities requiring an
extension to SIP are needed, the group will seek to define such
extensions within the SIP working group, and then use them here.