RFC 5471: Guidelines for IP Flow Information Export (IPFIX) Testing
In plain English — editorial summary, not part of the RFC
This document presents a list of tests for implementers of IP Flow Information eXport (IPFIX) compliant Exporting Processes and Collecting Processes. This document specifies guidelines for a series of tests that can be run on the IPFIX Exporting Process and Collecting Process in order to probe the conformity and robustness of the IPFIX protocol implementations. These tests cover all important functions, in order to gain a level of confidence in the IPFIX implementation. Therefore, they allow the implementer to perform interoperability or plug tests with other IPFIX Exporting Processes and Collecting Processes. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5471
- Published
- March 2009
- Authors
- C. Schmoll; P. Aitken; B. Claise
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 32
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5476Packet Sampling (PSAMP) Protocol SpecificationsCurrent
March 2009
- RFC 5101Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow InformationObsoleted
January 2008
- RFC 5102Information Model for IP Flow Information ExportObsoleted
January 2008
- RFC 5470Architecture for IP Flow Information ExportUpdated
March 2009
- RFC 5472IP Flow Information Export (IPFIX) ApplicabilityCurrent
March 2009
- RFC 5473Reducing Redundancy in IP Flow Information Export (IPFIX) and Packet Sampling (PSAMP) ReportsCurrent
March 2009
- RFC 5474A Framework for Packet Selection and ReportingCurrent
March 2009
- RFC 5475Sampling and Filtering Techniques for IP Packet SelectionCurrent
March 2009
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?