Session Initiation Protocol (sip) --------------------------------- Charter Last Modified: 2006-03-24 Current Status: Active Working Group Chair(s): Dean Willis Keith Drage Real-time Applications and Infrastructure Area Director(s): Jon Peterson 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) Oct 2005 Mechanism for obtaining globally routable unique URIs (GRUU) to IESG (PS) Done Mechanism for REFER without implicit SUBSCRIBE to IESG (PS) Nov 2005 Connection reuse mechanism to IESG (PS) Done Mechanism for Target-Dialog to IESG (PS) Jan 2006 Submit Answering/Alerting Modes to the IESG for Proposed Standard Done Mechanism for feature parameters with REFER To IESG (PS) Feb 2006 Mechanism and guidelines for outbound connections to IESG (PS) Feb 2006 Guidelines for Using Certificates with SIP to IESG (BCP) Mar 2006 Location Conveyance with SIP to IESG (PS) Apr 2006 Mechanism for End-to-Middle Requests to IESG (PS) Apr 2006 Mechanism for Response Identity to IESG (PS) Jul 2006 Using SAML for SIP (PS) Jul 2006 Revise Charter, including developing a task for a roadmap that will identify the Internet-Drafts: Posted Revised I-D Title ------ ------- -------------------------------------------- Mar 2000 Jun 2006 Management Information Base for the Session Initiation Protocol (SIP) Oct 2002 Oct 2005 Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP) Aug 2003 Aug 2006 Connection Reuse in the Session Initiation Protocol (SIP) Jan 2004 Aug 2006 Obtaining and Using Globally Routable User Agent (UA) URIs (GRUU) in the Session Initiation Protocol (SIP) Jun 2005 Jun 2006 Session Initiation Protocol Location Conveyance Jul 2005 Jun 2006 End-to-middle Security in the Session Initiation Protocol (SIP) Jul 2005 Jun 2006 Managing Client Initiated Connections in the Session Initiation Protocol (SIP) Dec 2005 May 2006 Requesting Answering Modes for the Session Initiation Protocol (SIP) Jan 2006 Aug 2006 Rejecting Anonymous Requests in the Session Initiation Protocol (SIP) Feb 2006 Jun 2006 Diagnostic Responses for Session Initiation Protocol Hop Limit Errors Mar 2006 Jun 2006 Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking Proxies Apr 2006 Aug 2006 Connected Identity in the Session Initiation Protocol (SIP) May 2006 Jun 2006 Example call flows using Session Initiation Protocol (SIP) security mechanisms May 2006 Jun 2006 Certificate Management Service for The Session Initiation Protocol (SIP) Jun 2006 Jun 2006 SIP SAML Profile and Binding Jun 2006 Jun 2006 A Hitchhikers Guide to the Session Initiation Protocol (SIP) 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 RFC3325 I Dec 2002 Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks RFC3323 PS Dec 2002 A Privacy Mechanism for the Session Initiation Protocol (SIP) 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 RFC3841Standard Aug 2004 Caller Preferences for the Session Initiation Protocol (SIP) RFC3840Standard Aug 2004 Indicating User Agent Capabilities in the Session Initiation Protocol (SIP) RFC3891Standard Sep 2004 The Session Inititation Protocol (SIP) 'Replaces' Header RFC3892Standard Sep 2004 The SIP Referred-By Mechanism RFC3893Standard Sep 2004 SIP Authenticated Identity Body (AIB) Format 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 RFC4320Standard Jan 2006 Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) non-INVITE Transaction RFC4321 I Jan 2006 Problems identified associated 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)