Traffic Engineering & QoS Methods for IP-, ATM-, & Based Multiservice Networks
draft-ietf-tewg-qos-routing-04
Document | Type |
Expired Internet-Draft
(tewg WG)
Expired & archived
|
|
---|---|---|---|
Author | Gerald Ash | ||
Last updated | 2015-10-14 (Latest revision 2001-10-15) | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired (IESG: Dead) | |
Action Holders |
(None)
|
||
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | Bert Wijnen | ||
IESG note | |||
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 is an informational document submitted in response to a request from the IETF Traffic Engineering Working Group (TEWG) for service provider uses, requirements, and desires for traffic engineering best current practices. As such, the work sets a direction for routing and traffic performance management in networks based on traffic engineering (TE) and QoS best current practices and operational experience, such as used in the AT&T dynamic routing/class-of-service network.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)