Requirements for A Telephony Gateway Device Control Protocol
draft-taylor-ipdc-reqts-00

Document Type Expired Internet-Draft (individual)
Author Tom Taylor 
Last updated 1998-09-15
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-taylor-ipdc-reqts-00.txt

Abstract

This document describes the requirements for a protocol to control a device which supports telephone lines or trunks on one side and packet network ports on the other. The primary functions of the device are to make, modify, and break media stream connections between these edge-points, to perform operations on the media streams, and to detect and report specific events associated with those streams or the edge-points. This device may also terminate call signalling which it processes itself and/or passes to the device which controls it. Using the terminology provided by Cuervo et al [1], the device just described is a Media Gateway, and is controlled by a Media Gateway Controller. The requirements for the protocol separate into two major parts: operational and functional. The operational requirements are concerned with reliability and security of control messaging, control session startup and takedown, handling of control session failures, and control system performance. The functional requirements cover connection control, media processing, event notification, and resource status tracking. They may also include signalling backhaul from the Media Gateway to the Media Gateway Controller. The protocol should extend to the control of devices which contain telephony edge-points only (such as digital cross-connects) or packet network ports only (such as transcoders or announcement servers).

Authors

Tom Taylor (tom.taylor.stds@gmail.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)