Re: [bmwg] WGLC: draft-ietf-bmwg-ipflow-meth-03
"Jan Novak (janovak)" <janovak@cisco.com> Sun, 02 October 2011 18:09 UTC
Return-Path: <janovak@cisco.com>
X-Original-To: bmwg@ietfa.amsl.com
Delivered-To: bmwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B47621F85A8 for <bmwg@ietfa.amsl.com>; Sun, 2 Oct 2011 11:09:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.892
X-Spam-Level:
X-Spam-Status: No, score=-9.892 tagged_above=-999 required=5 tests=[AWL=0.708, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gHkQ680Sn8HV for <bmwg@ietfa.amsl.com>; Sun, 2 Oct 2011 11:09:02 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 58F6621F85A4 for <bmwg@ietf.org>; Sun, 2 Oct 2011 11:09:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=janovak@cisco.com; l=4529; q=dns/txt; s=iport; t=1317579122; x=1318788722; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=Tp31sHzuusVOlmfYsoNreKeEHXgM32gJvZ6eeRtEvwo=; b=GcckHRc0bBP4M0JO3a0kP4nVARwwGIx/oVDrEvHOjEms4rv8Ra5Ejz1D 9HFRZo76DSEU+oz2qWpLCP7KpW8kXFgKKucy6HbGjG98752CwhJSuaT06 gt3/3bU8a6qApxVIjrIuNzqp3FjokYo2+JkoWJAvxonD/RvqVebapnF1L c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAOOniE6Q/khM/2dsb2JhbAA7BqgOgQWBUwEBAQECAQEBAQ8BHQo0FwQCAQgOAwEDAQEBCgYXAQYBJh8DBggBAQQBEggah1kGmm0BnGiEAIJAYQSZDotlLQ
X-IronPort-AV: E=Sophos;i="4.68,477,1312156800"; d="scan'208";a="56928033"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 02 Oct 2011 18:12:01 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p92IC18L027575; Sun, 2 Oct 2011 18:12:01 GMT
Received: from xmb-ams-212.cisco.com ([144.254.75.23]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 2 Oct 2011 20:12:01 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 02 Oct 2011 20:12:02 +0200
Message-ID: <C95CC96B171AF24CA1BB6CA3C52D0BA0010DB498@XMB-AMS-212.cisco.com>
In-Reply-To: <201109161541.p8GFfXqW009331@alpd052.aldc.att.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [bmwg] WGLC: draft-ietf-bmwg-ipflow-meth-03
Thread-Index: Acx0hy6GhFbHw3YURj63j7JleZz5OAMp10JQ
References: <201108011522.p71FLxj6018359@alpd052.aldc.att.com> <201109161541.p8GFfXqW009331@alpd052.aldc.att.com>
From: "Jan Novak (janovak)" <janovak@cisco.com>
To: Al Morton <acmorton@att.com>, bmwg@ietf.org
X-OriginalArrivalTime: 02 Oct 2011 18:12:01.0824 (UTC) FILETIME=[C8712A00:01CC812E]
Subject: Re: [bmwg] WGLC: draft-ietf-bmwg-ipflow-meth-03
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Sun, 02 Oct 2011 18:09:03 -0000
Hi Al, Thanks for your corrections - rectified. I have also cross-checked section 12.2 and 2.1 to contain all the references. Jan The climate of Edinburgh is such that the weak succumb young .... and the strong envy them. Dr. Johnson -----Original Message----- From: bmwg-bounces@ietf.org [mailto:bmwg-bounces@ietf.org] On Behalf Of Al Morton Sent: 16 September 2011 16:42 To: bmwg@ietf.org Subject: Re: [bmwg] WGLC: draft-ietf-bmwg-ipflow-meth-03 At 11:22 AM 8/1/2011, Al Morton wrote: >BMWG, >CC: IPFIX WG, > >This message begins the third WG Last call on the draft: > >IP Flow Information Accounting and Export Benchmarking Methodology > >A URL for this draft is: >http://tools.ietf.org/html/draft-ietf-bmwg-ipflow-meth-03 In addition to Paul's comments, I found a few more - mostly clarifying edits, I think. Since I have to read every WGLC in case it reaches consensus and moves to publication-requested, I'm writing these comments as Al bmwg chair 1 Introduction, 5 para ... Therefore, this document focuses on a methodology for how to measure the maximum IP flow rate that a network device can sustain without impacting the forwarding plane, without losing any IP flow information, and without compromising the IP flow accuracy (see section 7 for details). Suggest: ... Therefore, this document specifies a ^^^^^^^^^^^^ methodology to measure the maximum IP flow rate that a ^^^^^^^^^^^^^^^^^^^^^^ 1 Introduction, 7 para ... A variety of different network device architectures exist that are capable of Flow monitoring and export. As such, this document does not attempt to list the various white box variables (CPU load, memory utilization, TCAM utilization etc) that could be gathered as ... TCAM, and all other unusual acronyms, need to be expanded at first use. >>> Somewhere, there is a list of acronyms that IETFers need not expand, I couldn't find it today, and wonder if anyone knows its location. 2.2.5 Flow Export Rate Definition: The number of Cache entries that expire from the Cache (as defined by the Flow Expiration term) and are exported to the Collector within a measurement time interval. The measured Flow Export Rate MUST include BOTH the Data Stream and the Control Information, as defined in section 2 of [RFC5470]. "BOTH" is not an RFC2119 requirement term, so it can't be capitalized here as though it is. You could try: The measured Flow Export Rate MUST include *both* the Data Stream 3. Flow Monitoring Performance Metric Suggest: 3. Flow Monitoring Performance Benchmark (for rationale behind this change, see the comment/text below) 3.3 Measurement Concept, last paragraph: ... The Monitoring Plane handles Flows which reflect the analysed traffic. The metric that measures the Monitoring Plane performance is Flow Export Rate, and the benchmark is the Flow Monitoring Throughput. Suggest: ...The metric for Monitoring Plane performance is ^^^ Flow Export Rate, and the benchmark is the Flow Monitoring Throughput. 4.1 Measurement Topology, 1 para ...Instead of the Forwarding Plane, these appliances generally have some kind of feed (an optical splitter, an interface sniffing traffic on a shared media or an internal channel on the DUT providing a copy of the traffic) providing the information about the traffic necessary for Flow monitoring analysis. The measurement topology then needs to be adjusted to the appliance architecture. Suggest: ... The measurement topology then needs to be adjusted to the appliance architecture, and MUST be described in the results. 4.2 Baseline DUT Set Up, 3 para The DUT export interface (see figure 2) MUST be configured with sufficient output buffers to avoid dropping the Flow Export data due to a simple lack of resources in the interface hardware. Suggest that since the buffer size is critical, we make it a mandatory part of the results/report. 11.2 Informative References Add references to the RFCs listed in the Existing Terminology Section. _______________________________________________ bmwg mailing list bmwg@ietf.org https://www.ietf.org/mailman/listinfo/bmwg
- [bmwg] WGLC: draft-ietf-bmwg-ipflow-meth-03 Al Morton
- Re: [bmwg] WGLC: draft-ietf-bmwg-ipflow-meth-03 Al Morton
- Re: [bmwg] WGLC: draft-ietf-bmwg-ipflow-meth-03 Fernando Calabria (fcalabri)
- Re: [bmwg] WGLC: draft-ietf-bmwg-ipflow-meth-03 David Newman
- Re: [bmwg] WGLC: draft-ietf-bmwg-ipflow-meth-03 Al Morton
- Re: [bmwg] WGLC: draft-ietf-bmwg-ipflow-meth-03 Jan Novak (janovak)