Device Reset Characterization
RFC 6201, “Device Reset Characterization”, is an Informational document published in March 2011 by R. Asati, C. Pignataro, F. Calabria, C. Olvera. It updates RFC 1242, RFC 2544. The canonical text is published by the RFC Editor.
Abstract
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 6201 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6202 Known Issues and Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP
- RFC 6203 IMAP4 Extension for Fuzzy Search
- RFC 6198 Requirements for the Graceful Shutdown of BGP Sessions
- RFC 6204 Basic Requirements for IPv6 Customer Edge Routers
- RFC 6197 Location-to-Service Translation Service List Boundary Extension
- RFC 6205 Generalized Labels for Lambda-Switch-Capable Label Switching Routers
- RFC 6196 Moving mailserver: URI Scheme to Historic
- RFC 6206 The Trickle Algorithm