This is a call to all the great companies to date that have implemented IPFIX. It is clear that IPFIX is the next generation protocol for to be included with most network monitoring solutions and for this reason, I'd like this companies and those considering IPFIX to include support for RFC 5610 or some similar sort of technology. Without support for this RFC, deciphering new elements is nearly impossible. The situation IPFIX collector vendors are facing is similar to trying to look decipher traps or browse OIDs without a MIB file.
Below is a template being received from a device where the IPFIX collector does not know how to interpret a field. Notice the 2nd column below '13745_33071' :
- 13745 = plixer
- 33071 = unique element ID
Notice that the value above shows up as a square. This is because our IPFIX collector didn't know how to decode this data which resulted in our front end trying to display the binary information. Without a RFC 5610 template, we have to tell another developer how to decode the value which allows the front end to display it like this:

I really don't want to see the efforts of Boschi, Trammell, Hitachi Europe, Mark, Fraunhofer IFAM, Zseby and Fraunhofer FOKUS go in vain. Please contact us if your company would like to consider implementing RFC 5610. We have experience with the release of IPFIXify which is a gateway for translating syslogs, event logs and SNMP traps to IPFIX.








Leave a comment