The Session Initiation Proposal Investigation (sipping) working group in the Transport Area of the IETF has been rechartered. For additional information, please contact the Area Directors or the working group Chairs. Session Initiation Proposal Investigation (sipping) ==================================================== Current Status: Acrive Working Group Chair(s): Gonzalo Camarillo <gonzalo.camarillo@ericsson.com> Dean Willis <dean.willis@softarmor.com> Rohan Mahy <rohan@cisco.com> Transport Area Director(s): Allison Mankin <mankin@psg.com> Jon Peterson <jon.peterson@neustar.biz> Transport Area Advisor: Allison Mankin <mankin@psg.com> Mailing Lists: General Discussion: sipping@ietf.org To Subscribe: sipping-request@ietf.org In Body: (un)subscribe Archive: http://www.ietf.org/mail-archive/web/sipping/index.html Description of Working Group: The Session Initiation Protocol Project INvestiGation (SIPPING) working group is chartered to document the use of SIP for several applications related to telephony and multimedia, and to develop requirements for any extensions to SIP needed for those applications. Such requirements will be referred to the SIP working group for development of any new SIP method or Guiding principles for the performance of SIPPING's work will include: 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 ongoing SIP-related development, as commonalities may indicate for general, reusable functionality in SIP. 4. Describing the requirements for any extension determined to and handing them to the SIP WG. 5. Developing procedures and requirements for configuration and delivery of SIP User Profiles 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 the SIP Security specification within RFC 3261, and additional SIP specifications as they apply. 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 - requirements from 3GPP for SIP - 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 - 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 a framework for multi-party conferencing with SIP. 4. SIP calling to media - the working group will develop a requirements draft 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. 5. SIP URI-List services - the working group will develop requirements for SIP list services mechanisms enabling a client to request that a server distribute a specific SIP request to a list of recipient URIs. The working group will develop a mechanism to transport this list of recipient URIs (a URI-list) from a SIP client to SIP server in conjunction with the request (a request-contained list). The working group will also specify mechanisms (presumed not to be SIP mechanims) for storing, modifying, or retrieving a URI-list stored on a server (stored URI-lists). The working group will specify the use of URI-lists with various SIP request types for which list services are appropriate with both stored and request-contained URI-lists. The working group will also develop requirements and specifications for a positive opt-in mechanism by which list servers can prevent amplification of attacks and relay abuses. 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) is related to the task areas in a number of areas. 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. G&M: Done Submit Internet-Draft on SIP-Telephony Framework to IESG for consideration as a Proposed Standard Done 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 Done Submit SIP 3rd party call control to IESG for consideration as BCP Done Submit Internet-Draft on 3G Requirements to IESG for consideration as an Informational Done Submit Internet-Draft on Mapping ISUP Overlap Signaling to SIP to IESG for consideration as a Proposed Standard Done Submit Internet-Draft on Usage Guideline for Events (Subscribe-Notify) to IESG for consideration as an Informational Done Submit Internet-Drafts Basic and PSTN Call Flows to IESG for consideration as an Informational Done Requirements for Content Indirection Done Submit Message Waiting SIP event package to IESG for consideration as a Proposed Standard Done Using ENUM with SIP Applications to IESG for consideration as an Informational Done Requirements for Reuse of Connections Done Requirements for SIP Request History Done Submit Internet-Draft on Requirements for AAA Application in SIP Telephony to IESG for consideration as an Informational Done Sip Interworking with QSIG for BCP Jun 04 3pcc Transcoding to IESG as Info Jul 04 KPML to IESG as PS Aug 04 Conferencing Requirements to IESG as Info Aug 04 Conferencing Framework to IESG as Info Aug 04 Conferencing Call Control-Conferencing to IESG as BCP Sep 04 Location Requirements to IESG as Info Sep 04 End-to-Middle Security Requirements to IESG as Info Sep 04 Requirements on Trait-Based Authorization to IESG as Info Oct 04 Configuration Framework to the IESG as a PS Oct 04 Submit Requirements and Framework for Exploders to the IESG as PS Oct 04 Submit Opt-in/Opt-out Mechanism for Exploders to the IESG as PS Oct 04 Submit URI List Transport Mechanism to the IESG as PS Nov 04 Submit I-D on Ad-Hoc Conferencing using URI lists to the IESG as PS Nov 04 Submit I-D on MESSAGE Exploders to the IESG as PS Nov 04 Submit I-D on Multiple REFER to the IESG as PS Nov 04 Submit I-D on Subscriptions to Ad-Hoc Resource Lists to the IESG as PS Dec 04 Event Filtering Requirements to the IESG Dec 04 Caller Preferences Use Cases Dec 04 SIP Service Examples Dec 04 Session Policy Requirements to IESG as Info Jan 05 Session Independent Policy Mechanism to the IESG as PS Feb 05 Transcoding with Conf Bridge to IESG as Info Feb 05 Transcoding Framework to IESG as Info Mar 05 Session Specific Policy Mechanism to the IESG as PS Apr 05 Review charter with Area Directors and recharter or conclude _______________________________________________ IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
