How ISPs May Quietly Kill VoIP
ravenII writes "PBS's i'Cringley's informative piece gives an eye-opening look at the anticompetitive behavior of some ISPs who are showing up late to the VoIP game. This is not something that could be easily mandated, and the beauty of this approach is that they're not explicitly doing anything to the 3rd party service applications. They're just identifying and tagging their own services, which is within their rights."
didn't the FCC lay the smack down on some ISP for doing this? Verizon maybe?
If bad puns were like deli meat, this would be the wurst
This is a good example of where letter of the law and spirit of the law collide. The FCC lacks the expertise too adequetly monitor their charge. There needs to be another solution. Perhaps, more openness?
So the main point seems to be that there will be a preferential class of packets that will be guaranteed to have some level of service such that the packets arrive quickly and in order. The bad part is that all other traffic will remain at the same old unguaranteed service level.
Well, that's what we have now.
Face it, the reason people use VoIP is because it is cheap/free, not because it has superior QoS than POTS. Throw in compression and encryption and you're talking about some pretty serious degradation of service.
So, in summary, nothing to see here.
When our call service can't reach me in order to help the world's largest retailer (you figure it out), then we'll see what ISP gets what heated phone call from whom. Hint: it won't be me, rather someone at bit less friendly with a much bigger bat.
The argument he makes is that big providers will offer their own VoIP offerings, and will give their VoIP traffic precedence on their networks, in turn degrading service for all other traffic (and thus, competitor's VoIP traffic).
However, without realizing it, he also explains why it won't happen. He argues that currently, all traffic is routed using "best effort". His argument then sxtends that these large organizations will effectively restrict other VoIP traffic as they give priority to ther own. I don't see how this necesarilly holds, though.
Imagine a high bandwitch connection. A certain percentage of that bandwidth is the used to service the "preferred" VoIP traffic. This leaves the remainder of the bandwidth to be divided amoung the other traffic. For this to actually affect the competitor's VoIP traffic, the amount of preferred traffic must be large enough to use enough of the available bandwidth that the remainder is unable to service the remaining traffic effectively.
Thus, this practice would not have a significant effect until a large amount of the VoIP traffic is "preferred" traffic - which supposedly would be the goal of starting to do so in the first place.
The only effect that creating "preferred" traffic will have is to provide better service for that traffic. I think that the actual effect on other traffic (even competitor's VoIP), will remain small.
The propaganda that capitalism is the most powerful medium for innovation, falls on its face here.
Capitalism with sensible government regulation is indeed the best path to rapid innovation.
Uh oh... did I just say that?!!
--- Grow a pair, liberals... stop letting the Republicans bully you!
This isn't an issue that requires direct oversight.
It requires clear labeling of products so people know what they are buying.
One set of ISPs offers "Internet Service", by which they mean access to the web, and then a collection of other services that they will offer.
And there is nothing wrong with them offering that service. It is what many, perhaps most, customers want.
The problem is that it is not the "Internet Service" that others want, including most slashdot readers presumably. Which is basically unrestricted access to the Internet with at most a total bandwidth constraint (and protect-the-net restrictions like no forged packets).
If an ISP is clearly labeled as providing "Internet Access" then they could not violate their service guarantees to you to favor their own traffic. If you want to use Vonage, host a server, select your own email provider, or any of a number of things that "power users" find desirable you would look for an "Access Provider".
If you only have a vague idea of what the difference between VoIP and email is, then you probably want a "Service Provider" who will provide you with services and take responsibility for integrating them.
The key problem right now is the ISPs are bluffing at providing open access to the Internet. There is probably a strong case that stealing from the common pool of "best effort" capacity without explicit disclosure.
But the solution is not to restrict what business Service Providers go into, it's to make sure they clearly label what business they are in.
"And there are other dirty tricks available to broadband ISPs. Telecom New Zealand, for example, is reportedly planning to alter TCP packet interleaving to discourage VoIP. By bunching all voice packets in the first half of each second, half a second of dead air would be added to every conversation, changing latency in a way that would drive grandmothers everywhere back to their old phone companies."
Comment forecast: Bits of genius surrounded by a sea of mediocrity.
I actually engineer and sell Asterisk boxes to small businesses, providing VoIP inside the office, connecting to the pstn. Our device encrypts all voice traffic on the public internet (between offices, and from remote clients/road warriors).
This article is of course mostly just stupid. Creating a vlan or QoS policy for VoIP will not cause the rest of the traffic to be crappy, not unless at least 50% of their actual traffic is voice traffic and that would require a whole lot of phone calls. VoIP is not really a broadband service per se.. it only takes 64kbps, my dsl service gives me 1.5mbps down and 1mbps up... I'd have to have 10 simultaneous calls up to use 50% of my bandwidth on voice...
Even if this was the case, the ISPs can't let "all other traffic" suffer at the expense of voip, if their voip policies are being so generous to their voip traffic that other voip providers service suffers, guess what, internet traffic in general will be suffering, and people will certainly notice that and complain (Hey, my bittorrent is only downloading at 50Kpbs, it used to get at least 150Kbps... )
Anyway, the article is idiocy, and people who know VoIP know how to secure it, and yes, I would never make a VoIP call over the public net without encryption.
Because you don't have any money. And if you don't have any money, you don't have any control. Your only other recourse is to vote, but with the Iraqi election turnout higher than the American, that's a longshot at best.
Haida Manga
When our call service can't reach me in order to help the world's largest retailer (you figure it out), then we'll see what ISP gets what heated phone call from whom. Hint: it won't be me, rather someone at bit less friendly with a much bigger bat.
If you're using a home Cable or DSL Modem for a mission critical application like this then I think you have bigger issues to deal with (such as your ISPs TOS). Otherwise this probably isn't going to affect you a whole lot. I don't foresee this causing too much trouble on people with T1 and larger pipes supplying their connections...
The best way to think of it is really like a FIFO queue, or standing in line at the Post Office.
All packets that the ISP favors (their own VoIP packets) go first in line. All other packets have to fight for a spot in line. (Non-VoIP packets are treated the same as every other packet*).
Now, assuming that there's enough spots in the line for all of the packets, nothing is dropped. The ISPs VoIP packets go out first, giving them a slight advantage, but everything goes out. If there aren't enough spots, then some of the packets get dropped.
*In practice, this isn't quite true. There are also packet priorities built into the IP specification, and it is likely that VoIP packets are using these as well. Therefore, the line would really look like this:
1. ISP approved packets
2. Non-ISP approved packets with high priorities
3. Every other packet.
Once these packets leave the ISPs network, it's "catch as catch can" again, however, it is likely that the ISP voIP packets have IP priorities as high as, if not higher than the non-ISP VoIP packets, causing them to still have a slight edge.
-- Joe
If ISPs use QoS to give preferential treatment to their on VoIP services, they can only do so within their own network, as mentioned in the article. If best effort carriage under such conditions results in degrading all other VoIP traffic, then the whole scheme seems doomed to failure.
/jab
The special, high-quality calls promised you by ISPs engaging in this practice would revert to standard best effort calls the moment you reach out to touch someone who is using a different ISP. This scheme only supports high quality on something analogous to a local phone call.
I still say utilities should be government run and regulated. Let's see what's happened with deregulation:
Savings and Loan: Ugh, I don't even need to recap this one.
Phone Service; Payphone prices have doubled, my phone bills are now ridiculous and often miscalculated, and the bill has tripled.
Power: I live in California. 'Nuff said.
Things that every home needs I feel really should be government run, because companies are stupid. Yes, when you just give someone a company that they didn't build from the ground up and say "okay be creative" they screw it up 9 times outta 10. Especially when it's something that there is no negative recourse for. If I build a software company and own 50% of the stock, I'm not gonna try a hair-brained idea that might make billions, because I could lose everything. If someone gives me a company that say, provides people with phone service and I'm the ONLY company providing that to those people, I don't care if I bankrupt my company trying to make billions, because I know the government will just bail me out because people need phone service.
Deregulation sucks. The solution is that things which are critical to the nation's success with high upkeep costs and needed by 90%+ of the population should be government run.
What is government run:
DMV (travel/commerce)
DoT (Road building & maintaining)
USPS (communication/commerce)
Water/Gas (not sure about this one, correct me if I'm wrong)
What should be:
Basic local phone service
Fibre-Optic Internet/Cable
Cellular Phone Service/reception (why have 6 different towers beaming stuff through my body when we only need one? wasteful and pointless)
Capitalism shot itself in the foot with deregulation and (as above posters have pointed out) allowing monopolies to run unchecked.
Hold on... while I agree with your point, Cringely didn't talk about ISP's quashing traffic - he talked about them enabling class-of-service for their OWN voice traffic and leaving foreign voip traffic in the best-efforts network layer.
Engineering and maintaining a voice-quality COS on a network is expensive and difficult. Does anyone really believe that telcos or cablecos (having invested billions in building their networks) should hand this value over to Vonage etc for free? The reason Vonage can charge low prices is that it doesn't bear these costs - is it the ISP's job to bear these costs on their behalf?
If Vonage wants COS on these networks, it should approach them and offer to pay the engineering, hardware and operational costs. If not, they should continue to enjoy the service they've received for free to date.
My Internet connection is 5Mbps down, 800kbps up and capable of sustaining close to that for long periods of time. My Vonage phone works beautifully as long as I'm not hammering the network with Bittorrent. There's nothing to complain about here.
Maybe the dumbest Cringley column ever.
The last time I checked, I PAID my ISP EVERY MONTH for service!! THAT payment guarantees a certain level of service. If the cable company or other ISP deliberately degrades this service with malice, then I can SUE. I forsee BIG TIME class action suits over this... Unless of course, the FCC steps in (as they already did once for Vonage).