Motivation for Benchmarking BFD Protocol Implementations
draft-salahuddin-bmwg-bfd-motivation-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Esa Salahuddin , Jay Karthik | ||
| Last updated | 2007-02-28 | ||
| 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 document describes the motivation for benchmarking the Bidirectional Forwarding Detection (BFD) protocol. The BFD protocol is a relatively new protocol intended to detect failures in the bidirectional path between two network elements, with potentially very low latency [BFD, BFD-GEN]. The BFD protocol is being implemented by several vendors and is being deployed extensively by the service providers. Hence, it is imperative that common understanding is established for performance and conformance benchmarks as well as interoperability. This draft seeks to generate interest on this topic in the working group. If there is sufficient interest on this topic, drafts that address the Methodology and Terminology for the BFD protocol could be proposed; before BMWG could make this an official working group item.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)