Session Initiation Protocol Core (sipcore) ------------------------------------------ Charter Last Modified: 2010-04-16 Current Status: Active Working Group Chair(s): Adam Roach Paul Kyzivat Real-time Applications and Infrastructure Area Director(s): Gonzalo Camarillo Robert Sparks Real-time Applications and Infrastructure Area Advisor: Robert Sparks Mailing Lists: General Discussion:sipcore@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/sipcore Archive: http://www.ietf.org/mail-archive/web/sipcore/ Description of Working Group: The Session Initiation Protocol Core (SIPCore) working group is chartered to maintain and continue the development of the core SIP specifications, currently defined as proposed standard RFCs 3261, 3262, 3263, 3264, and 3265. The SIPCore working group will concentrate on specifications that update or replace the core SIP specifications. In this context, "update" means replacing or modifying protocol elements in the above listed RFCs in ways that would affect most or all implementations of those RFCs alone. Extensions to SIP that add new functionality that would not be required of all implementations will be done outside of this WG. The process and requirements for such extensions are documented in RFC 3427bis, "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. Reuse of existing Internet protocols and architectures and integrating with other Internet applications is crucial. The primary source of change requirements will be a) interoperability problems that stem from ambiguous, or under-defined specification, and b) requirements from other working groups in the RAI Area. Although in general the WG will not work on extensions to SIP, it may take on some previous work items from the SIP working group to allow for a smooth transition. The adoption of new items requires explicit agreement from the AD or rechartering. Goals and Milestones: Jul 2009 Delivering request-URI and parameters to UAS via proxy to IESG (PS) Jul 2009 INFO package framework to IESG (PS) Aug 2009 Termination of early dialog prior to final response to IESG (PS) Aug 2009 Location Conveyance with SIP to IESG (PS) Oct 2009 Example security flows to IESG (Informational) Oct 2009 Invite Transaction Handling Correction to IESG (PS) Oct 2009 Extension for use in etags in conditional notification toIESG (PS) Dec 2009 SIP Events throttling mechanism to IESG (PS) Dec 2009 Mechanism for indicating support for keep-alives (PS) Dec 2009 Error corrections and clarifications to RFC3265 to IESG (PS) Jan 2010 Presence Scaling Requirements to IESG as Info Internet-Drafts: Posted Revised I-D Title ------ ------- -------------------------------------------- Apr 2009 Sep 2009 Scaling Requirements for Presence in SIP/SIMPLE Apr 2009 Dec 2009 Response Code for Indication of Terminated Dialog May 2009 May 2010 Indication of support for keep-alive May 2009 Jun 2010 Example call flows using Session Initiation Protocol (SIP) security mechanisms May 2009 Feb 2010 Session Initiation Protocol (SIP) Event Notification Extension for Notification Rate Control Jun 2009 Feb 2010 Location Conveyance for the Session Initiation Protocol Jul 2009 May 2010 Session Initiation Protocol (SIP) INFO Method and Package Framework Jul 2009 Feb 2010 SIP-Specific Event Notification Sep 2009 Mar 2010 Correct transaction handling for 2xx responses to Session Initiation Protocol (SIP) INVITE requests Dec 2009 May 2010 Re-INVITE and Target-refresh Request Handling in the Session Initiation Protocol (SIP) Feb 2010 Feb 2010 An Extension to the Session Initiation Protocol (SIP) for Request History Information Request For Comments: RFC Stat Published Title ------- -- ----------- ------------------------------------ RFC5839 PS May 2010 An Extension to Session Initiation Protocol (SIP) Events for Conditional Event Notification