Professional Documents
Culture Documents
Brian Trammell - CERT/NetSA - Pittsburgh, PA, US Elisa Boschi - Hitachi Europe - Zurich, CH NANOG 41 - Albuquerque, NM, US - October 15, 2007
What is IPFIX?
Emerging IETF standard for exible export of IP ow data from routers or other metering processes. Denes a rich, easily extensible information model, a template-driven data representation, and a unidirectional protocol for export of IP ow data over a variety of transport protocols. Does not dene specic requirements for ow assembly, ow key selection, etc.
October 15, 2007 NANOG 41 - Albuquerque 2
Representation
Templates in the message stream describe the data sets. Allows exible and efcient representation of ows on the wire.
message
template A template B data A1 data B1
message
data A2
NANOG 41 - Albuquerque
Information model
The information model supports reporting a wide variety of information elements:
Five-tuple (IPv4, IPv6) and standard counters Packet treatment: e.g., routed next hop and AS Detailed counters: e.g., sum of squares, ag counters Timestamps down to nanosecond resolution Any ICMP, TCP, UDP header eld Layer 2, VLAN, MPLS, and other sub-IP information
Flow keys are not limited to specic information elements. New IEs registered with IANA. Enterprise-specic IEs for private extensions.
October 15, 2007 NANOG 41 - Albuquerque 5
Comparison to sFlow
sFlow is a packet sampling protocol
Intended for many of the same applications as NetFlow and IPFIX. Use of packet sampling instead of ow assembly reduces state overhead on measurement device. Analogous to PSAMP, which extends IPFIX for export of sampled packet data.
Status
Its taken longer than wed thought, but were nearly done Core IPFIX protocol documents completed in 2006, (probably) to be published as RFCs in 2007. Working group continuing to dene extensions to and applications of the protocol.
Bidirectional ow export Redundancy reduction for export efciency Flow storage and File-based interoperability MIB and XML-based conguration for IPFIX devices etc
The IPFIX protocol has no direct support for single-record export of bidirectional ows (biows). This extension allows reversal of any element within the Information Model for biow export. To be published as an RFC this year.
October 15, 2007 NANOG 41 - Albuquerque 8
Reducing Redundancy
Technique for bandwidth-saving information export
Separates the export of ow records such that attributes common to several ow records are sent only once. Links common ow properties to specic properties with a unique identier.
NANOG 41 - Albuquerque
Flow Storage
Many analysis tools interoperate not via direct communication, but via le exchange.
exchange available via a variety of transport methods (HTTP, FTP, SSH+SCP, SMTP+MIME, etc., etc.) les support a variety of useful operations (compression, encryption, etc.) les are a natural unit of grouping related ow data (e.g. a single security incident or query result).
NANOG 41 - Albuquerque
11
IPFIX Files
An IPFIX le is any serialized stream of IPFIX Messages.
Alternately, a le transport for IPFIX.
NANOG 41 - Albuquerque
14
ntop
web-based trafc measurement application acts as IPFIX collecting process available from http://www.ntop.org/
October 15, 2007 NANOG 41 - Albuquerque 15
FIN
IPFIX is an emerging standard for exible ow export, representation, and storage.
For those who want to follow the progress: http://tools.ietf.org/wg/ipx - WG tools page http://www.ietf.org/html.charters/ipx-charter.html
NANOG 41 - Albuquerque
16
Questions?
ask now or later: bht@cert.org elisa.boschi@hitachi-eu.com
NANOG 41 - Albuquerque
17