Last Modifield: 05/29/2002
1. Documenting the requirements of specific chartered tasks.
2. Documenting the usage of SIP to solve real problems that need to be solved in a standardized way.
3. Looking for commonalities among the chartered tasks and other ongoing SIP-related development, as commonalities may indicate need for general, reusable functionality in SIP.
4. Describing the requirements for any extension determined to be needed, and handing them to the SIP WG.
Besides performing needed specification of several applications of SIP, SIPPING can be seen as also working out use cases that clarify the role of SIP in the Internet, and help to ensure that Occam's razor is appropriately applied to SIP usage.
The security of all the deliverables will be of special importance. The technology for security will be keyed from a SIP security specification developed (in progress now) by the SIP Working Group.
The specific tasks for SIPPING will be:
1. PSTN and/or 3G telephony-equivalent applications that need a standardized approach
- informational guide to common call flows
- support for T.38 fax
- requirements from 3GPP for SIP usage
- framework of SIP for telephony (SIP-T)
- call transfer and call forwarding
- AAA application in SIP telephony
- mapping between SIP and ISUP
2. Messaging-like applications of SIP -
- support for hearing-/speech-impaired calling
- development of usage guidelines for subscribe-notify (RFC 2848, SIP events) to ensure commonality among applications using them, including SIMPLE WG's instant messaging.
3. Multi-party applications of SIP
- the working group will review a number of technical pieces including call transfer, subscribe-notify, SIP features negotiation, and session description protocol (SDP) capability negotiation, and will develop requirements and an initial design or framework for multi-party conferencing with SIP.
4. SIP calling to media servers
- the working group will develop a requirements draft for an approach to SIP interaction with media servers. An example is whether a voicemail server is just a box that a caller can send an INVITE to.
At a later time, the working group and chairs may request of the Area Directors that new tasks be added to the charter. Such additions to the charter will require IESG approval.
The group will work very closely with SIP working group. The group will also maintain open dialogue with the IPTEL working group, whose Call Processing Language (CPL) related to the task areas in a number of ways. The group will also coordinate closely with SIMPLE, AAA, and MMUSIC (SDP development).
SIPPING will also ensure compatibility with the work done by the now concluded PINT working group. SIPPING will encourage active participation from the Distributed Call Signaling (DCS) Group of the PacketCable Consortium for distributed telephony services, 3GPP, 3GPP2, and several ITU-T study groups.
| Done | Submit Internet-Draft on SIP-Telephony Framework to IESG for consideration as a BCP | |
| APR 02 | Submit Internet-Draft on ISUP-SIP Mapping to IESG for consideration as Proposed Standard | |
| Done | Submit Internet-Draft on Requirements for use of SIP to support telephony for the Hearing-Impaired to IESG for consideration as an Informational RFC | |
| APR 02 | Submit Internet-Draft on Call Transfer using REFER to IESG for consideration as a BCP | |
| MAY 02 | Submit Internet-Draft on Common Call Flows to IESG for consideration as a BCP | |
| MAY 02 | Using ENUM with SIP Applications to IESG for consideration as an Informational RFC | |
| MAY 02 | Submit Internet-Draft on Requirements for AAA Application in SIP Telephony to IESG for consideration as an Informational RFC | |
| Done | Submit SIP 3rd party call control to IESG for consideration as BCP | |
| JUN 02 | Submit Internet-Draft on Multi-Party/Conferencing Framework to IESG for consideration as an Informational RFC | |
| JUN 02 | Submit Internet-Draft on T.38 Fax Call Flows to IESG for consideration as a BCP | |
| JUN 02 | Submit Internet-Draft on 3G Requirements to IESG for consideration as an Informational RFC | |
| JUL 02 | Submit Internet-Draft on Mapping ISUP Overlap Signaling to SIP to IESG for consideration as a Proposed Standard | |
| AUG 02 | Submit Message Waiting SIP event package to IESG for consideration as PS | |
| Done | Submit Internet-Draft on Usage Guideline for Events (Subscribe-Notify) to IESG for consideration as an Informational RFC | |
| OCT 02 | Submit Call Info SIP event package to IESG for consideration as PS | |
| OCT 02 | Submit Conf Info SIP event package to IESG for consideration as PS | |
| NOV 02 | Review charter with Area Directors and recharter or conclude |