Session Initiation Protocol (sip) --------------------------------- Charter Last Modified: 2009-03-03 Current Status: Active Working Group Chair(s): Dean Willis Keith Drage Real-time Applications and Infrastructure Area Director(s): Robert Sparks Cullen Jennings Real-time Applications and Infrastructure Area Advisor: Cullen Jennings Technical Advisor(s): Dan Romascanu 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) Done Mechanism for connected identity to WGLC (PS) Done Consent-Based Communications WGLC (PS) Done Rejecting Anonymous Requests to WGLC (PS) Done Certificate Management Service for SIP to WGLC (PS) Done Mechanism for connected identity to IESG (PS) Done Refering to Multiple Resources to IESG as PS Done Addressing an Amplification Vulnerability in Forking Proxies to IESG (PS) Done Rejecting Anonymous Requests to IESG (PS) Done Signaling support for ICE to WGLC (PS) Done Location Conveyance with SIP to WGLC (PS) Done Submit Answering/Alerting Modes to the IESG (PS) Done Mechanism and guidelines for outbound connections 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 Consent-Based Communications to IESG (PS) Done Signaling support for ICE to IESG (PS) Done Certificate Management Service for SIP to IESG (PS) Done Mechanism and guidelines for outbound connections to IESG (PS) Done Extensions to SIP UA Profile Delivery Change Notification Event Package for XCAP to WGLC (PS) Done Session Policies to WGLC as PS Done Connection reuse mechanism to IESG (PS) Done Extension for use of etags in conditional notification to WGLC Done New resource priority namespaces for DISA to WGLC (PS) Done Requirements for media keying to WGLC (Informational) Done Corrections to the SIPS Specification to IESG (PS) Done Session Policies to IESG as PS 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) Dec 2007 Extension for use in etags in conditional notification to IESG (PS) Done Roadmap for SIP to WGLC (Informational) Done Extensions to SIP UA Profile Delivery Change Notification Event Package for XCAP to IESG (PS) Done Roadmap for SIP to IESG (Informational) 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) Nov 2008 Termination of early dialog prior to final response to IESG (PS) Done Using SAML for SIP to WGLC (Exp) 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) Internet-Drafts: Posted Revised I-D Title ------ ------- -------------------------------------------- Aug 2003 Mar 2009 Connection Reuse in the Session Initiation Protocol (SIP) Jan 2004 Oct 2007 Obtaining and Using Globally Routable User Agent (UA) URIs (GRUU) in the Session Initiation Protocol (SIP) Jun 2005 Mar 2009 Location Conveyance for the Session Initiation Protocol Jul 2005 Oct 2008 Managing Client Initiated Connections in the Session Initiation Protocol (SIP) May 2006 Nov 2008 Certificate Management Service for The Session Initiation Protocol (SIP) Jun 2006 Mar 2009 SIP SAML Profile and Binding Oct 2006 Nov 2008 A Framework for Session Initiation Protocol (SIP) Session Policies Dec 2006 Nov 2008 The use of the SIPS URI Scheme in the Session Initiation Protocol (SIP) Jan 2007 Jun 2007 Indicating Support for Interactive Connectivity Establishment (ICE) in the Session Initiation Protocol (SIP) May 2007 Mar 2009 An Extension to Session Initiation Protocol (SIP) Events for Conditional Event Notification Jul 2007 Mar 2009 Addressing Record-Route issues in the Session Initiation Protocol (SIP) Aug 2007 Mar 2009 Message Body Handling in the Session Initiation Protocol (SIP) Nov 2007 Apr 2009 Using Extended Key Usage (EKU) for Session Initiation Protocol (SIP) X.509 Certificates Nov 2007 Apr 2009 Domain Certificates in the Session Initiation Protocol (SIP) Nov 2007 Mar 2009 Framework for Establishing an SRTP Security Context using DTLS Nov 2007 Apr 2009 UA-Driven Privacy Mechanism for SIP Dec 2007 Oct 2008 An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Diff Event Package Feb 2008 Nov 2008 Essential correction for IPv6 ABNF and URI comparison in RFC3261 May 2008 Mar 2009 Response Code for Indication of Terminated Dialog Oct 2008 Jan 2009 Session Initiation Protocol (SIP) INFO Method and Package Framework Request For Comments: RFC Stat Published Title ------- -- ----------- ------------------------------------ RFC2976 PS Oct 2000 The SIP INFO Method RFC3204 PS Dec 2001 MIME media types for ISUP and QSIG Objects RFC3261 PS Jul 2002 SIP: Session Initiation Protocol RFC3262 PS Jul 2002 Reliability of Provisional Responses in SIP RFC3263 PS Jul 2002 SIP: Locating SIP Servers RFC3265 PS Jul 2002 SIP-Specific Event Notification RFC3361 PS Aug 2002 DHCP Option for SIP Servers RFC3310 I Sep 2002 Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA) RFC3311 PS Oct 2002 The Session Initiation Protocol UPDATE Method RFC3312 PS Oct 2002 Integration of Resource Management and SIP RFC3420 PS Nov 2002 Internet Media Type message/sipfrag RFC3323 PS Dec 2002 A Privacy Mechanism for the Session Initiation Protocol (SIP) RFC3325 I Dec 2002 Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks RFC3428 PS Dec 2002 Session Initiation Protocol Extension for Instant Messaging RFC3326 PS Dec 2002 The Reason Header Field for the Session Initiation Protocol (SIP) RFC3327 PS Dec 2002 Session Initiation Protocol Extension for Registering Non-Adjacent Contacts RFC3329 PS Jan 2003 Security Mechanism Agreement for the Session Initiation Protocol (SIP) Sessions RFC3313 I Jan 2003 Private Session Initiation Protocol (SIP)Extensions for Media Authorization RFC3486Standard Mar 2003 Compressing the Session Initiation Protocol RFC3515 PS Apr 2003 The Session Initiation Protocol (SIP) Refer Method RFC3319 PS Jul 2003 Dynamic Host Configuration Protocol (DHCPv6)Options for Session Initiation Protocol (SIP) Servers RFC3581 PS Aug 2003 An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing RFC3608Standard Oct 2003 Session Initiation Protocol Extension Header Field for Service Route Discovery During Registration RFC3853Standard Jul 2004 S/MIME AES Requirement for SIP RFC3840Standard Aug 2004 Indicating User Agent Capabilities in the Session Initiation Protocol (SIP) RFC3841Standard Aug 2004 Caller Preferences for the Session Initiation Protocol (SIP) RFC3892Standard Sep 2004 The SIP Referred-By Mechanism RFC3893Standard Sep 2004 SIP Authenticated Identity Body (AIB) Format RFC3891Standard Sep 2004 The Session Inititation Protocol (SIP) 'Replaces' Header RFC3911Standard Nov 2004 The Session Inititation Protocol (SIP) 'Join' Header RFC3903Standard Nov 2004 An Event State Publication Extension to the Session Initiation Protocol (SIP) RFC3969BCP Jan 2005 The Internet Assigned Number Authority (IANA) Universal Resource Identifier (URI) Parameter Registry for the Session Initiation Protocol (SIP) RFC3968BCP Jan 2005 The Internet Assigned Number Authority (IANA) Header Field Parameter Registry for the Session Initiation Protocol (SIP) RFC4032Standard Mar 2005 Update to the Session Initiation Protocol (SIP) Preconditions Framework RFC4028Standard May 2005 Session Timers in the Session Initiation Protocol (SIP) RFC4092Standard Jun 2005 Usage of the Session Description Protocol (SDP) Alternative Network Address Types (ANAT) Semantics in the Session Initiation Protocol (SIP) RFC4168Standard Oct 2005 The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol (SIP) RFC4244Standard Dec 2005 An Extension to the Session Initiation Protocol (SIP) for Request History Information RFC4321 I Jan 2006 Problems identified associated with the Session Initiation Protocol's (SIP) non-INVITE Transaction RFC4320Standard Jan 2006 Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) non-INVITE Transaction RFC4412 PS Feb 2006 Communications Resource Priority for the Session Initiation Protocol (SIP) RFC4488 PS May 2006 Suppression of Session Initiation Protocol (SIP) REFER Method Implicit Subscription RFC4508 PS May 2006 Conveying Feature Tags with Session Initiation Protocol (SIP) REFER Method RFC4483 PS May 2006 A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages RFC4485 I May 2006 Guidelines for Authors of Extensions to the Session Initiation Protocol (SIP) RFC4538 PS Jun 2006 Request Authorization through Dialog Identification in the Session Initiation Protocol (SIP) RFC4474 PS Aug 2006 Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP) RFC4780 PS May 2007 Management Information Base for the Session Initiation Protocol (SIP) RFC4916 PS Jun 2007 Connected Identity in the Session Initiation Protocol (SIP) RFC5079 PS Dec 2007 Rejecting Anonymous Requests in the Session Initiation Protocol (SIP) RFC5366 PS Oct 2008 Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP) RFC5367 PS Oct 2008 Subscriptions to Request-Contained Resource Lists in the Session Initiation Protocol (SIP) RFC5368 PS Oct 2008 Referring to Multiple Resources in the Session Initiation Protocol (SIP) RFC5365 PS Oct 2008 Multiple-Recipient MESSAGE Requests in the Session Initiation Protocol (SIP) RFC5360 PS Oct 2008 A Framework for Consent-based Communications in the Session Initiation Protocol (SIP) RFC5373 PS Nov 2008 Requesting Answering Modes for the Session Initiation Protocol (SIP) RFC5393 PS Dec 2008 Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking Proxies RFC5411 I Feb 2009 A Hitchhiker's Guide to the Session Initiation Protocol (SIP) RFC5478 PS Mar 2009 IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespaces RFC5479 I Apr 2009 Requirements and Analysis of Media Security Management Protocols