Session Initiation Protocol (sip)

In addition to this official charter maintained by the IETF Secretariat, there is additional information about this working group on the Web at:

Additional SIP Page

Last Modified: 2007-02-28

Additional information is available at tools.ietf.org/wg/sip

Chair(s):

Dean Willis <dean.willis@softarmor.com>

Keith Drage <drage@alcatel-lucent.com>

Real-time Applications and Infrastructure Area Director(s):

Jon Peterson <jon.peterson@neustar.biz>

Cullen Jennings <fluffy@cisco.com>

Real-time Applications and Infrastructure Area Advisor:

Cullen Jennings <fluffy@cisco.com>

Technical Advisor(s):

Dan Romascanu <dromasca@avaya.com>

Mailing Lists:

General Discussion: sip@ietf.org
To Subscribe: sip-request@ietf.org
In Body: subscribe
Archive: http://www.ietf.org/mail-archive/web/sip/index.html

Description of Working Group:

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.

Goals and Milestones:

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		Replaces header to IESG (PS)
Done		Upgrade S/MIME requirement for AES in 3261 to IESG (PS)
Done		Application Interaction to IESG (BCP)
Done		Presence Publication to IESG (PS)
Done		Resource Priority signaling mechanism 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 obtaining globally routable unique URIs (GRUU) to IESG (PS)
Done		Connection reuse mechanism 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)
Aug 2006		Diagnostic Responses for SIP Errors to WGLC (PS)
Aug 2006		Submit Answering/Alerting Modes to the IESG (PS)
Aug 2006		Mechanism and guidelines for outbound connections to WGLC (PS)
Done		Mechanism for connected identity to WGLC (PS)
Done		Consent-Based Communications WGLC (PS)
Sep 2006		Mechanism for obtaining globally routable unique URIs (GRUU) to IESG (PS)
Sep 2006		Mechanism and guidelines for outbound connections to IESG (PS)
Sep 2006		Location Conveyance with SIP to WGLC (PS)
Sep 2006		Example security flows to WGLC (Informational)
Done		Rejecting Anonymous Requests to WGLC (PS)
Done		Certificate Management Service for SIP to WGLC (PS)
Oct 2006		Consent-Based Communications to IESG (PS)
Oct 2006		Diagnostic Responses for SIP Errors to IESG (PS)
Oct 2006		Rejecting Anonymous Requests to IESG (PS)
Oct 2006		Mechanism for connected identity to IESG (PS)
Oct 2006		Addressing an Amplification Vulnerability in Forking Proxies to IESG (PS)
Oct 2006		Extensions to SIP UA Profile Delivery Change Notification Event Package for XCAP to WGLC (PS)
Oct 2006		Refering to Multiple Resources to IESG as PS
Nov 2006		Certificate Management Service for SIP to IESG (PS)
Dec 2006		Extensions to SIP UA Profile Delivery Change Notification Event Package for XCAP to IESG (PS)
Dec 2006		Location Conveyance with SIP to IESG (PS)
Dec 2006		Example security flows to IESG (Informational)
Dec 2006		Roadmap for SIP to WGLC (Informational)
Dec 2006		Signaling support for ICE to WGLC (PS)
Jan 2007		Session Policies to WGLC as PS
Jan 2007		Signaling support for ICE to IESG (PS)
Mar 2007		Session Policies to IESG as PS
Mar 2007		Roadmap for SIP to IESG (Informational)
Mar 2007		Guidelines for use of SIP security to WGLC (Informational)
Apr 2007		Connection reuse mechanism to IESG (PS)
Jun 2007		Guidelines for use of SIP security to IESG (Informational)
Jun 2007		Identify requirements for test matrix to move SIP to Draft Standard
Jun 2007		Revise charter
Sep 2007		Extension for use of etags in conditional notification to WGLC
Sep 2007		Using SAML for SIP to WGLC (PS)
Dec 2007		Using SAML for SIP to IESG (PS)
Dec 2007		Extension for use in etags in conditional notification to IESG (PS)
Dec 2007		Delivering request-URI and parameters to UAS via proxy to WGLC
Feb 2008		Delivering request-URI and parameters to UAS via proxy to IESG (PS)

Internet-Drafts:

Request For Comments:

IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.

Return to working group directory.

Return to IETF home page.