Re: [bmwg] WGLC: draft-ietf-bmwg-protection term-06 and meth-05
Vrushabhendra Gurudevappa <vgurudevappa@camiant.com> Tue, 21 July 2009 17:16 UTC
Return-Path: <vgurudevappa@camiant.com>
X-Original-To: bmwg@core3.amsl.com
Delivered-To: bmwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 24F113A68A6 for <bmwg@core3.amsl.com>; Tue, 21 Jul 2009 10:16:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.393
X-Spam-Level:
X-Spam-Status: No, score=-1.393 tagged_above=-999 required=5 tests=[AWL=1.205, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 SUuFjiBx-Jf9 for <bmwg@core3.amsl.com>; Tue, 21 Jul 2009 10:16:51 -0700 (PDT)
Received: from mail.camiant.com (mail.camiant.com [209.48.60.131]) by core3.amsl.com (Postfix) with ESMTP id 3B5923A6E8D for <bmwg@ietf.org>; Tue, 21 Jul 2009 10:16:49 -0700 (PDT)
Received: from mail.corporate.camiant.local ([10.0.0.63]) by mail.corporate.camiant.local ([10.0.0.63]) with mapi; Tue, 21 Jul 2009 13:16:48 -0400
From: Vrushabhendra Gurudevappa <vgurudevappa@camiant.com>
To: "bmwg@ietf.org" <bmwg@ietf.org>
Date: Tue, 21 Jul 2009 13:16:47 -0400
Thread-Topic: Re:[bmwg] WGLC: draft-ietf-bmwg-protection term-06 and meth-05
Thread-Index: AcoKJwcMMXSh5T5wSAW2AI0Ci+Dk+Q==
Message-ID: <2BAB63F974AB4148B45BF704BCA9E2E20374C939B0@mail.corporate.camiant.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_2BAB63F974AB4148B45BF704BCA9E2E20374C939B0mailcorporate_"
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 22 Jul 2009 08:04:05 -0700
Cc: "jkarthik@cisco.com" <jkarthik@cisco.com>
Subject: Re: [bmwg] WGLC: draft-ietf-bmwg-protection term-06 and meth-05
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bmwg>
List-Post: <mailto:bmwg@ietf.org>
List-Help: <mailto:bmwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jul 2009 17:16:53 -0000
I-D Title(s): Benchmarking Terminology for Protection Performance Filename(s): draft-ietf-bmwg-protection-meth-05.txt Reviewer Name: Vrushi Gurudevappa Date: July 20, 2009 Please organize your comments in the following categories below. Review Summary: This draft provides all the scenarios and measurement techniques needed to successfully benchmark FastReroute Protection. Overall: * Does/Do the draft(s) provide clear identification of the scope of work? E.g., is the class of device, system, or service being characterized clearly articulated. Yes. * If a terminology memo, are the measurement areas clearly defined or otherwise cited? Is the working set of supporting terminology sufficient and correct? To your knowledge, are the areas of the memo that may conflict with other bodies of work? Are there any measurements or terminology that are superfluous? Are any missing? n/a * If a methodology memo, does the methodology AND its corresponding terminology adequately define a benchmarking solution for its application area? Do the methodologies present sufficient detail for the experimental control of the benchmarks? Yes they do. * If neither a terminology or methodology, does the offered memo offer complementary information important to the use or application of the related benchmarking solution? n/a * Do you feel there are undocumented limitations or caveats to the benchmarking solution being proposed? If so, please describe. Not aware of any * Does the memo attempt to define acceptance criteria for any of the benchmark areas? No Technical Content: (Accuracy, Completeness of coverage) Are definitions accurate? Is the terminology offered relevant? Definitions are accurate and terminology is relevant To your knowledge, are there technical areas that are erroneous? Are there questionable technical areas that need to be re-examined or otherwise scrutinized. Not to my knowledge. Does the solution adequately address IPv6? n/a Do you feel the memo(s) being offered are technically mature enough for advancement to informational RFC? Yes, I do Clarity and Utility: If you had a need, would you utilize the benchmarking solutions advocated by this and its related memos? If not, why? Yes, I would and in fact I have done it in the past year. Conformance to BMWG principles: (see BMWG charter) http://www.ietf.cnri.reston.va.us/html.charters/bmwg-charter.html Do you have confidence that the benchmarks, as explicitly defined, will yield consistent results if repeated on the same device (DUT/SUT), multiple times for a given test condition. If not, cite benchmark(s) and issue(s). Absolutely yes. Do you have confidence that the benchmarks, if executed for a given test condition, utilizing the documented methodology on multiple test infrastructure (e.g., test equipment), would yield correct and consistent results on the same DUT/SUT? (Said differently, are the benchmark's methodology written with enough exacting detail, that benchmark implementation differences do not yield a difference in the measured quantities?) If not, cite benchmark(s) and issue(s). Yes of course. Do you feel that the benchmarks form a basis of comparison between implementations of quantity being characterized? (I.e., are the benchmarks suitable for comparing solutions from different vendors.) I do feel the benchmarks for a good basis for comparison between implementations. Thanks, -Vrushi
- [bmwg] WGLC: draft-ietf-bmwg-protection term-06 a… Al Morton
- Re: [bmwg] WGLC: draft-ietf-bmwg-protection term-… Al Morton
- Re: [bmwg] WGLC: draft-ietf-bmwg-protection term-… Al Morton
- Re: [bmwg] WGLC: draft-ietf-bmwg-protection term-… Scott Poretsky
- Re: [bmwg] WGLC: draft-ietf-bmwg-protection term-… Vrushabhendra Gurudevappa
- Re: [bmwg] WGLC: draft-ietf-bmwg-protection term-… Andrey Kiselev (ankisele)
- Re: [bmwg] WGLC: draft-ietf-bmwg-protection term-… Arun Gandhi
- Re: [bmwg] WGLC: draft-ietf-bmwg-protection term-… Rajiv Asati (rajiva)
- Re: [bmwg] WGLC: draft-ietf-bmwg-protection term-… Mohan Nanduri
- Re: [bmwg] WGLC: draft-ietf-bmwg-protection term-… Eric Brendel
- Re: [bmwg] WGLC: draft-ietf-bmwg-protection term-… Al Morton
- Re: [bmwg] WGLC: draft-ietf-bmwg-protection term-… Al Morton
- Re: [bmwg] WGLC: draft-ietf-bmwg-protection term-… Kris Michielsen
- Re: [bmwg] WGLC: draft-ietf-bmwg-protection term-… Jay Karthik (jakarthi)
- Re: [bmwg] WGLC: draft-ietf-bmwg-protection term-… Kris Michielsen
- Re: [bmwg] WGLC: draft-ietf-bmwg-protection term-… Scott Poretsky
- Re: [bmwg] WGLC: draft-ietf-bmwg-protection term-… Kris Michielsen
- Re: [bmwg] WGLC: draft-ietf-bmwg-protection term-… Rajiv Asati (rajiva)
- Re: [bmwg] WGLC: draft-ietf-bmwg-protection term-… Scott Poretsky
- Re: [bmwg] WGLC: draft-ietf-bmwg-protection term-… Jay Karthik (jakarthi)