So it is not able to really ascertain things like application layer information, but it's still quite powerful. It's still rooted in an analysis of things like source and destination ports and IP protocol IDs. So you have to understand that it does have some shortcomings. Now it's not as powerful as things like Network-Based Application Recognition, or NBAR. If you're trying to get a sense of the traffic flow and a new rollout and you're trying to understand, "Hey, what protocols go across this?" You could use NetFlow to get a high-level perspective. So we're measuring utilization, resources, and you could also do this to do planning. This is an industry-standard technology, okay. If you're a service provider billing customers based on usage, they're going to get it from NetFlow. So we are tallying things, like source IPs, destination IPs, what protocols, and we can use this, in fact, service providers can use this to do billing. NetFlow is a great way to do accounting of traffic inside of your network. Simple Network Management Protocol, or SNMP, gathering statistics, syslog, gathering those informational or emergency messages or warning messages that our device is telling us that, "Hey I have a problem or this has come up, this has gone down." Well what about traffic flow? How could we gather statistics on the traffic flow so we can figure out who is using this particular type of traffic, so this particular application, how can we monitor that? How can we see who is over utilizing the network? We can implement a feature such as NetFlow to do that. So far we've been looking at ways to monitor our device specifically.