1 / 7

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

IPFIX Information Model <draft-ipfix-info-03.txt>. Paul Callato, Jeff Meyer, Juergen Quittek 59th IETF meeting, IPFIX session. Changes Since Version -02. several editorial changes changed the XML representation of the information model replaced representation of IPFIX protocol fields

kirsi
Download Presentation

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

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IPFIX Information Model<draft-ipfix-info-03.txt> Paul Callato, Jeff Meyer, Juergen Quittek 59th IETF meeting, IPFIX session

  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 2

  3. XML Representation translate with XSLT scripts and include section 2 info model schema .xsd info model I-D .xml section 3 translate with XSLT scripts validate info model .xml section 4 info model I-D .txt include in appendices 3

  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,ipv6Address 4

  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 5

  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 6

  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 7

More Related