datatracker.ietf.org
Session Initiation Protocol (sip)
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Personnel | |
| Chairs: |
Keith Drage <keith.drage@alcatel-lucent.com> Dean Willis <dean.willis@softarmor.com> |
| Area Director: | ? |
| Tech Advisor: |
Dan Romascanu <dromasca@avaya.com> |
|
Mailing List |
|
| Address: | sip@ietf.org |
| To Subscribe: | sip-request@ietf.org |
| Archive: | http://www.ietf.org/mail-archive/web/sip/ |
In addition to the charter maintained by the IETF Secretariat, there is additional information about this working group on the Web at: Additional SIP Page
The Session Initiation Protocol (SIP) working group is chartered to
maintain and continue the development of SIP, currently specified as
proposed standard RFC 3261, and its family of extensions.
SIP is a text-based protocol, similar to HTTP and SMTP, for
initiating interactive communication sessions between users.
Such sessions include voice, video, chat, interactive games, and
virtual reality. The main tasks of the group involve bringing SIP
from proposed to draft standard and specifying and developing
proposed extensions that arise out of strong requirements. The SIP
working group will concentrate on the specification of SIP and its
extensions, and will not explore the use of SIP for specific
environments or applications. It will, however respond to general-
purpose requirements for changes to SIP provided by other working
groups, including the SIPPING working group, when those
requirements are within the scope and charter of SIP. The process and
requirements for such extensions are documented in RFC 3427, "Change
Process for the Session Initiation Protocol".
Throughout its work, the group will strive to maintain the basic model
and architecture defined by SIP. In particular:
1. Services and features are provided end-to-end whenever possible.
2. Standards-track extensions and new features must be generally
applicable, and not applicable only to a specific set of session types.
3. Simplicity is key.
4. Reuse of existing Internet protocols and architectures and
integrating
with other Internet applications is crucial.
The primary source of change requirements to be considered by the SIP
Working Group is the SIPPING working group, which
analyzes the requirements for application of SIP to several different
tasks, including the tasks of standards-development organizations
that are developing systems based on SIP and that may require changes
or extensions thereto. Additional requirements are produced by the
other IETF working groups that are using SIP, including the SIMPLE WG
(which is using SIP for messaging and presence) and the XCON working
group (which is using SIP for centralized conferencing).
In addition to extending SIP as required to address these externally-
derived requirements, the deliverables of the group include assuring
capable security and privacy mechanisms within SIP and increasing
the stability of the SIP specification.
Specific deliverables toward these goals include:
1. Mechanisms for secure expression of identity in requests and
responses.
2. Mechanism to securely request services delivery by non-terminal
elements ("end-to-middle").
3. Guidelines for use of existing security mechanisms such as TLS,
IPsec, and certificates.
4. Guidelines for the use of descriptive techniques such as SAML
(Security Association Markup Language) with SIP.
5. Draft standard versions of SIP and critical supporting
specifications.
Other deliverables may be agreed upon as extensions are understood
to be necessary. Prospective deliverables will be discussed
with the Area Director before inclusion on agendas, and new
proposed work must be approved via a charter update.
| Done | Server Features Negotiation submitted to IESG |
| Done | Complete IESG requested fixes to provrel and servfeat |
| Done | Revised proposed standard version of SIP (2543bis) submitted to IESG |
| Done | SIP Events specification to IESG |
| Done | The UPDATE Method submitted for Proposed Standard |
| Done | SIP extensions for media authorization (call-auth) submitted as Informational |
| Done | Preconditions extensions (manyfolks) spec to IESG |
| Done | SIP Privacy specification to IESG |
| Done | SIP Privacy and Security Requirements to IESG |
| Done | The MESSAGE Method submitted for Proposed Standard |
| Done | The Replaces Header submitted for Proposed Standard |
| Done | Refer spec to IESG |
| Done | SIP NAT extension submitted to IESG |
| Done | SIP over SCTP specification and applicability statement |
| Done | Mechanism for Content Indirection in SIP submitted to IESG for Proposed Standard |
| Done | The SIP Referred-By Header submitted to IESG for Proposed Standard |
| Done | Session Timer spec, revised to IESG |
| Done | Caller preferences specification submitted to IESG |
| Done | Submit SIP Identity documents to IESG for Proposed Standard |
| Done | The SIP Join Header submitted to IESG for Proposed Standard |
| Done | Upgrade S/MIME requirement for AES in 3261 to IESG (PS) |
| Done | Replaces header to IESG (PS) |
| Done | Application Interaction to IESG (BCP) |
| Done | Resource Priority signaling mechanism to IESG (PS) |
| Done | Presence Publication to IESG (PS) |
| Done | Guidelines for Authors of SIP extensions submitted as Informational |
| Done | Enhancements for Authenticated Identity Management to IESG (BCP) |
| Done | MIB spec to IESG |
| Done | Request History mechanism to IESG (PS) |
| Done | Mechanism for REFER without implicit SUBSCRIBE to IESG (PS) |
| Done | Mechanism for Target-Dialog to IESG (PS) |
| Done | Mechanism for feature parameters with REFER To IESG (PS) |
| Done | Mechanism for End-to-Middle Requests to IESG (PS) |
| Done | Consent-Based Communications WGLC (PS) |
| Done | Mechanism for connected identity to WGLC (PS) |
| Done | Certificate Management Service for SIP to WGLC (PS) |
| Done | Rejecting Anonymous Requests to WGLC (PS) |
| Done | Rejecting Anonymous Requests to IESG (PS) |
| Done | Mechanism for connected identity to IESG (PS) |
| Done | Addressing an Amplification Vulnerability in Forking Proxies to IESG (PS) |
| Done | Refering to Multiple Resources to IESG as PS |
| Done | Signaling support for ICE to WGLC (PS) |
| Done | Submit Answering/Alerting Modes to the IESG (PS) |
| Done | Mechanism and guidelines for outbound connections to WGLC (PS) |
| Done | Location Conveyance with SIP to WGLC (PS) |
| Done | Mechanism for obtaining globally routable unique URIs (GRUU) to IESG (PS) |
| Done | Corrections to the SIPS Specification to WGLC (PS) |
| Done | Mechanism and guidelines for outbound connections to IESG (PS) |
| Done | Consent-Based Communications to IESG (PS) |
| Done | Certificate Management Service for SIP to IESG (PS) |
| Done | Signaling support for ICE to IESG (PS) |
| Done | Extensions to SIP UA Profile Delivery Change Notification Event Package for XCAP to WGLC (PS) |
| Done | Connection reuse mechanism to IESG (PS) |
| Done | Session Policies to WGLC as PS |
| Done | Extension for use of etags in conditional notification to WGLC |
| Done | Session Policies to IESG as PS |
| Done | Corrections to the SIPS Specification to IESG (PS) |
| Done | New resource priority namespaces for DISA to WGLC (PS) |
| Done | Requirements for media keying to WGLC (Informational) |
| Done | New resource priority namespaces for DISA to IESG (PS) |
| Done | X.509 Certificates for TLS use in SIP to WGLC (Info) |
| Done | X.509 extended key usage for SIP to WGLC (PS) |
| Done | Requirements for media keying to IESG (Informational) |
| Done | Extensions to SIP UA Profile Delivery Change Notification Event Package for XCAP to IESG (PS) |
| Done | Roadmap for SIP to WGLC (Informational) |
| Done | Roadmap for SIP to IESG (Informational) |
| Dec 2007 | Extension for use in etags in conditional notification to IESG (PS) |
| Done | Establishment of secure media sessions using DTLS-SRTP to WGLC (PS) |
| Done | MIME body handling in SIP to WGLC (PS) |
| Done | Establishment of secure media sessions using DTLS-SRTP to IESG (PS) |
| Done | Guidelines for double route recording to WGLC (BCP) |
| Aug 2008 | Guidelines for double route recording to IESG (BCP) |
| Sep 2008 | X.509 Certificates for TLS use in SIP to IESG (PS) |
| Sep 2008 | X.509 extended key usage for SIP to IESG (PS) |
| Done | Termination of early dialog prior to final response to WGLC (PS) |
| Done | Using SAML for SIP to WGLC (Exp) |
| Nov 2008 | Termination of early dialog prior to final response to IESG (PS) |
| Dec 2008 | Location Conveyance with SIP to IESG (PS) |
| Dec 2008 | Using SAML for SIP to IESG (Exp) |
| Dec 2008 | Delivering request-URI and parameters to UAS via proxy to WGLC (PS) |
| Jan 2009 | MIME body handling in SIP to IESG (PS) |
| Feb 2009 | Delivering request-URI and parameters to UAS via proxy to IESG (PS) |
| Done | Mechanisms for UA initiated privacy to WGLC (BCP) |
| Done | INFO package framework to WGLC (PS) |
| Mar 2009 | Example security flows to WGLC (Informational) |
| Mar 2009 | Identify requirements for test matrix to move SIP to Draft Standard |
| Mar 2009 | Revise charter |
| Mar 2009 | Essential corrections to RFC 3261 (1st batch) to IESG (PS) |
| Apr 2009 | Mechanisms for UA initiated privacy to IESG (BCP) |
| Apr 2009 | INFO package framework to IESG (PS) |
| Jul 2009 | Example security flows to IESG (Informational) |