IPFIX Information Model<draft-ipfix-info-03.txt>

Paul Callato, Jeff Meyer, Juergen Quittek59th IETF meeting, IPFIX session

IETF 59 IPFIX INFO MODEL 2

Changes Since Version -02

• several editorial changes• changed the XML representation of the

information model replaced representation of IPFIX protocol fields added representation of field template added representation of abstract data types

• modified list of (abstract) data types• modified list of fields

IETF 59 IPFIX INFO MODEL 3

XML Representation

infomodel

schema.xsd

infomodel.xml

infomodel

I-D.xml

infomodel

I-D.txt

translate with XSLTscripts and include

include in appendices

translate with XSLT scripts validate

section 2

section 3

secti

on 4

IETF 59 IPFIX INFO MODEL 4

Issue 1: Datatypes

• Concrete XML data types were replaced by abstract IPFIX data types

• What is the useful set in order to be prepared for future extensions?

• version -02: byte, unsignedByte short, unsignedShort int, unsignedInt long, unsignedLong float, double hexBinary string boolean dateTime, ipdr:dateTimeMsecm ipdr:dateTimeUsec, ipfix:dateTimeNsec ipdr:ipV4Addr, ipdr:ipV6Addr ipdr:UUID

• version -03: octet unsigned16 unsigned32 unsigned64 float32 octetArray string boolean dateTimeSeconds dataTimeMicroSeconds ipv4Address,ipv6Addres

s

IETF 59 IPFIX INFO MODEL 5

Issue 2: Field IDs

• Current version is compatible to NFv9 field IDs

• Allocating field IDs will be delegated to IANA

• There are some field Ids that we do not want to re-use. These will be labeled "reserved for NFv9"

• The list of currently unused NFv9 fields needs to be checked for candidates to include in IPFIX

IETF 59 IPFIX INFO MODEL 6

NFv9 Field Issues

• NFv9 has separate counters for incoming octets/packets and outgoing octets/packets not nicely applicable to probes unclear observation point Shall we just use one of them for IPFIX? Shall we define new fiels without "in" or "out" as

prefix?• NFv9 has separated values for IPv4 and IPv6

network mask length shall we adopt this?

• NFv9 has smaplingInterval and samplingAlgorithm PSAMP showed that this is not sufficient

IETF 59 IPFIX INFO MODEL 7

List of not yet used NFv9 fields

• engineType (38), engineID (39)• ipv4SrcPrefix (44), ipv4DestPrefix (45)• MPLSTopLabel (46), MPLSTopLabelIPaddress (47)

• destClassOfService (55)• srcMACAddr (56), destMACAddress (57)• srcVLAN (58), dstVLAN (59)• direction (61) : {ingressFlow|egreeFlow}• IPv6OptionHeaders (74)• MPLSlable1-10 (70-78)• mplsTopLabelIPv6Addr