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

NOTE: This charter is a snapshot of the 67th IETF Meeting in San Diego, California USA. It may now be out-of-date.
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: 2006-03-24

Chair(s):

Robert Sparks <RjS@estacado.net>
Hisham Khartabil <hisham.khartabil@telio.no>

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

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

* The Real-time Applications and Infrastructure Area Directors were seated during the IETF 65.

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 Presence and 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.

The primary work of this group will be to generate:

1. A proposed standard SIP extension documenting the transport of
Instant Messages in SIP, compliant to the requirements for IM outlined
in RFC 2779, CPIM and in BCP 41 (so that the transport implications of
the extension with respect to network congestion are considered in the
design).

2. A proposed standard SIP event package and any related protocol
mechanisms used to support presence, compliant to the requirements for
presence outlined in RFC 2779 and CPIM.

3. An architecture for the implementation of a traditional
buddylist-based instant messaging and presence application with SIP.
Included might be new mechanisms for message confirmation delivery,
indications for when a party is in the process of typing a message,
secure buddylist manipulation operations, and the extension of the
CPIM
presence format to describe typical IM states. Each of these
mechanisms
will be consistent with a SIP-based architecture, as well as meeting
the constraints otherwise described in this charter.

All SIMPLE proposals fulfilling these goals must document the mappings
of their operation to CPIM. 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.

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.

The working group will operate in close cooperation with the IMPP
working group, which will be completing CPIM in parallel. The working
group will also cooperate with any other groups defined to standardize
other presence and IM systems, to ensure maximum sharing of
information
and avoid reinvention of the wheel. The working group will cooperate
with the SIP working group, soliciting reviews to ensure its
extensions
meet SIPs requirements. The working group will also collaborate with
the SIP WG to ensure consistent operation of the SUBSCRIBE and NOTIFY
methods across the other applications being defined for its use.

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
May 2004  Submission of SIMPLE PIDF profile to IESG for publication as Proposed Standard
May 2004  Submission of base XCAP draft to IESG for publication as Proposed Standard
May 2004  Submission of XCAP event package to IESG for for publication as Proposed Standard
May 2004  Submission of Partial Notification mechanism to IESG for publication as a Proposed Standard
May 2004  Submission of indication of instant message preparation using SIP to IESG for publication as a Proposed Standard
Jun 2004  Submission of XCAP usage for manipulation of presence document content
Jun 2004  Submission of XCAP usage for setting presence authorization to IESG for publication as Proposed Standard
Jul 2004  Submission of Filtering mechanisms to IESG for publication as a Proposed Standard
Jul 2004  Submission of CPIM mapping draft to IESG for publication as Informational
Jul 2004  Submission of instant messaging session draft to IESG for publication as a Proposed Standard
Jul 2004  Submission of instant messaging session relay drafts to IESG for publication as Proposed Standards
Aug 2004  Submission of advanced messaging requirements draft to IESG for publication as Informational
Sep 2004  Submission of proposed mechnisms meeting the advanced messaging requirements to the IESG or appropriate working group
Sep 2004  Submission of Presence/IM System Architecture draft to IESG for publication as Informational

Internet-Drafts:

  • draft-ietf-simple-message-sessions-16.txt
  • draft-ietf-simple-xcap-12.txt
  • draft-ietf-simple-xcap-list-usage-05.txt
  • draft-ietf-simple-partial-notify-08.txt
  • draft-ietf-simple-partial-pidf-format-07.txt
  • draft-ietf-simple-prescaps-ext-07.txt
  • draft-ietf-simple-presence-rules-08.txt
  • draft-ietf-simple-xcap-pidf-manipulation-usage-02.txt
  • draft-ietf-simple-msrp-relays-08.txt
  • draft-ietf-simple-partial-publish-05.txt
  • draft-ietf-simple-xcap-diff-04.txt
  • draft-ietf-simple-pres-policy-caps-01.txt
  • draft-ietf-simple-common-policy-caps-01.txt
  • draft-ietf-simple-xml-patch-ops-02.txt
  • draft-ietf-simple-imdn-01.txt
  • draft-ietf-simple-messaging-requirements-00.txt

    Request For Comments:

    RFCStatusTitle
    RFC3856 Standard A Presence Event Package for the Session Initiation Protocol (SIP)
    RFC3857 Standard A Watcher Information Event Template-Package for the Session Initiation Protocol (SIP)
    RFC3858 Standard An Extensible Markup Language (XML) Based Format for Watcher Information
    RFC3994 Standard Indication of Message Composition for Instant Messaging
    RFC4479 PS A Data Model for Presence
    RFC4480 PS RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF)
    RFC4481 PS Timed Presence Extensions to the Presence Information Data Format (PIDF) to Indicate Status Information for Past and Future Time Intervals
    RFC4482 PS CIPID: Contact Information in Presence Information Data Format
    RFC4660 PS Functional Description of Event Notification Filtering
    RFC4661 PS An Extensible Markup Language (XML) Based Format for Event Notification Filtering
    RFC4662 PS A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists

    Meeting Minutes


    Slides

    Chairs Update
    IMDN
    interdomain Optimization (problem statement)
    Presence Traffic Optimization and Server Scalability