Movatterモバイル変換


[0]ホーム

URL:


Search RFCs

Advanced Search

RFC Editor

RFC 6201

Device Reset Characterization,March 2011

File formats:
icon for text fileicon for PDFicon for HTML
Status:
INFORMATIONAL
Updates:
RFC 1242,RFC 2544
Authors:
R. Asati
C. Pignataro
F. Calabria
C. Olvera
Stream:
IETF
Source:
bmwg (ops)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC6201

Discuss this RFC: Send questions or comments to the mailing listbmwg@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 6201


Abstract

An operational forwarding device may need to be restarted(automatically or manually) for a variety of reasons, an eventcalled a "reset" in this document. Since there may be aninterruption in the forwarding operation during a reset, it isuseful to know how long a device takes to resume the forwardingoperation.

This document specifies a methodology for characterizing reset (andreset time) during benchmarking of forwarding devices and providesclarity and consistency in reset test procedures beyond what isspecified in RFC 2544. Therefore, it updates RFC 2544. This documentalso 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.


For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.




IABIANAIETFIRTFISEISOCIETF Trust
ReportsPrivacy StatementSite MapContact Us

Advanced Search

[8]ページ先頭

©2009-2026 Movatter.jp