Skip to main content

Device Reset Characterization
RFC 6201

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'An operational forwarding device may need to be restarted (automatically or manually) for a variety of …
Received changes through RFC Editor sync (changed abstract to 'An operational forwarding device may need to be restarted (automatically or manually) for a variety of reasons, an event called 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 operation.

This document specifies a methodology for characterizing reset (and reset time) during benchmarking of forwarding devices and provides clarity and consistency in reset test procedures beyond what is specified in RFC 2544. Therefore, it updates RFC 2544. This document also defines the benchmarking term "reset time" and, only in this, updates RFC 1242. This document is not an Internet Standards Track specification; it is published for informational purposes.')
2015-10-14
(System) Notify list changed from bmwg-chairs@ietf.org, draft-ietf-bmwg-reset@ietf.org to (None)
2011-03-28
Cindy Morgan State changed to RFC Published from RFC Ed Queue.
2011-03-28
Cindy Morgan [Note]: changed to 'RFC 6201'
2011-03-27
(System) RFC published