draft-ietf-bmwg-ipflow-meth-06.txt   draft-ietf-bmwg-ipflow-meth-07.txt 
Internet Engineering Task Force Jan Novak Internet Engineering Task Force Jan Novak
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended status: Informational Intended status: Informational
Expires: 22 July, 2012 21 January 2012 Expires: 31 July, 2012 31 January 2012
IP Flow Information Accounting and Export Benchmarking IP Flow Information Accounting and Export Benchmarking
Methodology Methodology
draft-ietf-bmwg-ipflow-meth-06.txt draft-ietf-bmwg-ipflow-meth-07.txt
Abstract Abstract
This document provides a methodology and framework for quantifying This document provides a methodology and framework for quantifying
the performance impact of monitoring of IP flows on a network device the performance impact of monitoring of IP flows on a network device
and export of this information to a collector. It identifies the rate and export of this information to a collector. It identifies the rate
at which the IP flows are created, expired, and successfully exported at which the IP flows are created, expired, and successfully exported
as a new performance metric in combination with traditional as a new performance metric in combination with traditional
throughput. The metric is only applicable to the devices compliant throughput. The metric is only applicable to the devices compliant
with the Architecture for IP Flow Information Export [RFC5470]. with the Architecture for IP Flow Information Export [RFC5470].
skipping to change at page 1, line 39 skipping to change at page 1, line 39
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-Drafts documents at any time. It is inappropriate to use Internet-Drafts
as reference material or to cite them other than as "work in as reference material or to cite them other than as "work in
progress." progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on 2 April, 2012. This Internet-Draft will expire on 31 July, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 15, line 46 skipping to change at page 15, line 46
Process and Exporting Process Process and Exporting Process
4.3.6 MPLS Measurement Specifics 4.3.6 MPLS Measurement Specifics
The Flow Record configuration for measurements with MPLS The Flow Record configuration for measurements with MPLS
encapsulated traffic SHOULD contain the MPLS label. encapsulated traffic SHOULD contain the MPLS label.
The tester SHOULD ensure that the data received by the Collector The tester SHOULD ensure that the data received by the Collector
contains the expected MPLS labels. contains the expected MPLS labels.
The MPLS forwarding performance document [RFC5695] specifies number The MPLS forwarding performance document [RFC5695] specifies a
of possible MPLS label operations to test. The Observation Points number of possible MPLS label operations to test. The Observation
MUST be placed on all the DUT test interfaces where the particular Points MUST be placed on all the DUT test interfaces where the
MPLS label operation takes place. The performance measurements particular MPLS label operation takes place. The performance
SHOULD be performed with only one MPLS label operation at the time. measurements SHOULD be performed with only one MPLS label operation
at the time.
The DUT MUST be configured in such a way that all the traffic is The DUT MUST be configured in such a way that all the traffic is
subject to the measured MPLS label operation. subject to the measured MPLS label operation.
Novak Expires July, 2012 Novak Expires July, 2012
4.4 Collector 4.4 Collector
The Collector is needed in order to capture the Flow Export data The Collector is needed in order to capture the Flow Export data
which allows the Flow Monitoring Throughput to be measured. which allows the Flow Monitoring Throughput to be measured.
skipping to change at page 16, line 35 skipping to change at page 16, line 35
During the analysis, the Flow Export data needs to be decoded and the During the analysis, the Flow Export data needs to be decoded and the
received Flow Records counted. received Flow Records counted.
The capture buffer MUST be cleared at the beginning of each The capture buffer MUST be cleared at the beginning of each
measurement. measurement.
4.5 Sampling 4.5 Sampling
Packet sampling and flow sampling is out of scope of this document. Packet sampling and flow sampling is out of scope of this document.
This document applies to situations without packet, flow or export This document applies to situations without packet, flow, or export
sampling. sampling.
4.6 Frame Formats 4.6 Frame Formats
Flow monitoring itself is not dependent in any way on the media used Flow monitoring itself is not dependent in any way on the media used
on the input and output ports. Any media can be used as supported by on the input and output ports. Any media can be used as supported by
the DUT and the test equipment. the DUT and the test equipment.
At the time of writing the most common transmission media and At the time of writing the most common transmission media and
corresponding frame formats (Ethernet, Packet over SONET) for IPv4, corresponding frame formats (Ethernet, Packet over SONET) for IPv4,
skipping to change at page 20, line 5 skipping to change at page 20, line 5
unique combinations of Flow Keys values SHOULD be several times unique combinations of Flow Keys values SHOULD be several times
larger than the DUT Cache Size. This makes sure that any incoming larger than the DUT Cache Size. This makes sure that any incoming
packet will never refresh any already existing Cache entry. packet will never refresh any already existing Cache entry.
The availability of Cache Size, Inactive Timeout, Active Timeout as The availability of Cache Size, Inactive Timeout, Active Timeout as
configuration parameters is implementation specific. If the Flow configuration parameters is implementation specific. If the Flow
monitoring implementation does not support these parameters, the test monitoring implementation does not support these parameters, the test
Novak Expires July, 2012 Novak Expires July, 2012
possibilities as specified by this document are restricted. Some possibilities as specified by this document are restricted. Some
testing might be viable if the implementation follows [IPFIX-CONFIG] testing might be viable if the implementation follows the
document and needs to be considered on the case by case basis. [IPFIX-CONFIG] document and needs to be considered on the case by
by case basis.
5.2 Traffic Configuration 5.2 Traffic Configuration
Traffic Generation Traffic Generation
The traffic generator needs to increment the Flow Keys values with The traffic generator needs to increment the Flow Keys values with
each sent packet, this way each packet represents one Cache entry each sent packet, this way each packet represents one Cache entry
in the DUT Cache. in the DUT Cache.
If the test traffic rate is below the maximum media rate for If the test traffic rate is below the maximum media rate for
the particular packet size the traffic generator MUST send the the particular packet size the traffic generator MUST send the
 End of changes. 6 change blocks. 
11 lines changed or deleted 13 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/