Skip to main content

Device Reset Characterization

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Rajiv Asati , Carlos Pignataro , Fernando Calabria , Cesar Olvera
Last updated 2010-02-19
Replaced by RFC 6201
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-bmwg-reset
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:


An operational forwarding device may need to be re-started (automatically or manually) for a variety of reasons, an event that we call a "reset" in this document. Since there may be an interruption in the forwarding operation during a reset, it is useful to know how long a device takes to begin forwarding packets again. This document specifies a methodology for characterizing reset during benchmarking of forwarding devices, and provides clarity and consistency in reset test procedures beyond what's specified in RFC2544. It therefore updates RFC2544.


Rajiv Asati
Carlos Pignataro
Fernando Calabria
Cesar Olvera

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