Concluded WG Session Initiation Proposal Investigation (sipping)
Note: The data for concluded WGs is occasionally incorrect.
| WG | Name | Session Initiation Proposal Investigation | |
|---|---|---|---|
| Acronym | sipping | ||
| Area | Real-time Applications and Infrastructure Area (rai) | ||
| State | Concluded | ||
| Charter | charter-ietf-sipping-04 Approved | ||
| Document dependencies | |||
| Additional resources | Additional SIPPING Web Page | ||
| Personnel | Chairs | Gonzalo Camarillo, Mary Barnes | |
| Area Director | Robert Sparks | ||
| Secretary | Oscar Novo | ||
| Liaison Contacts | Gonzalo Camarillo, Jean-Francois Mule | ||
| Mailing list | Address | sipping@ietf.org | |
| To subscribe | sipping-request@ietf.org | ||
| Archive | https://mailarchive.ietf.org/arch/browse/sipping |
Final Charter for 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:
-
Documenting the requirements of specific chartered tasks.
-
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; guidance on IPv4-IPv6
co-existence support by SIP and SIP-supported media; and
inclusion of real-time text conversation (ToIP), service
invocations benefitting hearing and speech impaired users,
and other SIP equal access services as requirements are proposed. -
Looking for commonalities among the chartered tasks and ongoing
SIP-related development, as commonalities may indicate for general,
reusable functionality in SIP. -
Describing the requirements for any extension determined to pass
there hurdles, and handing the development task to the SIP WG. -
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.
Milestones
| Date | Milestone | Associated documents |
|---|---|---|
| Apr 2009 | Overload Design Considerations to IESG as Info | |
| Mar 2009 | Revise Charter | |
| Mar 2009 | NAT Scenarios to IESG as Info | |
| Jan 2009 | User Agent Profile for Media Policy to the IESG as PS | |
| Jan 2009 | Overload Design Considerations WGLC | |
| Jan 2009 | Schema and Guidelines for SIP User Agent Profile Datasets to IESG as PS | |
| Dec 2008 | Updates to Asserted Identity in SIP to IESG as Info | |
| Nov 2008 | Presence Scaling Requirements to IESG as Info | |
| Oct 2008 | Schema and Guidelines for SIP User Agent Profile Datasets WGLC | |
| Sep 2008 | Service Identification to IESG as INFO | |
| Aug 2008 | Presence Scaling Requirements WGLC |
Done milestones
| Date | Milestone | Associated documents |
|---|---|---|
| Done | Service Identification WGLC | |
| Done | Updates to Asserted Identity in SIP WGLC | |
| Done | Call Control Framework to the IESG as Info | |
| Done | SIP Offer/Answer Examples to IESG as Info | |
| Done | WGLC NAT scenarios | |
| Done | SIP Race Condition Examples to IESG as Info | |
| Done | Requirements for Management of Overload in SIP to IESG as Info | |
| Done | WGLC SIP Race Condition Examples | |
| Done | SIP Torture Tests for IPv6 to the IESG as Info | |
| Done | SIP Call Control - Transfer to IESG as Info | |
| Done | WGLC SIP Offer/Answer Examples | |
| Done | WGLC Requirements for Management of Overload in SIP | |
| Done | Session Policy package to the IESG as PS | |
| Done | SPAM problems in SIP to IESG as Info | |
| Done | WGLC SIP Torture Tests for IPv6 | |
| Done | WGLC Call Control Framework | |
| Done | Session Border Controller requirements to IESG as Info | |
| Done | Multiple Dialog Usages to IESG as Info | |
| Done | WGLC Session Policy package | |
| Done | WGLC User Agent Profile for Media Policy | |
| Done | WGLC Session Border Controller requirements | |
| Done | WGLC SPAM problems in SIP | |
| Done | Format Extension for Capacity Attributes in Resource Lists to the IESG as PS | |
| Done | SIP Service Examples to IESG as Info | |
| Done | WGLC Multiple Dialog Usages | |
| Done | Framework for Realtime Text over IP to IESG as Informational | |
| Done | WGLC SIP Service Examples | |
| Done | WGLC IPv6 Transition | |
| Done | IPv6 Transition in SIP to the IESG as Info | |
| Done | Service Quality Reporting to IESG as PS | |
| Done | Requirements on Trait-Based Authorization to IESG as Info | |
| Done | Transcoding Framework to IESG as Info | |
| Done | Transcoding with Conf Bridge to IESG as Info | |
| Done | Submit URI List Transport Mechanism to the IESG as PS | |
| Done | Framework for Consent-based Communications in SIP to IESG | |
| Done | Requirements for Consent-based Communications in SIP to IESG as Info | |
| Done | Configuration Framework to the IESG as a PS | |
| Done | End-to-Middle Security Requirements to IESG as Info | |
| Done | Conferencing Call Control-Conferencing to IESG as BCP | |
| Done | Conferencing Framework to IESG as Info | |
| Done | Conferencing Requirements to IESG as Info | |
| Done | KPML to IESG as PS | |
| Done | 3pcc Transcoding to IESG as Info | |
| Done | Sip Interworking with QSIG | |
| Done | Submit Internet-Draft on Requirements for AAA Application in SIP Telephony to IESG for consideration as an Informational RFC | |
| Done | Requirements for SIP Request History | |
| Done | Submit Internet-Draft on T.38 Fax Call Flows to IESG for consideration as a BCP | |
| Done | Requirements for Reuse of Connections in SIP | |
| Done | Using ENUM with SIP Applications to IESG for consideration as an Informational RFC | |
| Done | Submit Message Waiting SIP event package to IESG for consideration as PS | |
| Done | Requirements for Content Indirection in SIP | |
| Done | Submit Internet-Drafts Basic and PSTN Call Flows to IESG fro consideration as BCPs | |
| Done | Submit Internet-Draft on Usage Guideline for Events (Subscribe-Notify) 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 3G Requirements 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 Requirements for use of SIP to support telephony for the Hearing-Impaired to IESG for consideration as an Informational RFC | |
| Done | Submit Internet-Draft on ISUP-SIP Mapping to IESG for consideration as Proposed Standard | |
| Done | Submit Internet-Draft on SIP-Telephony Framework to IESG for consideration as a BCP |