[bmwg] WGLC: draft-ietf-bmwg-mpls-forwarding-meth-00
"Silvija Andrijic Dry (sdry)" <sdry@cisco.com> Thu, 16 October 2008 15:46 UTC
Return-Path: <bmwg-bounces@ietf.org>
X-Original-To: bmwg-archive-1@ietf.org
Delivered-To: ietfarch-bmwg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 998D33A6A73; Thu, 16 Oct 2008 08:46:58 -0700 (PDT)
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 482303A6ABF for <bmwg@core3.amsl.com>; Thu, 16 Oct 2008 08:46:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 5c7ra1gvp8Bj for <bmwg@core3.amsl.com>; Thu, 16 Oct 2008 08:46:57 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id CDF553A6939 for <bmwg@ietf.org>; Thu, 16 Oct 2008 08:46:56 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,424,1220227200"; d="scan'208";a="24515214"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 16 Oct 2008 15:47:57 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9GFlvOp032415; Thu, 16 Oct 2008 11:47:57 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9GFlvnA005859; Thu, 16 Oct 2008 15:47:57 GMT
Received: from xmb-rtp-215.amer.cisco.com ([64.102.31.124]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 16 Oct 2008 11:47:57 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 16 Oct 2008 11:47:09 -0400
Message-ID: <98D7DD91CEAC714AB0163AE94766264101660793@xmb-rtp-215.amer.cisco.com>
In-Reply-To: <FA59234A6DCF2C48A6FE427870763DCA0159E944@xmb-rtp-213.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [bmwg] WGLC: draft-ietf-bmwg-mpls-forwarding-meth-00
Thread-Index: AckeT+msg2jogHa6QZ6cr7UnDUZSQQN69IAQANpizcA=
References: <200809241413.m8OEDFD0009557@klph001.kcdc.att.com> <FA59234A6DCF2C48A6FE427870763DCA0159E944@xmb-rtp-213.amer.cisco.com>
From: "Silvija Andrijic Dry (sdry)" <sdry@cisco.com>
To: Al Morton <acmorton@att.com>, bmwg@ietf.org
X-OriginalArrivalTime: 16 Oct 2008 15:47:57.0217 (UTC) FILETIME=[8F4F1110:01C92FA6]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4186; t=1224172077; x=1225036077; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=sdry@cisco.com; z=From:=20=22Silvija=20Andrijic=20Dry=20(sdry)=22=20<sdry@ci sco.com> |Subject:=20[bmwg]=20WGLC=3A=20draft-ietf-bmwg-mpls-forward ing-meth-00 |Sender:=20 |To:=20=22Al=20Morton=22=20<acmorton@att.com>,=20<bmwg@ietf .org>; bh=bKKt0Ef7SAfpYVOLaP7HAvgacsVTST+andtRBUOON9c=; b=VWdG5f8QiSmT2PXI1N2++HQ4kYog8HId4zo1BDDEn5GPIqexKAREj60fSO Jn+e7eoqijvSUrvsHH4bwLITT7IFf73m3i09BUXieFfw40+oGPoZQTu91IgU 4aDk1YMxIm;
Authentication-Results: rtp-dkim-2; header.From=sdry@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; );
Subject: [bmwg] WGLC: draft-ietf-bmwg-mpls-forwarding-meth-00
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: <https://www.ietf.org/mailman/private/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: bmwg-bounces@ietf.org
Errors-To: bmwg-bounces@ietf.org
Al and BMWG, Below is my WGLC review of draft-ietf-bmwg-mpls-forwarding-meth-00. In general I'm in support of progressing this draft. Thx, Silvija Last Call Review Template I-D Title(s): MPLS Forwarding Benchmarking Methodology Filename(s): draft-ietf-bmwg-mpls-forwarding-meth-00.txt Reviewer Name: Silvija Dry Date: 10/16/08 Please organize your comments in the following categories below. Review Summary: 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? The methodology is defined with adequate level of detail to be useful benchmarking solution for MPLS products. * 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. No. * 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? Yes. To your knowledge, are there technical areas that are erroneous? Are there questionable technical areas that need to be re-examined or otherwise scrutinized. No. 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. 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. 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). 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. 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.) Yes. If not, cite benchmarks and issues. For those benchmarks cited above, do you feel that the benchmarks, as specified, have universal applicability for the given behavior being characterized? (i.e., benchmarks might not form a basis for cross-vendor comparison, can be used universally in a different role.) Yes. Editorial Comments: (includes any deficiencies noted w.r.t. I-D Nits, spelling, & grammar) None. _______________________________________________ _______________________________________________ bmwg mailing list bmwg@ietf.org https://www.ietf.org/mailman/listinfo/bmwg
- Re: [bmwg] WGLC: draft-ietf-bmwg-mpls-forwarding-… Al Morton
- [bmwg] WGLC: draft-ietf-bmwg-mpls-forwarding-meth… Al Morton
- Re: [bmwg] WGLC: draft-ietf-bmwg-mpls-forwarding-… Chip Popoviciu (cpopovic)
- [bmwg] Review: WGLC: draft-ietf-bmwg-mpls-forward… Rajiv Papneja
- [bmwg] WGLC: draft-ietf-bmwg-mpls-forwarding-meth… Silvija Andrijic Dry (sdry)
- Re: [bmwg] WGLC: draft-ietf-bmwg-mpls-forwarding-… Al Morton
- [bmwg] WGLC: draft-ietf-bmwg-mpls-forwarding-meth… Mike Hamilton
- Re: [bmwg] WGLC: draft-ietf-bmwg-mpls-forwarding-… Bill Cerveny
- Re: [bmwg] WGLC: draft-ietf-bmwg-mpls-forwarding-… Al Morton
- Re: [bmwg] WGLC: draft-ietf-bmwg-mpls-forwarding-… Al Morton
- Re: [bmwg] WGLC: draft-ietf-bmwg-mpls-forwarding-… Rajiv Asati (rajiva)
- Re: [bmwg] WGLC: draft-ietf-bmwg-mpls-forwarding-… Rajiv Asati (rajiva)
- Re: [bmwg] WGLC: draft-ietf-bmwg-mpls-forwarding-… Rajiv Asati (rajiva)