Quality of Service using Traffic Engineering over MPLS: An Analysis
draft-bhani-mpls-te-anal-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Professor Raj Jain , Praveen Bhaniramka , Wei Sun | ||
| Last updated | 1999-04-02 | ||
| 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
We compare the service received by TCP and UDP flows when they share either a link or an MPLS traffic trunk. Since traffic trunks allow non shortest path links also to be used, the total network throughput goes up with proper traffic engineering. If UDP and TCP flows are mixed in a trunk, TCP flows receive reduced service as the UDP flows increase their rates. Also, we found that in order to benefit from traffic engineering, MPLS trunks should be implemented end-to-end (first router to last router). If some part of the network is MPLS-unaware, the benefits are reduced or eliminated.
Authors
Professor Raj Jain
Praveen Bhaniramka
Wei Sun
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)