Document Action: 'Device Reset Characterization' to Informational RFC (draft-ietf-bmwg-reset-06.txt)
The IESG <iesg-secretary@ietf.org> Fri, 14 January 2011 22:44 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D49423A6BEB; Fri, 14 Jan 2011 14:44:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.508
X-Spam-Level:
X-Spam-Status: No, score=-102.508 tagged_above=-999 required=5 tests=[AWL=0.091, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iSDedUvxNfgU; Fri, 14 Jan 2011 14:44:09 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 620AC3A6BF6; Fri, 14 Jan 2011 14:44:08 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Document Action: 'Device Reset Characterization' to Informational RFC (draft-ietf-bmwg-reset-06.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20110114224408.27691.70444.idtracker@localhost>
Date: Fri, 14 Jan 2011 14:44:08 -0800
Cc: bmwg chair <bmwg-chairs@tools.ietf.org>, Internet Architecture Board <iab@iab.org>, bmwg mailing list <bmwg@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jan 2011 22:44:09 -0000
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 Group. The IESG contact persons are Ron Bonica and Dan Romascanu. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-bmwg-reset/ 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 operation. 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. Personnel Al Morton is document shepherd.