Session Initiation Protocol Core (sipcore)
------------------------------------------

 Charter
 Last Modified: 2010-12-15

 Current Status: Active Working Group

 Chair(s):
     Adam Roach  <adam@nostrum.com>
     Paul Kyzivat  <pkyzivat@alum.mit.edu>

 Real-time Applications and Infrastructure Area Director(s):
     Gonzalo Camarillo  <gonzalo.camarillo@ericsson.com>
     Robert Sparks  <rjsparks@nostrum.com>

 Real-time Applications and Infrastructure Area Advisor:
     Robert Sparks  <rjsparks@nostrum.com>

 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 5727, "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:

   Done         INFO package framework to IESG (PS) 

   Done         Termination of early dialog prior to final response to IESG 
                (PS) 

   Done         Invite Transaction Handling Correction to IESG (PS) 

   Done         Extension for use in etags in conditional notification to IESG 
                (PS) 

   Done         SIP Events throttling mechanism to IESG (PS) 

   Done         Presence Scaling Requirements to IESG as Info 

   Done         Mechanism for indicating support for keep-alives (PS) 

   Done         Example security flows to IESG (Informational) 

   Done         Location Conveyance with SIP to IESG (PS) 

   Jul 2011       Delivering request-URI and parameters to UAS via proxy to IESG 
                (PS) 

   Aug 2011       Error corrections and clarifications to RFC3265 to IESG (PS) 

   Aug 2011       WGLC on requirements for a mechanism to indicate proxy 
                capabilities to both endpoints and other proxies in the path of 
                a REGISTER transaction or a dialog-forming transaction. 


 Internet-Drafts:

Posted Revised         I-D Title   <Filename>
------ ------- --------------------------------------------
May 2009 Jul 2011   <draft-ietf-sipcore-event-rate-control-08.txt>
                Session Initiation Protocol (SIP) Event Notification Extension 
                for Notification Rate Control 

Jun 2009 May 2011   <draft-ietf-sipcore-location-conveyance-08.txt>
                Location Conveyance for the Session Initiation Protocol 

Jul 2009 Jul 2011   <draft-ietf-sipcore-rfc3265bis-03.txt>
                SIP-Specific Event Notification 

Feb 2010 Apr 2011   <draft-ietf-sipcore-rfc4244bis-05.txt>
                An Extension to the Session Initiation Protocol (SIP) for 
                Request History Information 

Jul 2011 Jun 2011   <draft-ietf-sipcore-proxy-feature-reqs-00.txt>
                Requirements for indication of features supported by a SIP 
                proxy 

 Request For Comments:

  RFC   Stat Published     Title
------- -- ----------- ------------------------------------
RFC5839 PS   May 2010    An Extension to Session Initiation Protocol (SIP) Events 
                       for Conditional Event Notification 

RFC6026 PS   Sep 2010    Correct Transaction Handling for 2xx Responses to 
                       Session Initiation Protocol (SIP) INVITE Requests 

RFC6086 PS   Jan 2011    Session Initiation Protocol (SIP) INFO Method and 
                       Package Framework 

RFC6141 PS   Mar 2011    Re-INVITE and Target-Refresh Request Handling in the 
                       Session Initiation Protocol (SIP) 

RFC6216 I    Apr 2011    Example Call Flows Using Session Initiation Protocol 
                       (SIP) Security Mechanisms 

RFC6223 PS   Apr 2011    Indication of Support for Keep-Alive 

RFC6228 PS   May 2011    Session Initiation Protocol (SIP) Response Code for 
                       Indication of Terminated Dialog