Why Not Just Call It IPFIX?
Posted in IPFIX, NetFlow, Network Traffic Analysis, Network Traffic Monitor on May 6th, 2011 by NewsTraxI have a question for you marketing folks out there. Why are so many companies renaming their implementation of NetFlow or IPFIX? Here are some examples:
- NetStream is 3Com’s rename of NetFlow
- JFlow is Juniper’s rename of NetFlow
- AppFlow is the Citrix’s rename of IPFIX
- Nortel called it IPFIX when really it was NetFlow
Why not just call it what it is (i.e. NetFlow or IPFIX)? Why do these industry leaders have to rename it? Many of the same companies above support SNMP, why didn’t they rename that? They export syslogs, why didn’t they rename that? I think it is causing confusion in the industry. Here are some vendors that didn’t change their implementations:
For a free 30 day trial of Scrutinizer, Download Now!
Sign up for Advanced NetFlow Training™ coming to a city near you!


When we visit our local doctor, sometimes we don’t always agree with what they have to say. Sure, we didn’t go to medical school and we don’t have a fancy degree on our wall. But heck, it’s our body and once in a while we know something just isn’t right. So what do we do? We get a second opinion. The same concept is important in almost any part of life – even network management. Sometimes something just doesn’t seem right, and we need to get a second opinion before we blindly trust what our hardware and software is telling us.