Terminology for Benchmarking IGP Convergence
draft-poretsky-igp-convergence-term-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Scott Poretsky | ||
| Last updated | 2003-02-13 | ||
| 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 describes the terminology for benchmarking IGP Route Convergence. The motivation and applicability for this benchmarking is provided in [1]. The methodology to be used for this benchmarking is described in [2]. The methodology and terminology to be used for benchmarking route convergence can be applied to any link-state IGP such as ISIS [3] and OSPF [4]. The data plane is measured to obtain the convergence benchmarking metrics. The purpose of this document is to introduce new terms required to complete execution of the IGP Route Convergence Methodology [2].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)