IPDC Device Management Protocol
draft-bell-ipdc-signaling-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Bob Bell , Scott Pickett , Alan Mikhak | ||
Last updated | 1998-08-06 | ||
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
The protocol described in this document is a member of the IP Device Control (IPDC) family of protocols. The IPDC protocols are proposed as a protocol suite, components of which can be used individually or together to perform connection control, media control, and signaling transport for environments where the service control logic is separated from the network access server. Please see the references section for other IPDC documents. The protocol specification presented here is intended for use between a media gateway controller and a media gateway. The media gateway may be capable of acting as a voice over IP gateway, voice over ATM gateway, dialup modem media gateway, circuit switch, or cross- connect. Using the IP Device Signaling Transport protocol presented here, the media gateway can receive a signaling from a circuit switched network and deliver the signaling to a media gateway controller on an intervening IP network. The media gateway controller can also send signaling to a media gateway for delivery on a circuit switched network.
Authors
Bob Bell
Scott Pickett
Alan Mikhak
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)