Requirements for Mid Call Communication in the SIP
draft-hwang-sipping-midcall-reqs-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jinkyung Hwang | ||
| Last updated | 2005-01-20 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
In its current form, Session Initiation Protocol (SIP) allows session invitations, instant messages, and other requests to be delivered from one party to another. However it doesnot explicitly permit midcall events such as hook/flash from the user to be passed on to the network application server. Without such ability, it is not clear how SIP can be used to provide certain network controlled services. This document identifies a set of requirements for extensions to SIP to provide a MidCall-based communications framework.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)