Document Action: 'IP Flow Information Accounting and Export Benchmarking Methodology' to Informational RFC (draft-ietf-bmwg-ipflow-meth-10.txt)

The IESG <> Mon, 23 April 2012 21:11 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id ECD1011E8088; Mon, 23 Apr 2012 14:11:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id WwxahWNipi-x; Mon, 23 Apr 2012 14:11:08 -0700 (PDT)
Received: from (localhost []) by (Postfix) with ESMTP id D5A2611E808A; Mon, 23 Apr 2012 14:11:07 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Document Action: 'IP Flow Information Accounting and Export Benchmarking Methodology' to Informational RFC (draft-ietf-bmwg-ipflow-meth-10.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.01
Message-ID: <>
Date: Mon, 23 Apr 2012 14:11:07 -0700
Cc: bmwg chair <>, bmwg mailing list <>, RFC Editor <>
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 23 Apr 2012 21:11:09 -0000

The IESG has approved the following document:
- 'IP Flow Information Accounting and Export Benchmarking Methodology'
  (draft-ietf-bmwg-ipflow-meth-10.txt) as an Informational RFC

This document is the product of the Benchmarking Methodology Working

The IESG contact persons are Ronald Bonica and Benoit Claise.

A URL of this Internet Draft is:

     Technical Summary 
For internetworking devices that perform routing or switching as 
their primary function, the likely reduction in traffic-handling
capacity when traffic monitoring is active continues to be a relevant 
question many years after it was first asked ("What happens when you
turn-on Netflow?"). 

This document provides a methodology and framework for quantifying 
the performance impact of monitoring of IP flows on a network device
and export of this information to a collector. It identifies the rate 
at which the IP flows are created, expired, and successfully exported 
as a new performance metric in combination with traditional 
throughput. The metric is only applicable to the devices compliant 
with the Architecture for IP Flow Information Export [RFC5470].

The methods are applicable to both internetworking devices that 
forward traffic and other devices that simply monitor traffic with 
non-intrusive access to transmission facilities.
The Forwarding Plane and Monitoring Plane represent two separate
functional blocks, each with its own performance capability. The
Forwarding Plane handles user data packets and is fully characterised 
by the metrics defined by [RFC2544]. 
The Monitoring Plane handles Flows which reflect the analysed 
traffic. The metric for Monitoring Plane performance is Flow Export 
Rate, and the benchmark is the Flow Monitoring Throughput.

     Working Group Summary 
Quite a few bmwg participants and ipfix participants have given this a look
and now concur with the results. 
Examples of Test Implementation and Results were presented 
during development, which is compelling evidence of practicality.
There were WGLCs yielding long lists of comments/issues to deal with, 
and this was finally accomplished. It took several WGLCs before this version
reached consensus (with a few minor editorial changes).  

     Document Quality 
All would agree that Paul Aitken provided very careful and complete 
reviews throughout the development process; he left no stone unturned.

Al Morton  is shepherd.