IPDC Base Protocol
draft-taylor-ipdc-00

Document Type Expired Internet-Draft (individual)
Authors Allan Rubens  , Pat Calhoun  , Tom Taylor 
Last updated 1998-08-03
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-00.txt

Abstract

The protocol described in this document provides the basis for 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. According to the framework provided by Cuervo et al [1], the IPDC protocol suite operates between the Media Gateway Controller and the Media Gateway. In terms of previous contributions to the experts of Questions 13-14/16, the corresponding entities are the Call Control and Media Control portions of the H.323 Gateway. The operation of IPDC in the service of H.323 is clarified in a companion contribution entitled 'IPDC Architectural Framework' [3].

Authors

Allan Rubens (acr@merit.edu)
Pat Calhoun (pcalhoun@cisco.com)
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.)