On 9/7/06, <b class="gmail_sendername"><a href="http://LES.NET">LES.NET</a> (1996) INC.</b> <<a href="mailto:voip@les.net">voip@les.net</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
One problem I see with the whole packet based QoS thing (if its real)...<br>Is that word will eventually get out that you can buy QoS and people will<br>use it for file sharing, gaming, and what not. It would effectively
<br>become useless once a lot of people start using it I would think.<br></blockquote></div><br>It all comes down to classification.<br><br>If only VoIP packets are given the priority, other apps and increased users won't cause problems.
<br><br>If all packets are given priority, it won't really help anyone, including the person buying the service.<br><br>How they classify, though, is the interesting thing. If they're trusting TOS set by the user they're open to the fraud you mention (though by limiting the amount of BW they're willing to PQ they're mitigating this). If they use IP addresses then they're limited to which gateways/companies the service is useful for (ie it might help Primus customers, but not
<a href="http://Les.net">Les.net</a> customers).<br><br>Also of near equal importance is where the QoS mechanisms are applied. If it's after the head end then local congestion within the node will affect voice quality. If it's before the head end, it's in the cable modem. This is the best way to do it, though the question arises "what classification can that little thing do?"
<br><br>QoS is end to end, and per hop. Anything less and you introduce jitter and the potential for loss.<br><br>Sean<br><br>-- <br>Sean Walberg <<a href="mailto:sean@ertw.com">sean@ertw.com</a>> <a href="http://ertw.com/">
http://ertw.com/</a>