2.5.12 Session Initiation Protocol (sip)

NOTE: This charter is a snapshot of the 68th IETF Meeting in Prague, Czech Republic. It may now be out-of-date.
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

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>

* The Real-time Applications and Infrastructure Area Directors were seated during the IETF 65.

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:

  • draft-ietf-sip-mib-12.txt
  • draft-ietf-sip-connect-reuse-07.txt
  • draft-ietf-sip-gruu-12.txt
  • draft-ietf-sip-location-conveyance-07.txt
  • draft-ietf-sip-outbound-08.txt
  • draft-ietf-sip-e2m-sec-05.txt
  • draft-ietf-sip-answermode-02.txt
  • draft-ietf-sip-acr-code-04.txt
  • draft-ietf-sip-fork-loop-fix-04.txt
  • draft-ietf-sip-connected-identity-05.txt
  • draft-ietf-sip-certs-03.txt
  • draft-ietf-sip-saml-01.txt
  • draft-ietf-sip-hitchhikers-guide-02.txt
  • draft-ietf-sip-uri-list-conferencing-01.txt
  • draft-ietf-sip-multiple-refer-01.txt
  • draft-ietf-sip-uri-list-message-01.txt
  • draft-ietf-sip-uri-list-subscribe-01.txt
  • draft-ietf-sip-consent-framework-01.txt
  • draft-ietf-sip-xcap-config-00.txt
  • draft-ietf-sip-session-policy-framework-01.txt
  • draft-ietf-sip-sips-02.txt
  • draft-ietf-sip-ice-option-tag-01.txt

    Request For Comments:

    RFCStatusTitle
    RFC2976 PS The SIP INFO Method
    RFC3204 PS MIME media types for ISUP and QSIG Objects
    RFC3261 PS SIP: Session Initiation Protocol
    RFC3262 PS Reliability of Provisional Responses in SIP
    RFC3263 PS SIP: Locating SIP Servers
    RFC3265 PS SIP-Specific Event Notification
    RFC3310 I Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA)
    RFC3311 PS The Session Initiation Protocol UPDATE Method
    RFC3312 PS Integration of Resource Management and SIP
    RFC3313 I Private Session Initiation Protocol (SIP)Extensions for Media Authorization
    RFC3319 PS Dynamic Host Configuration Protocol (DHCPv6)Options for Session Initiation Protocol (SIP) Servers
    RFC3323 PS A Privacy Mechanism for the Session Initiation Protocol (SIP)
    RFC3325 I Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks
    RFC3326 PS The Reason Header Field for the Session Initiation Protocol (SIP)
    RFC3327 PS Session Initiation Protocol Extension for Registering Non-Adjacent Contacts
    RFC3329 PS Security Mechanism Agreement for the Session Initiation Protocol (SIP) Sessions
    RFC3361 PS DHCP Option for SIP Servers
    RFC3420 PS Internet Media Type message/sipfrag
    RFC3428 PS Session Initiation Protocol Extension for Instant Messaging
    RFC3486 Standard Compressing the Session Initiation Protocol
    RFC3515 PS The Session Initiation Protocol (SIP) Refer Method
    RFC3581 PS An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing
    RFC3608 Standard Session Initiation Protocol Extension Header Field for Service Route Discovery During Registration
    RFC3840 Standard Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)
    RFC3841 Standard Caller Preferences for the Session Initiation Protocol (SIP)
    RFC3853 Standard S/MIME AES Requirement for SIP
    RFC3891 Standard The Session Inititation Protocol (SIP) 'Replaces' Header
    RFC3892 Standard The SIP Referred-By Mechanism
    RFC3893 Standard SIP Authenticated Identity Body (AIB) Format
    RFC3903 Standard An Event State Publication Extension to the Session Initiation Protocol (SIP)
    RFC3911 Standard The Session Inititation Protocol (SIP) 'Join' Header
    RFC3968 BCP The Internet Assigned Number Authority (IANA) Header Field Parameter Registry for the Session Initiation Protocol (SIP)
    RFC3969 BCP The Internet Assigned Number Authority (IANA) Universal Resource Identifier (URI) Parameter Registry for the Session Initiation Protocol (SIP)
    RFC4028 Standard Session Timers in the Session Initiation Protocol (SIP)
    RFC4032 Standard Update to the Session Initiation Protocol (SIP) Preconditions Framework
    RFC4092 Standard Usage of the Session Description Protocol (SDP) Alternative Network Address Types (ANAT) Semantics in the Session Initiation Protocol (SIP)
    RFC4168 Standard The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol (SIP)
    RFC4244 Standard An Extension to the Session Initiation Protocol (SIP) for Request History Information
    RFC4320 Standard Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) non-INVITE Transaction
    RFC4321 I Problems identified associated with the Session Initiation Protocol's (SIP) non-INVITE Transaction
    RFC4412 PS Communications Resource Priority for the Session Initiation Protocol (SIP)
    RFC4474 PS Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP)
    RFC4483 PS A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages
    RFC4485 I Guidelines for Authors of Extensions to the Session Initiation Protocol (SIP)
    RFC4488 PS Suppression of Session Initiation Protocol (SIP) REFER Method Implicit Subscription
    RFC4508 PS Conveying Feature Tags with Session Initiation Protocol (SIP) REFER Method
    RFC4538 PS Request Authorization through Dialog Identification in the Session Initiation Protocol (SIP)

    Meeting Minutes


    Slides

    Agenda
    Status of the SIP working group as of IETF 68
    ICE Option Tag
    GRUU Again for the Last Time, Really
    Essential Corrections Process
    Clarifications of SIPS:
    Outbound
    URI Discovery with DNS SD
    Controlling Fragmentation in Client-Initiated Requests
    Privacy Clarified
    Fixing Record Route
    Domain Certificates