A SPEECHSC protocol for Media Resource Control
draft-shanmugham-speechsc-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Saravanan Shanmugham | ||
| Last updated | 2003-05-22 | ||
| 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
This document describes a proposal for the SPEECHSC protocol and aims to meet the requirements specified in the SPEECHSC working group requirements document. It is based on the Media Resource Control Protocol (MRCP) developed jointly by Cisco Systems, Inc., Nuance Communications, and Speechworks Inc. The SPEECHSC protocol will control media service resources like speech synthesizers, recognizers, signal generators, signal detectors, fax servers etc. over a network. This protocol depends on a session management protocol such as the Session Initiation Protocol (SIP) to establish a separate SPEECHSC control session between the client and the media server. It also depends on SIP to establish the media pipe and associated parameters between the media source or sink and the media server. Once this is done, the SPEECHSC protocol exchange can happen over the control session established above allowing the client to command and control the media processing resources that may exist on the media server.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)