Applicability of MEGACO to Middlebox Control
draft-sct-midcom-megaco-02
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Sanjoy Sen , Cedric Aoun , Tom Taylor | ||
Last updated | 2002-05-13 | ||
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 draft discusses the applicability of the Megaco/H.248 device control protocol [1] as the Middlebox communication protocol. It discusses the architectural similarities between Megaco and Midcom and how Megaco meets most of the key requirements for the Midcom protocol. Modeling the underlying Middlebox resources (such as, filters, policy rules etc) as separate elements from the Megaco entities allows the usage of the protocol as-is, satisfying some of the resource access control requirements. Minimal extensions in the form of new Termination/Package definition (without impacting the base protocol) are sought for Midcom. The Midcom protocol profile and other extensions/packages will be specified in a separate internet draft.
Authors
Sanjoy Sen
Cedric Aoun
Tom Taylor
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)