SIP for Instant Messaging and Presence Leveraging Extensions (simple) --------------------------------------------------------------------- Charter Last Modified: 2011-08-18 Current Status: Active Working Group Chair(s): Hisham Khartabil Ben Campbell Real-time Applications and Infrastructure Area Director(s): Gonzalo Camarillo Robert Sparks Real-time Applications and Infrastructure Area Advisor: Gonzalo Camarillo Technical Advisor(s): Jon Peterson Mailing Lists: General Discussion:simple@ietf.org To Subscribe: https://www.ietf.org/mailman//listinfo/simple In Body: subscribe Archive: http://www.ietf.org/mail-archive/web/simple/index.html Description of Working Group: 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. Goals and Milestones: Done Submission of event package for presence to IESG for publication as Proposed Standard Done Submission of watcher information drafts to IESG for publication as Proposed Standards Done Submission of proposed event list mechanism to the SIP working group Done Submission of requirements for event publishing to the IESG for publication as Proposed Standard Done Submission of proposed mechanism for event publishing to the SIP working group Done Submission of SIMPLE PIDF profile to IESG for publication as Proposed Standard Done Submission of base XCAP draft to IESG for publication as Proposed Standard Done Submission of Partial Notification mechanism to IESG for publication as a Proposed Standard Done Submission of indication of instant message preparation using SIP to IESG for publication as a Proposed Standard Done Submission of XCAP usage for manipulation of presence document content Done Submission of XCAP usage for setting presence authorization to IESG for publication as Proposed Standard Done Submission of Filtering mechanisms to IESG for publication as a Proposed Standard Done Submission of instant messaging session draft to IESG for publication as a Proposed Standard Done Submission of instant messaging session relay drafts to IESG for publication as Proposed Standards Done Submission of proposed mechanisms meeting the advanced messaging requirements to the IESG or appropriate working group Done Submission of XCAP event package to IESG or appropriate working group targeting publication as Proposed Standard Done Submission of an Instant Message Disposition Notification mechanism to the IESG for publication as a Proposed Standard Done Submission of additional connection models for MSRP to IESG for Proposed Standard Oct 2010 Submission of proposed mechanisms for initiating and managing Instant Message group chat to the IESG for publication as Proposed Standard Nov 2010 Submission of SIMPLE protocol annotated overview draft to IESG for publication as Informational Mar 2011 Conclusion of SIMPLE Internet-Drafts: Posted Revised I-D Title ------ ------- -------------------------------------------- Jun 2007 Jun 2011 Multi-party Chat Using the Message Session Relay Protocol (MSRP) Aug 2011 Aug 2011 Connection Establishment for Media Anchoring (CEMA) for the Message Session Relay Protocol (MSRP) Request For Comments: RFC Stat Published Title ------- -- ----------- ------------------------------------ RFC3856Standard Aug 2004 A Presence Event Package for the Session Initiation Protocol (SIP) RFC3857Standard Aug 2004 A Watcher Information Event Template-Package for the Session Initiation Protocol (SIP) RFC3858Standard Aug 2004 An Extensible Markup Language (XML) Based Format for Watcher Information RFC3994Standard Feb 2005 Indication of Message Composition for Instant Messaging RFC4481 PS Jul 2006 Timed Presence Extensions to the Presence Information Data Format (PIDF) to Indicate Status Information for Past and Future Time Intervals RFC4480 PS Jul 2006 RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF) RFC4482 PS Jul 2006 CIPID: Contact Information in Presence Information Data Format RFC4479 PS Jul 2006 A Data Model for Presence RFC4662 PS Aug 2006 A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists RFC4661 PS Sep 2006 An Extensible Markup Language (XML) Based Format for Event Notification Filtering RFC4660 PS Sep 2006 Functional Description of Event Notification Filtering RFC4825 PS May 2007 The Extensible Markup Language (XML) Configuration Access Protocol (XCAP) RFC4826 PS May 2007 Extensible Markup Language (XML) Formats for Representing Resource Lists RFC4827 PS May 2007 An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Usage for Manipulating Presence Document Contents RFC4976 PS Sep 2007 Relay Extensions for the Message Sessions Relay Protocol (MSRP) RFC4975 PS Sep 2007 The Message Session Relay Protocol (MSRP) RFC5025 PS Dec 2007 Presence Authorization Rules RFC5264 PS Sep 2008 Publication of Partial Presence Information RFC5263Standard Sep 2008 Session Initiation Protocol (SIP) extension for Partial Notification of Presence Information RFC5262 PS Sep 2008 Presence Information Data format (PIDF) Extension for Partial Presence RFC5261 PS Sep 2008 An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors RFC5196 PS Sep 2008 Session Initiation Protocol (SIP) User Agent Capability Extension to Presence Information Data Format (PIDF) RFC5438 PS Feb 2009 Instant Message Disposition Notification (IMDN) RFC5874 PS May 2010 An Extensible Markup Language (XML) Document Format for Indicating A Change in XML Configuration Access Protocol (XCAP) Resources RFC6135 PS Feb 2011 An Alternative Connection Model for the Message Session Relay Protocol (MSRP)