Accomplishing Diffserv TE needs with Current Specifications
draft-boyle-tewg-ds-nop-00
| Document | Type |
Expired Internet-Draft
(tewg WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Jim Boyle | ||
| Last updated | 2001-07-05 | ||
| 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 | |
| Consensus boilerplate | Unknown | ||
| 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
The emerging requirements for differentiated service control in MPLS based traffic engineered networks [DSTE-REQ] can be met by existing specifications. Current implementations could be adapted with a relaxed perception of semantics on the syntax outlined in current specifications [OSPF-TE][ISIS-TE][RSVP-TE]. This would provide for a solution that fulfills the scenarios and functionality requirements called for in DSTE-REQ.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)