The Session Initiation Protocol Project INvestiGation (SIPPING) 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. Guiding principles include:
1. Describe the requirements of specific tasks.
2. Look for commonalities in tasks that indicate needs for general, reusable
functionality in SIP.
3. Describe the requirements for extensions that provide general, reusable
functionality to SIP.
4. Describe the usage of SIP and its extensions to solve real problems that need
to be solved in a standardized way.
The group will work very close with the Session Initiation Protocol (SIP) working group. The group will also maintain open dialogues with the IPTelephony (iptel) working group, whose Call Processing Language (CPL) relates to many features of SIP, will continue to consider the requirements and specifications previously established by the PSTN and Internet Internetworking (PINT) working group, and will consider input from the Distributed Call Signaling (DCS) Group of the PacketCable Consortium for distributed telephony services and from 3GPP, 3GPP2, and MWIF for third-generation wireless network requirements.
The specific deliverables of the group are:
1. sipt: Requirements and Practices for interaction with
telephony systems (SIP-T, Telephony Call Flows).
2. hearing: Requirements and Practices for providing support for hearing
impaired users.
3. H.323: Requirements and Practices for interaction with H.323 systems.
4. 3g: Requirements and Practices for interaction with third-generation wireless
systems.
5. natfriend: Requirements and Practices for making SIP a NAT-friendly
protocol..
6. regspec: Requirements, Practices and Registration Specifications for
interworking with other descriptive specifications, such as MIME, DNS, DHCP,
ENUM, etc..
7. general: Discussion and Guidelines on the general usage of SIP.
8. multiparty: Requirements and Practices for multiparty conferencing.
9. fax: Requirements, Practices, and Registrations Specifications for using
SIP with FAX.
10. mwi: Requirements and Practices for Message Waiting Indicator.
11. media: Requirements and Practices for usage of SIP in media servers,
messaging
servers, conferencing servers, and similar applications.
12. regpay: Practices for Registration Payload.
13. callcontrol: Requirements for Call Control.
Other deliverables may be agreed upon during the working process. New deliverables must be approved by the Transport Area Directors before inclusion on the agenda.
Goals and Milestones:
01Mar01 Specification on MIME for ISUP and
Q.SIG to IESG
01Apr01 Specification on SIP-DHCP to IESG
01Apr01 Specification on SIP-SRV to IESG
15Apr01 Informational on ISUP-SIP Body Mapping to IESG
15Apr01 Informational on ISUP-SIP header Mapping to IESG
15May01 Informational on Call Control Framework to IESG.
22May01 Informational on Call Flows to IESG
01Jun01 Informational on T.38 Requirements and Usage to
IESG.
01Jun01 Informational on SIP-H.323 Interworking
Requirements to IESG.
15Jun01 Informational on SIP-T Framework to IESG
01Jul01 Informational on NAT-friendliness to IESG
01Sep01 Informational on Usage of Registration Payload to IESG
15Sep01 Informational on Security and Privacy Requirements to
IESG
15Dec01 Report on future milestones and/or recharter to IESG