H.248 control of AAL2 CID Allocation
draft-tappenden-atm-aal2-package-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Chris Tappenden | ||
| Last updated | 2001-11-19 | ||
| 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 contribution proposes specific procedures that media gateways shall follow for H.248 Allocation of AAL2 CIDs. This proposal covers gateways using non-AAL2 signalling (no Q.2630.x) with a backward SPVC call setup mode. This contribution attempts to build upon existing RFCs and expand upon the expected behavior of Media Gateways when receiving H.248 messaging designed to set-up and tear down AAL2 connections.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)