The charter of the Session Initiation Proposal Investigation (sipping) working group in the Transport Area of the IETF has been updated. For additional information, please contact the Area Directors or the working group Chairs. +++ Session Initiation Proposal Investigation (sipping) Current Status: Active Working Group Chair(s): Gonzalo Camarillo <gonzalo.camarillo@ericsson.com> Dean Willis <dean.willis@softarmor.com> Rohan Mahy <rohan@ekabal.com> Transport Area Director(s): Allison Mankin <mankin@psg.com> Jon Peterson <jon.peterson@neustar.biz> Transport Area Advisor: Allison Mankin <mankin@psg.com> Secretary(ies): Oscar Novo <Oscar.Novo@ericsson.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 extensions to SIP needed for those applications. Such requirements will be referred to the SIP working group for development of any new SIP method, header, or option-tag as described in Change Policy for SIP (RFC 3467). 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. Examples of important topics identified are the session policy architecture, allowing network entities to convey policy into an User Agent's activity; requirements analysis for session border controllers to determine how best such devices can operate with SIP usage; and guidance on IPv4-IPv6 co-existence support by SIP and SIP-supported media. 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 pass there hurdles, and handing the development task 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. Goals and Milestones: Done Submit Internet-Draft on SIP-Telephony Framework to IESG for consideration as a BCP 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 RFC 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 RFC 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 RFC Done Submit Internet-Drafts Basic and PSTN Call Flows to IESG fro consideration as BCPs Done Requirements for Content Indirection in SIP Done Submit Message Waiting SIP event package to IESG for consideration as PS Done Using ENUM with SIP Applications to IESG for consideration as an Informational RFC Done Requirements for Reuse of Connections in SIP Done Submit Internet-Draft on T.38 Fax Call Flows to IESG for consideration as a BCP 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 RFC Done Sip Interworking with QSIG Done 3pcc Transcoding to IESG as Info Done KPML to IESG as PS Done Conferencing Requirements to IESG as Info Done Conferencing Framework to IESG as Info Done Conferencing Call Control-Conferencing to IESG as BCP Done End-to-Middle Security Requirements to IESG as Info Done Configuration Framework to the IESG as a PS Oct 05 Revise Charter Nov 05 Requirements for Consent-based Communications in SIP to IESG as Info Nov 05 Submit I-D on Subscriptions to Ad-Hoc Resource Lists to the IESG as PS Nov 05 Submit I-D on Multiple REFER to the IESG as PS Nov 05 Submit I-D on Ad-Hoc Conferencing using URI lists to the IESG as PS Nov 05 Submit URI List Transport Mechanism to the IESG as PS Nov 05 Framework for Consent-based Communications in SIP to IESG Nov 05 Session Policy Requirements to IESG as Info Dec 05 Requirements on Trait-Based Authorization to IESG as Info Dec 05 Transcoding Framework to IESG as Info Dec 05 Transcoding with Conf Bridge to IESG as Info Dec 05 Service Quality Reporting to IESG as PS Jan 06 Session Independent Policy Mechanism to the IESG as PS Jan 06 Session Specific Policy Mechanism to the IESG as PS Jan 06 SIP Security Flows to IESG as Info Feb 06 SIP Service Examples to IESG as Info Feb 06 IPv6 Transition in SIP to the IESG as Info Mar 06 Revise Charter _______________________________________________ IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
