2013
DOI: 10.17487/rfc7015
|View full text |Cite
|
Sign up to set email alerts
|

Flow Aggregation for the IP Flow Information Export (IPFIX) Protocol

Abstract: This document provides a common implementation-independent basis for the interoperable application of the IP Flow

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
11
0

Year Published

2013
2013
2022
2022

Publication Types

Select...
6
2
1

Relationship

0
9

Authors

Journals

citations
Cited by 66 publications
(11 citation statements)
references
References 15 publications
(6 reference statements)
0
11
0
Order By: Relevance
“…Flows are analyzed within fixed time intervals (every 5 min by default). Bidirectional flows [96] are used since, according to some works (e.g. [8]), unidirectional flows may entail biased results.…”
Section: Architecturementioning
confidence: 99%
“…Flows are analyzed within fixed time intervals (every 5 min by default). Bidirectional flows [96] are used since, according to some works (e.g. [8]), unidirectional flows may entail biased results.…”
Section: Architecturementioning
confidence: 99%
“…Such patterns typically include source and destination IP addresses, port numbers, timestamps and transmission duration, as well as the amount of data and number of packets sent. Flow monitoring systems like compatible IOS routers usually export Netflow [29] or IPFIX [144] records and transmit them to a central node for analysis.…”
Section: Network Domainmentioning
confidence: 99%
“…For the purpose of the aggregation process there was a need to implement some information elements related to flow aggregation according to [14]. The implemented method was verified by preliminary measurements.…”
Section: Preliminary Experimentsmentioning
confidence: 99%