Unifying MEGACO/H.GCP Structures and Encoding
draft-rosen-megaco-structures-and-encoding-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Joerg Ott , Paul Sijben , Brian Rosen | ||
Last updated | 1999-07-01 | ||
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 MEGACO/H.GCP draft protocol has several structures that are not com- pletely defined, viz, how properties are described and grouped, the tem- plate concept, the package concept, etc. There is also an extended debate on the encoding of the protocol, and particularly, the encoding of the command parameters. This contribution proposes a unified approach to all of these issues. This Internet Draft was rushed to meet the Oslo deadline. As such, it was not thoroughly reviewed, especially to see that this ID conformed to its referenced fundamental ideas on capabilities.
Authors
Joerg Ott
Paul Sijben
Brian Rosen
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)