Skip to main content

Device Reset Characterization

Approval announcement
Draft of message to be sent after approval:


From: The IESG <>
To: IETF-Announce <>
Cc: Internet Architecture Board <>,
    RFC Editor <>,
    bmwg mailing list <>,
    bmwg chair <>
Subject: Document Action: 'Device Reset Characterization' to Informational RFC (draft-ietf-bmwg-reset-06.txt)

The IESG has approved the following document:
- 'Device Reset Characterization'
  (draft-ietf-bmwg-reset-06.txt) as an Informational RFC

This document is the product of the Benchmarking Methodology Working

The IESG contact persons are Ron Bonica and Dan Romascanu.

A URL of this Internet Draft is:

Ballot Text

Technical Summary
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 resume the forwarding

This document specifies a methodology for characterizing reset (and
recovery time) during benchmarking of forwarding devices, and
provides clarity and consistency in reset test procedures beyond
what's specified in RFC2544. It therefore updates RFC2544.

Working Group Summary
During the development of MPLS Forwarding Benchmarks as an add-on to our
fundamental forwarding plane memo, RFC 2544, the additional complexities
of RESET testing with current network devices became an issue.
The WG moved quickly to resolve the concerns with a new set of methods,
and this memo is the result. Consensus was achieved after issues were
resolved in list discussions.

Document Quality
Since this is an easily understood topic, many folks read this memo,
simply nodded and moved-on. Resets in hardware, in control software, and
interruption of power supply are addressed in this new methodology.


Al Morton is document shepherd.

RFC Editor Note