The SIP WG has primary responsibility for the future development of
SIP, but SIP-related work occurs in a number of IETF working groups:
- SIP WG
- SIP standardization has moved from MMUSIC to the SIP working
group, with its own mailing list and
such as tasks, schedules and design teams.
(Session Initiation Protocol Project
- "working group is chartered to document the application
of SIP to certain domain tasks and to develop requirements for the
changes or extensions to SIP needed to accomplish those tasks. The
SIPPING working group will concentrate on the frameworks, requirements,
and practices related to SIP and its extensions, and will not specify
changes or extensions to SIP."
The supplemental web
site contains schedules, working group drafts and other
- MMUSIC WG
- For SDP, SAP and related topics.
- Release 5 and later use SIP in its Internet Multimedia Subsystem
(IMS). The current
status list is a good summary of the drafts, while specs/latest contains the
most current drafts. In particular, TS 23.002 (architecture), TS 23.228
(concepts and procedures), 24.228 (call flows) and TS 24.229 (Call
Control Protocol) contain most of the SIP-related material.
- The PINT working group (now concluded) uses a profile of SIP.
- iptel WG
- The Call Processing Language is designed to work with SIP and
control its operation. The Gateway Location Protocol can be used to
introduce proxy servers to SIP.
- impp WG
(Instant Messaging and Presence Protocol)
- SIP has been proposed as a solution, one of several, to the Internet
presence and notification problem.
DTS/TIPHON-03018 - Interface Protocol Requirements Definition;
Implementation of TIPHON architecture using SIP
Uri Baniel maintains a list of SIP-related RFCs
by Henning Schulzrinne