draft-ietf-bmwg-ipflow-meth-08.txt   draft-ietf-bmwg-ipflow-meth-09.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: 9 September, 2012 9 March 2012 Expires: 12 September, 2012 12 March 2012
IP Flow Information Accounting and Export Benchmarking IP Flow Information Accounting and Export Benchmarking
Methodology Methodology
draft-ietf-bmwg-ipflow-meth-08.txt draft-ietf-bmwg-ipflow-meth-09.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 9 September, 2012. This Internet-Draft will expire on 12 September, 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 5, line 25 skipping to change at page 5, line 25
For long-running Flows, the time interval after which the Metering For long-running Flows, the time interval after which the Metering
Process expires a Cache entry to ensure Flow data is regularly Process expires a Cache entry to ensure Flow data is regularly
updated updated
Discussion: Discussion:
This term is typically presented as a configurable option in the This term is typically presented as a configurable option in the
particular Flow monitoring implementation. See section 5.1.1 of particular Flow monitoring implementation. See section 5.1.1 of
[RFC5470] for more detailed discussion. [RFC5470] for more detailed discussion.
Flows are considered long-running when they last longer than Flows are considered long-running when they last longer than
several multiples of the Active Timeout. When the Active Timeout several multiples of the Active Timeout. If the Active Timeout is
is zero Flows are long-running if they contain a larger number of zero, then Flows are considered long-running if they contain many
packets than usual for a single transaction based Flows, in the more packets (tens of packets) than usually observed in a single
order of tens of packets and higher. transaction.
Measurement units: Measurement units:
Seconds Seconds
2.2.4 Inactive Timeout 2.2.4 Inactive Timeout
Definition: Definition:
The time interval used by the Metering Process to expire an entry The time interval used by the Metering Process to expire an entry
from the Cache, when no more packets belonging to that specific from the Cache, when no more packets belonging to that specific
Cache entry have been observed during the interval. Cache entry have been observed during the interval.
 End of changes. 4 change blocks. 
7 lines changed or deleted 7 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/