SIP for Instant Messaging and Presence Leveraging Extensions (simple)
In addition to this official charter maintained by the IETF Secretariat, there is additional informati on about this working group on the Web at:
Additional SIMPLE Web Page
Last Modified: 2009-03-12
Additional information is available at tools.ietf.org/wg/simple
Chair(s):
Real-time Applications and Infrastructure Area Director(s):
- Robert Sparks <rjsparks@nostrum.com>
- Jon Peterson <jon.peterson@neustar.biz>
- Cullen Jennings <fluffy@cisco.com>
Real-time Applications and Infrastructure Area Advisor:
Technical Advisor(s):
Mailing Lists:
General Discussion: simple@ietf.orgTo 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 InitiationProtocol (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 | |
| 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 | |
| Dec 2009 | Submission of additional connection models for MSRP to IESG for Proposed Standard |
Internet-Drafts:
An Extensible Markup Language (XML) Document Format for Indicating A Change in XML Configuration Access Protocol (XCAP) Resources (0 bytes)Presence Interdomain Scaling Analysis for SIP/SIMPLE (0 bytes)
Multi-party Chat Using the Message Session Relay Protocol (MSRP) (0 bytes)
SIMPLE made Simple: An Overview of the IETF Specifications for Instant Messaging and Presence using the Session Initiation Protocol (SIP) (0 bytes)
Optimizing Federated Presence with View Sharing (0 bytes)
Models for Intra-Domain Presence and Instant Messaging (IM) Bridging (0 bytes)
An Alternative Connection Model for the Message Session Relay Protocol (MSRP) (0 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)
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)
Relay Extensions for the Message Sessions Relay Protocol (MSRP) (RFC 4976) (84244 bytes)
The Message Session Relay Protocol (MSRP) (RFC 4975) (144254 bytes)
Presence Authorization Rules (RFC 5025) (65880 bytes)
Publication of Partial Presence Information (RFC 5264) (30594 bytes)
Session Initiation Protocol (SIP) extension for Partial Notification of Presence Information (RFC 5263) (32556 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) User Agent Capability Extension to Presence Information Data Format (PIDF) (RFC 5196) (58488 bytes)
Instant Message Disposition Notification (IMDN) (RFC 5438) (83723 bytes)

