<?xml version='1.0' encoding='UTF-8'?>

<reference anchor='I-D.asati-bmwg-reset'>
<front>
<title>Device Reset Characterization</title>

<author initials='R' surname='Asati' fullname='Rajiv Asati'>
    <organization />
</author>

<author initials='C' surname='Pignataro' fullname='Carlos Pignataro'>
    <organization />
</author>

<author initials='F' surname='Calabria' fullname='Fernando Calabria'>
    <organization />
</author>

<author initials='C' surname='Olvera' fullname='Cesar Olvera'>
    <organization />
</author>

<date month='February' day='19' year='2010' />

<abstract><t>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.</t></abstract>

</front>

<seriesInfo name='Internet-Draft' value='draft-asati-bmwg-reset-03' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-asati-bmwg-reset-03.txt' />
</reference>

