Re: "malicious traffic identification"
This (from the article) makes me suspect telco involvement:
This section looks at various use-cases: service differentiation (which, of course, raises the debate about network neutrality); traffic monitoring for resource allocation based on subscriber policy (ie, “premium” versus “best effort” services – neutrality again); malicious traffic identification (which isn’t a bad idea); service-based billing (which could, again, tie back to the neutrality question)…
Note the bold items, aren't they about extracting additional revenue?? This action smells worse than the after effects of Red Tide on fish.
 Depending on whose determination of malicious traffic you want to use, malicious traffic could mean VOIP or SIP traffic in a country where the government controls the 'exit points', and wants to set up any, and all kinds of barriers to circumvent it getting its piece of the action.
 Red Tide is something that you wish never comes to your area if you live near the coast. The stench of hundreds of thousands of dead, rotting fish, well, lets say, I hope you are not ready to sit down for a meal. http://en.wikipedia.org/wiki/Red_tide