draft-novak-bmwg-ipflow-meth-05.txt IP Flow Information Accounting and Export Benchmarking Methodology Jan Novak Cisco Systems Presenting to IETF /08/20151

draft-novak-bmwg-ipflow-meth-05.txt Document Goal Defines metrics to characterise Flow Monitoring performance based on: - Architecture Model for IP Flow Information Export: RFC5740 Defines conditions to perform Network Devices benchmarking in the presence of Flow Monitoring –IPv4 Benchmarking Methodology: RFC2544 –IPv6 Benchmarking Methodology: RFC /08/20152

draft-novak-bmwg-ipflow-meth-05.txt3 Test Topology | | | Collector | | | | | | | | | | | sender | >| | >| receiver | | | | DUT | | | | | | | | | | receiver |< | |< | sender | | | | | | | /08/20153

draft-novak-bmwg-ipflow-meth-05.txt 4 The Concept – DUT 06/08/20154 Forwarding PlaneFlow Monitoring Plane Traffic information Flow Export packets Metric: packet rate Metric: Flow Record rate IPFIX | Sflow | Netflow | Others

06/08/2015draft-novak-bmwg-ipflow-meth-05.txt5 What is the Benchmark Flow Monitoring Plane: How many Flow Records the DUT can handle per second without dropping any Flow information and packets – Flow Monitoring Throughput Data Forwarding Plane: RFC2544 Throughput measured in the presence of Flow Monitoring

draft-novak-bmwg-ipflow-meth-05.txt CHANGES from version 4 Merged Normal and Overflow Cache Mode (former section 5.1 and 5.2) into one section/test set-up Allows for the test abstraction from the implementations or platform HW/SW restrictions 06/08/20156

draft-novak-bmwg-ipflow-meth-05.txt06/08/20157 CHANGES from version 4 Moved all miscellaneous tests into another Appendix B Moved Bidirectional Traffic set-up into Appendix B Clarified the set-up with several observation points

06/08/2015draft-novak-bmwg-ipflow-meth-05.txt8 CHANGES from version 4 Added more details on Flow Export Rate measurement – section 5.5 Expanded the RFC2544 measurements (section 6) with more details regarding test conditions and traffic set-ups

06/08/2015draft-novak-bmwg-ipflow-meth-05.txt9 Version 5 addresses all so far received comments and open issues from the last meeting

Proposed Scope Item (discussed on the list) Flow Export and Collection: Develop terminology and methods to characterize network devices flow monitoring, export, and collection. The goal is a methodology to assess the maximum IP flow rate that a network device can sustain without losing any IP flow information or compromising the accuracy of information exported on the IP flows, and to asses the forwarding plane performance (if the forwarding function is present) in the presence of Flow Monitoring.