Traffic Engineering Extensions for link Latency
draft-manral-ospf-te-delay-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Vishwas Manral | ||
| Last updated | 2011-02-22 | ||
| 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
RFC 3630 [RFC3630] describes extensions to OSPF protocol RFC 2328 [RFC2328] to support intra-area Traffic Engineering (TE). For multiple applications such as High Performance Computing and Electronic Financial markets, response times are critical. This document defines the Traffic Engineering (TE) extensions to RFC 3630 [RFC3630] and and RFC 5329 [RFC5329] for defining a delay metric, which can be used by latency sensistive applications.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)