Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of Flow Information

Aitken, P.

doi:10.17487/rfc7011

Cited by 100 publications

(19 citation statements)

References 22 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…As the objective is to determine if a sequence of elements belongs to one class and to measure how the system performs, individual packets have been grouped into flows. Using the definition of flow [9] which are a set of packets with same source IP, destination IP, source port, destination port and protocol in a period of time, bidirectional flows have been created [10].…”

Section: Methodsmentioning

confidence: 99%

Time-Aware Detection Systems

López-Vizcaíno¹,

Vigoya²,

Cacheda³

et al. 2019

The 2nd XoveTIC Conference (XoveTIC 2019)

View full text Add to dashboard Cite

Communication network data has been growing in the last decades and with the generalisation of the Internet of Things (IoT) its growth has increased. The number of attacks to this kind of infrastructures have also increased due to the relevance they are gaining. As a result, it is vital to guarantee an adequate level of security and to detect threats as soon as possible. Classical methods emphasise in detection but not taking into account the number of records needed to successfully identify an attack. To achieve this, time-aware techniques both for detection and measure may be used. In this work, well-known machine learning methods will be explored to detect attacks based on public datasets. In order to obtain the performance, classic metrics will be used but also the number of elements processed will be taken into account in order to determine a time-aware performance of the method.

show abstract

Section: Methodsmentioning

confidence: 99%

Time-Aware Detection Systems

López-Vizcaíno¹,

Vigoya²,

Cacheda³

et al. 2019

The 2nd XoveTIC Conference (XoveTIC 2019)

View full text Add to dashboard Cite

show abstract

“…For traffic monitoring, we consider legacy tools natively supported by OvS, namely sFlow [1] and IPFIX [2]. The measurement collector is placed outside the server, in a remote node across the network.…”

Section: A Testbedmentioning

confidence: 99%

“…We follow an experimental approach for the purpose of our study. We set up a testbed around an Open vSwitch (OvS) 2 switch, which is arguably the most popular virtual switch nowadays, natively integrated in OpenStack and VMware. We consider the two typical levels of granularity of traffic collection tools, namely the packet level monitoring offered by sFlow [1] and the flow level monitoring offered by IPFIX [2].…”

Section: Introductionmentioning

confidence: 99%

On the Cost of Measuring Traffic in a Virtualized Environment

Gogunska

Barakat

Urvoy-Keller

et al. 2018

2018 IEEE 7th International Conference on Cloud Networking (CloudNet)

View full text Add to dashboard Cite

The current trend in application development and deployment is to package applications and services within containers or virtual machines. This results in a blend of virtual and physical resources with complex network interconnection schemas mixing virtual and physical switches along with specific protocols to build virtual networks spanning over several servers. While the complexity of this setup is hidden by private/public cloud management solutions, e.g. OpenStack, this new environment constitutes a challenge when it comes to monitor and debug performance related issues. In this paper, we introduce the problem of measuring traffic in a virtualized environment and focus on one typical scenario, namely virtual machines interconnected with a virtual switch. For this scenario, we assess the cost of continuously measuring the network traffic activity of the machines. Specifically, we seek to estimate the competition that exists to access the physical resources (e.g., CPU) of the physical server between the measurement task and the legacy application activity.

show abstract

“…For example, OpenFlow-enabled routers can receive a "read state" message that requests to send statistic information like the number of existing flows [17]. Another example is IP Flow Information Export (IP-FIX), which enables to send statistic information like the number of flows [18]. The server identifies bottleneck links based on information about the number of existing flows received from the routers and the bandwidth of each link, and then it calculates the transmission rate which should be allocated to each flow by dividing the bandwidth of the bottleneck link by the number of competing flows.…”

Section: Proposed Schemementioning

confidence: 99%

A Bandwidth Allocation Scheme to Improve Fairness and Link Utilization in Data Center Networks

Yusuke

Koga

Iida

2018

IEICE Trans. Commun.

View full text Add to dashboard Cite

Yusuke ITO †a) , Student Member, Hiroyuki KOGA †b) , Member, and Katsuyoshi IIDA † †c) , Senior Member SUMMARY Cloud computing, which enables users to enjoy various Internet services provided by data centers (DCs) at anytime and anywhere, has attracted much attention. In cloud computing, however, service quality degrades with user distance from the DC, which is unfair. In this study, we propose a bandwidth allocation scheme based on collectable information to improve fairness and link utilization in DC networks. We have confirmed the effectiveness of this approach through simulation evaluations.

show abstract

Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of Flow Information

Cited by 100 publications

References 22 publications

Time-Aware Detection Systems

Time-Aware Detection Systems

On the Cost of Measuring Traffic in a Virtualized Environment

A Bandwidth Allocation Scheme to Improve Fairness and Link Utilization in Data Center Networks

Contact Info

Product

Resources

About