Quote:
|
Originally Posted by Undertoad
If you would have been able to comprehend my post, you would have understood that this was exactly my point. I would send both VoIP packets and ICMP packets, and then compare the two; since as I noted, a hardware or routing problem would affect both. If only the VoIP packets were affected, I would know the source of the problem, right? Ya follow buddy?
|
And what would you know? Somehow the VoIP packets are sometimes taking different routes? Or that some switches sometimes handle VoIP packets differently (in time, routing, etc) from ICMP packets? And if you do see service degradation, then so what? How do you explain why the condition does not exist one hour later as service degradation is applied intermittently. Maybe larger VoIP packets are suffering more from S/N problems? That particular characteristic being how that switch deals with higher S/N problems when internet traffic is heavier. How would you know? What are you going to do - sue? Meanwhile the consumer would assume you (Skype) software is to blame. The technical study has too many variables. The consumer does not care. He just goes with someone who provides better VoIP - such as Comcast.
In short, even if you do identify symptoms in a location where packet skewing exists, well, its legal. And you still have not proven that it is packet skewing - or other internet problems. IOW so what? You have identified where service is inferior. Now what does Skype do? Cry? It's all legal.