Thread: Broadband Hardware Trial 2015
View Single Post
Old 20-07-2015, 14:46   #69
qasdfdsaq
cf.mega poster
 
Join Date: Aug 2004
Posts: 11,207
qasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronze
qasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronze
Re: Broadband Hardware Trial 2015
Quote:
Originally Posted by Ignitionnet View Post
Quote:
Originally Posted by Carlos Carboni View Post
What is the dis-advantage of having your router doing the QoS over packetCable QoS?

what is the advantage for the user and/or the cable company?
I'm actually really struggling on how to answer this.

I think you misunderstand the function of PacketCable if you think simple QoS configured on a router is a substitute. The primary driver is being able to dynamically add and remove service flows so that these can run without affecting the 'best effort' broadband service flow.
I'd put it simply down to this: PacketCable is implemented as part of the cable stack and is therefore able to address the intricacies of DOCSIS and HFC signalling and scheduling.

QoS on a router isn't.
qasdfdsaq is offline   Reply With Quote