IP Flow Information Export
# IP Flow Information Export

Internet Protocol Flow Information Export (IPFIX) is an IETF protocol, as well as the name of the IETF working group defining the protocol. It was created based on the need for a common, universal standard of export for Internet Protocol flow information from routers, probes and other devices that are used by mediation systems, accounting/billing systems and network management systems to facilitate services such as measurement, accounting and billing. The IPFIX standard defines how IP flow information is to be formatted and transferred from an exporter to a collector. Previously many data network operators were relying on Cisco Systems' proprietary NetFlow technology for traffic flow information export.

The IPFIX standards requirements were outlined in the original RFC 3917. Cisco NetFlow Version 9 was the basis for IPFIX. The basic specifications for IPFIX are documented in RFC 7011 through RFC 7015, and RFC 5103.

## Architecture

The following figure shows a typical architecture of information flow in an IPFIX architecture:

A pool of Metering Processes collects data packets at one or more Observation Points, optionally filters them and aggregates information about these packets. An Exporter then gathers each of the Observation Points together into an Observation Domain and sends this information via the IPFIX protocol to a Collector. Exporters and Collectors are in a many-to-many relationship: One Exporter can send data to many Collectors and one Collector can receive data from many Exporters.

## Protocol

Similar to the NetFlow Protocol, IPFIX considers a flow to be any number of packets observed in a specific timeslot and sharing a number of properties, e.g. "same source, same destination, same protocol". Using IPFIX, devices like routers can inform a central monitoring station about their view of a potentially larger network.

IPFIX is a push protocol, i.e. each sender will periodically send IPFIX messages to configured receivers without any interaction by the receiver.

The actual makeup of data in IPFIX messages is to a great extent up to the sender. IPFIX introduces the makeup of these messages to the receiver with the help of special Templates. The sender is also free to use user-defined data types in its messages, so the protocol is freely extensible and can adapt to different scenarios.

IPFIX prefers the Stream Control Transmission Protocol (SCTP) as its transport layer protocol, but also allows the use of the Transmission Control Protocol (TCP) or User Datagram Protocol (UDP).

## Example

A simple information set sent via IPFIX might look like this:

This information set would be sent in the following IPFIX message:

| Bits 0..15 | Bits 16..31 |
| - | - |
| Version = 0x000a | Message Length = 64 Bytes |
| Export Timestamp = 2005-12-31 23:59:60 ||
| Sequence Number = 0 ||
| Observation Domain ID = 12345678 ||
| Set ID = 2 (Template) | Set Length = 20 Bytes |
| Template ID = 256 | Number of Fields = 3 |
| Typ = sourceIPv4Address | Field Length = 4 Bytes |
| Typ = destinationIPv4Address | Field Length = 4 Bytes |
| Typ = packetDeltaCount | Field Length = 4 Bytes |
| Set ID = 256 (Data Set using Template 256) | Set Length = 28 Bytes |
| Record 1, Field 1 = 192.168.0.201 ||
| Record 1, Field 2 = 192.168.0.1 ||
| Record 1, Field 3 = 235 Packets ||
| Record 2, Field 1 = 192.168.0.202 ||
| Record 2, Field 2 = 192.168.0.1 ||
| Record 2, Field 3 = 42 Packets ||

As can be seen, the message contains the IPFIX header and two IPFIX Sets: One Template Set that introduces the build-up of the Data Set used, as well as one Data Set, which contains the actual data. When IPFIX is sent over a protocol which keeps a session state (TCP or SCTP), the Template Set need not be retransmitted since it is buffered in Collectors. Since the Template Set can change over time, it must be retransmitted if a new session state is established or if IPFIX is sent over UDP which is a session-less protocol.

