On Sun, 24 Jun 2007, Robert Blayzor wrote:
Chris L. Morrow wrote:
Then there's the interesting: "How do you classify 'to be dropped' traffic?" Simon suggests nntp or BitTorrent could be put into a lower class queue, I'm curious as to how you'd classify traffic which is port-agile such as BitTorrent though. In theory that sounds like a grand plan, in practice it isn't simple...
It really depends on the network. Not all networks are the same. Case in point we have some network that carries a lot of video. Obviously we want all the channels to get from point A to point B, but there are services that really can be classed as "best effort"; like the VOD
I think I didn't state my question clearly :( I get that if you know the endpoints, or one side, or the protocol or the ports involved QOS isn't 'hard'. What my question really was getting at was Simon brought up the normal QOS stuckee 'BitTorrent' (substitute any other p2p sharing application which most folks claim is 'all illegal content anyway'). I was wondering how QOS was supposed to work on that traffic, given it's port/protocol agililty. I suppose if you had some special traffic you could qos up that and down everything else but that wasn't quite what Simon was getting at I don't think. -Chris