IETF Proceedings

IETF-92 Proceedings

Introduction | Area, Working Goup & BoF Reports | Plenaries | Training | Internet Research Task Force

Session Initiation Protocol Core (sipcore) (WG)

Minutes | Jabber Logs | Mailing List Archives

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

Chair(s):

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

Assigned Area Director

Ben Campbell

Recordings:

No Recordings Present

Meeting Slides:

No Slides Present

Internet-Drafts:

Locating Session Initiation Protocol (SIP) Servers in a Dual-Stack IP Network (15189 bytes)
A clarification on the use of Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP) Event Notification Framework (6760 bytes)
Clarifications for the use of REFER with RFC6665 (13949 bytes)
Explicit Subscriptions for the REFER Method (33022 bytes)

Request for Comments:

SIP-Specific Event Notification (RFC 6665) (125556 bytes) obsoletes rfc3265 updates RFC3261,RFC4660
Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP) (RFC 6809) (40053 bytes)
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 RFC3261
Session Initiation Protocol (SIP) INFO Method and Package Framework (RFC 6086) (75949 bytes) obsoletes rfc2976
Re-INVITE and Target-Refresh Request Handling in the Session Initiation Protocol (SIP) (RFC 6141) (57517 bytes) updates RFC3261
Example Call Flows Using Session Initiation Protocol (SIP) Security Mechanisms (RFC 6216) (143891 bytes)
Session Initiation Protocol (SIP) Response Code for Indication of Terminated Dialog (RFC 6228) (34311 bytes)
Indication of Support for Keep-Alive (RFC 6223) (41439 bytes)
Session Initiation Protocol (SIP) Event Notification Extension for Notification Rate Control (RFC 6446) (57971 bytes) updates RFC3265
IANA Registry for the Session Initiation Protocol (SIP) "Priority" Header Field (RFC 6878) (4688 bytes) updates RFC3261
The WebSocket Protocol as a Transport for the Session Initiation Protocol (SIP) (RFC 7118) (51248 bytes)
The Management Policy of the Resource Priority Header (RPH) Registry Changed to "IETF Review" (RFC 7134) (3565 bytes) updates RFC4412
Session Initiation Protocol (SIP) History-Info Header Call Flow Examples (RFC 7131) (93039 bytes)
An Extension to the Session Initiation Protocol (SIP) for Request History Information (RFC 7044) (85068 bytes) obsoletes rfc4244
Location Conveyance for the Session Initiation Protocol (RFC 6442) (80795 bytes)

Charter (as of 2009-04-13):

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.