Skip to main content

Methodology for benchmarking fast failover time with local protection
draft-vapiwala-bmwg-frr-failover-meth-00

Document Type Expired Internet-Draft (individual)
Expired & archived
Author Samir Vapiwala
Last updated 2005-12-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 draft provides the methodology for benchmarking the failover time of local protection (aka Fast Reroute). The failover to a backup tunnel could happen at the headend of the primary tunnel or a midpoint and the backup could offer link or node protection. It becomes vital to benchmark the failover time for all the cases and combinations. The failover time could also greatly differ based on the design and implementation and by factors like the number of prefixes carried by the tunnel, the number of primary tunnels affected by the event that caused the failover, number of primary tunnels the backup protects and type of failure etc. All the required benchmarking criteria and benchmarking topology required for measuring failover time of local protection is described Conventions used in this document

Authors

Samir Vapiwala

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)