Service provider edge or core routers are not the best traffic-limiting platforms. While they definitely have the capabilities to perform numerous Quality of Service (QoS) actions, complex QoS actions reduce their performance.
P2P traffic is harder to limit than any other traffic because the P2P programs usually use a number of cloaking mechanisms to evade detection (and traffic limits). Furthermore, the P2P programs use a large number of parallel TCP sessions, making the usual QoS algorithms that relied on the cooperative behavior of end users mostly useless.
The best way to deal with P2P traffic is to limit the traffic per user (meaning per IP address). Most high-speed routers don't have that functionality; you have to use dedicated platforms (for example, Cisco's Service Control Engine) to implement per-user traffic shaping or policing.
Dig Deeper on Telecom Routing and Switching
Related Q&A from Ivan Pepelnjak
Telecom networking expert Ivan Pepelnjak details the similarities and differences between Infrastructure as a Service (IaaS) and multi-tenant ... Continue Reading
Telecom networking expert Ivan Pepelnjak breaks down the speed, bandwidth and security benefits of moving from a simple cable Internet connection to ... Continue Reading
IP expert Ivan Pepelnjak breaks down the true headaches you'll face when building an IPv6-enabled service provider core, and what you can do to ease ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.