Session Initiation Protocol Core (sipcore)

Last Modified: 2010-12-15

Additional information is available at tools.ietf.org/wg/sipcore

Chair(s):

Real-time Applications and Infrastructure Area Director(s):

Real-time Applications and Infrastructure Area Advisor:

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
Oct 2010  Mechanism for indicating support for keep-alives (PS)
Dec 2010  Example security flows to IESG (Informational)
Jan 2011  Location Conveyance with SIP to IESG (PS)
May 2011  Delivering request-URI and parameters to UAS via proxy to IESG (PS)
Jun 2011  Error corrections and clarifications to RFC3265 to IESG (PS)

Internet-Drafts:

Session Initiation Protocol (SIP) Response Code for Indication of Terminated Dialog (38099 bytes)
Indication of support for keep-alive (44530 bytes)
Example call flows using Session Initiation Protocol (SIP) security mechanisms (148509 bytes)
Session Initiation Protocol (SIP) Event Notification Extension for Notification Rate Control (59402 bytes)
Location Conveyance for the Session Initiation Protocol (75369 bytes)
Re-INVITE and Target-refresh Request Handling in the Session Initiation Protocol (SIP) (57762 bytes)
An Extension to the Session Initiation Protocol (SIP) for Request History Information (104669 bytes)

Request For Comments:

An Extension to Session Initiation Protocol (SIP) Events for Conditional Event Notification (RFC 5839) (52999 bytes)
Correct Transaction Handling for 2xx Responses to Session Initiation Protocol (SIP) INVITE Requests (RFC 6026) (44035 bytes) updates RFC 3261
Session Initiation Protocol (SIP) INFO Method and Package Framework (RFC 6086) (75949 bytes) obsoletes RFC 2976