Routing of Multimedia Connections Across TDM-, ATM-, and IP-Based Networks
draft-ash-itu-sg2-qos-routing-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Gerald Ash | ||
| Last updated | 1999-10-27 | ||
| 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 presents the ongoing work in ITU-T SG2 Question 2/2 on Recommendation E.351 'Routing of Multimedia Connections Across TDM-, ATM-, and IP-based Networks.' There are many network operators who have implemented multiple networks using different network-layer (layer-3) routing protocols, which include TDM-, ATM-, and/or IP-based technology. Rapid growth of multimedia IP-based services has led in turn to ATM and IP technology being implemented and/or planned for PSTNs. Established routing methods are recommended for application across network types (summarized in Table 1 of the Recommendation), and include the following: a) E.164/NSAP based number translation/routing, b) automatic generation of routing tables based on network topology and status, c) automatic update and synchronization of topology databases, d) dynamic route selection, and e)QoS resource management. Signaling and information-exchange requirements needed to support these routing methods are recommended, and include the connectivity management and routing policy parameters summarized in Table 4 of the Recommendation.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)