IETF 82 Proceedings

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

Session Initiation Protocol Core (sipcore) (WG)

Minutes  | Audio Archives  |  Jabber Logs  |  Mailing List Archives

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

Chair(s):

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

* The Real-time Applications and Infrastructure Area Directors were seated during the IETF 65.

Real-time Applications and Infrastructure Area Advisor:

Meeting Slides

Internet-Drafts:

Request for Comments:

Charter (as of 2011-12-09)

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.