Media Gateway AAL2 Bearer-Path Establishment
draft-barr-megaco-aal2bearer-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | David Barr | ||
| Last updated | 2002-06-24 | ||
| 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 document proposes specific procedures that Media Gateways (MGs) shall follow for AAL2 bearer-path establishment under the control of H.248 (Megaco) capable Media Gateway Controllers (MGCs). The procedures cover MGs which use provisioned VCCs and backward call setup mode dynamic SVCs, and which do not use AAL2 signalling (i.e. no Q.2630.x). Although this document refers to the use of the H.248 (Megaco) gateway control protocol, many of the concepts and procedures are not specific to this protocol.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)