[c-nsp] Rate-limiting You Tube tarffic

[Peter Salanki]

If they would start doing i.e. encrypted web proxying, it would be  
impossible to see the final destination with a DPI solution ie.  
(Procera Networks PacketLogic or packeteer). If the proxying is not  
encrypted, atleast the Procera box can identify the final destination.

The normal solution to this is simply to disallow all proxying, and in  
the real world, there are very few people who has the know-how to  
proxy their Youtube traffic, so it usually is never a problem.

On Mar 8, 2008, at 8:27 AM, Mateusz Błaszczyk wrote:

> On 08/03/2008, Tassos Chatzithomaoglou <achatz at forthnet.gr> wrote:
>> You might want to look into NBAR and http classification, but  
>> depending on volume of traffic, a
>> traffic-shaper/service-control box might be more appropriate.
>>
>
> how would that work (NBAR/Packeteer) if people start using things like
> web proxying from privax network ?
>
> -- 
> -mat
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/