SIP for Instant Messaging and Presence Leveraging Extensions (simple)

In addition to this official charter maintained by the IETF Secretariat, there is additional information about this working group on the Web at:

       Additional SIMPLE Web Page

Last Modified: 2007-03-21

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

Chair(s):

  • Robert Sparks <RjS@estacado.net>

  • Hisham Khartabil <hisham.khartabil@gmail.com>

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

  • Jon Peterson <jon.peterson@neustar.biz>
  • Cullen Jennings <fluffy@cisco.com>

    Real-time Applications and Infrastructure Area Advisor:

  • Jon Peterson <jon.peterson@neustar.biz>

    Technical Advisor(s):

  • Jon Peterson <jon.peterson@neustar.biz>

    Mailing Lists:

    General Discussion: simple@ietf.org
    To Subscribe: simple-request@ietf.org
    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
    Feb 2007  Submission of proposed mechanisms meeting the advanced messaging requirements to the IESG or appropriate working group
    Feb 2007  Submission of XCAP event package to IESG or appropriate working group targeting publication as Proposed Standard
    Feb 2007  Submission of an Instant Message Disposition Notification mechanism to the IESG for publication as a Proposed Standard
    Mar 2007  Submission of a performance and scalability analysis of the SIMPLE presence mechanisms to the IESG for publication as Informational
    Jun 2007  Submission of SIMPLE protocol annotated overview draft to IESG for publication as Informational
    Aug 2007  Submission of proposed mechanisms for initiating and managing Instant Message group chat to the IESG for publication as Proposed Standard
    Aug 2007  Conclusion of SIMPLE

    Internet-Drafts:

    The Message Session Relay Protocol (144378 bytes)
    Session Initiation Protocol (SIP) extension for Partial Notification of Presence Information (32617 bytes)
    Presence Information Data format (PIDF) Extension for Partial Presence (28348 bytes)
    Session Initiation Protocol (SIP) User Agent Capability Extension to Presence Information Data Format (PIDF) (58089 bytes)
    Presence Authorization Rules (64987 bytes)
    Relay Extensions for the Message Sessions Relay Protocol (MSRP) (85753 bytes)
    Publication of Partial Presence Information (31196 bytes)
    An Extensible Markup Language (XML) Document Format for Indicating A Change in XML Configuration Access Protocol (XCAP) Resources (24443 bytes)
    An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors (45940 bytes)
    Instant Message Disposition Notification (74368 bytes)
    Problem Statement for SIP/SIMPLE (104364 bytes)
    Multi-party Instant Message (IM) Sessions Using the Message Session Relay Protocol (MSRP) (68185 bytes)

    Request For Comments:

    A Presence Event Package for the Session Initiation Protocol (SIP) (RFC 3856) (62956 bytes)
    A Watcher Information Event Template-Package for the Session Initiation Protocol (SIP) (RFC 3857) (46221 bytes)
    An Extensible Markup Language (XML) Based Format for Watcher Information (RFC 3858) (26416 bytes)
    Indication of Message Composition for Instant Messaging (RFC 3994) (27472 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)
    RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF) (RFC 4480) (74026 bytes)
    CIPID: Contact Information in Presence Information Data Format (RFC 4482) (22157 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)
    An Extensible Markup Language (XML) Based Format for Event Notification Filtering (RFC 4661) (48890 bytes)
    Functional Description of Event Notification Filtering (RFC 4660) (63886 bytes)
    An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Usage for Manipulating Presence Document Contents (RFC 4827) (22896 bytes)
    Extensible Markup Language (XML) Formats for Representing Resource Lists (RFC 4826) (68850 bytes)
    The Extensible Markup Language (XML) Configuration Access Protocol (XCAP) (RFC 4825) (166627 bytes)
    IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.

    Return to working group directory.

    Return to IETF home page.