RFC 6645: IP Flow Information Accounting and Export Benchmarking Methodology
In plain English — editorial summary, not part of the RFC
This document provides a methodology and framework for quantifying the performance impact of the monitoring of IP flows on a network device and the 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 RFC 5470, "Architecture for IP Flow Information Export". The methodology quantifies the impact of the IP flow monitoring process on the network equipment. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6645
- Published
- July 2012
- Authors
- J. Novak
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 39
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7133Information Elements for Data Link Layer Traffic MeasurementCurrent
May 2014
- RFC 6615Definitions of Managed Objects for IP Flow Information ExportCurrent
June 2012
- RFC 6727Definitions of Managed Objects for Packet SamplingCurrent
October 2012
- RFC 6728Configuration Data Model for the IP Flow Information Export (IPFIX) and Packet Sampling (PSAMP) ProtocolsCurrent
October 2012
- RFC 6815Applicability Statement for RFC 2544: Use on Production Networks Considered HarmfulCurrent
November 2012
- RFC 6235IP Flow Anonymization SupportCurrent
May 2011
- RFC 6049Spatial Composition of MetricsUpdated
January 2011
- RFC 6038Two-Way Active Measurement Protocol (TWAMP) Reflect Octets and Symmetrical Size FeaturesCurrent
October 2010
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?