Quote:
Originally Posted by Carlos Carboni
Hardly any with Packetcable 1.5 and top notch wifi... (Zoom Model Model 5402)
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.
A standard voice call requires 64kbps of symmetrical bandwidth; PacketCable's signalling ensures this gets nailed up as unsolicited grant, so it takes precedence over everything else running on the DOCSIS downstream and upstream channels. Can't really do that with the QoS on the home router, and wasteful to have that service flow sitting there all the time, so it has to be added via dynamic signalling.
That's one example. Another is video streams: with PacketCable a video service flow can be added on demand which uses PBE / Priority Best Effort on the cable network, thus taking precedence over the broadband Best Effort service flows for access to bandwidth and ensuring that video is smooth even on highly utilised service groups.
PacketCable is there to solve specific problems, which it does.
Lastly I'd imagine you'd be looking for the newer PacketCable 2.0 standard if looking for the latest and greatest. Most recent standards published 2014 where 1.5 was originally published in 2009 with extensions in 2012.
PacketCable is just software though, so support can be added progressively. eMTA functionality not so much.