Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
The Internet IT

Net Neutrality Never Really Existed? 157

dido writes "In his most recent column, Robert X. Cringely observes that network neutrality may have never really existed at all. It appears that some, perhaps all, of the major broadband ISPs have been implementing tiered service levels for a long time. From the article: 'What turns out to be the case is that some ISPs have all along given priorities to different packet types. What AT&T, Comcast and the others were trying to do was to find a way to be paid for priority access — priority access that had long existed but hadn't yet been converted into a revenue stream.'" Cringely comes to this conclusion after being unable to get a fax line working. His assumption that the (Vonage) line's failure to support faxing is due to Comcast packet prioritizing is not really supported or proved. But his main point about the longstanding existence of service tiering will come as no surprise to this community.
This discussion has been archived. No new comments can be posted.

Net Neutrality Never Really Existed?

Comments Filter:
  • by MadMidnightBomber ( 894759 ) on Friday April 13, 2007 @10:26AM (#18718097)

    Most transport streams that deliver audio use UDP - it doesn't matter if you lose a few packets here and there because the human hear hears a reasonably good approximation of the original sound. There's no point trying to redeliver packets that get lost, because they will be late anyway by the time you get them there. This scheme will just plain not work with digital data, fax or whatever, if you're losing bits of it here and there. I suppose you could re-implement a reliable TCP-like protocol on top of the unreliable transport stream, but it would be so much easier to take a scan or a photo and email it.

  • by Paulrothrock ( 685079 ) on Friday April 13, 2007 @10:29AM (#18718139) Homepage Journal

    P.S. Fax is obsolete. Scan and email.

    Tell that to my credit union or any of my insurers. Even though I have a scanner and can send them encrypted PDFs, they insist that I fax them various bits of information for "security purposes." This isn't much of a problem since my computer has a built-in fax modem, but why they don't accept encrypted PDFs is beyond me. It's just as secure as a fax.

  • Re:Nice Logic... (Score:4, Informative)

    by Brew Bird ( 59050 ) on Friday April 13, 2007 @10:31AM (#18718157)
    let me restate.

    For non-network important 'stuff', it's all pretty much best effort.

    Things that are important to the day to day opperation of the network (route updates, SNMP/Managment traffic) have to have priority over 'customer' traffic. But so what. That is such a tiny amount of bandwidth compared to the multi-meg service people get...

    A real question for vonage : Why dont you have a bandwidth tester on your network that your customers can hit? Better yet, something that produces latency and jitter stats?

    That would settle this whole argument once and for all. the closest I could find on their site was this:

    http://www.vonage.com/help.php?article=497&categor y=46&nav=102 [vonage.com]

    which is weak. It shows my 10M ethernet internet access with a D/L speed of 2.74M and and upload speed of 4.76 Mbs...

  • by jrumney ( 197329 ) on Friday April 13, 2007 @10:35AM (#18718201)

    VOIP uses lossy compression that is heavily tuned for voice. Of course it is going to be lousy for lossless data transmission. If you wound the baudrate down low enough (say 2400baud), you might have some success, but I wouldn't guarantee it.

  • by msauve ( 701917 ) on Friday April 13, 2007 @10:46AM (#18718357)
    other than G.711 (uncompressed PCM), voice codecs will not handle fax or modem calls. The standard method of handling fax calls over IP is T.38 [wikipedia.org].
  • by Anonymous Coward on Friday April 13, 2007 @10:48AM (#18718389)
    I know for a fact Broadwing now Level 3 Communications does service tagging. Our corporation bought a DS3 and were only to get single session rates of like 300K. We could fill up the entire 45Mb but it took a ridiculous number of sessions to do so. After much troubleshooting with them we found out our traffic was getting tagged as Bronze. They removed the tags and now we're smooth sailing with rates up to 1Mb per session. Still not the best but it is better. So just goes to show yes they are already tagging traffic.
  • Re:Nice Logic... (Score:3, Informative)

    by ironicsky ( 569792 ) on Friday April 13, 2007 @10:54AM (#18718485) Homepage Journal
    The problem is if they put a bandwidth tester on the website it is not going to make a difference. ISP's generally wont intefere with web traffic on port 80 or 443 or any other HTTP based protocol. But when you start using SIP protocol on Ports 5060, 5061, and in vonages case 10000-20000 the ISP and network providers degrade those services. So your bandwidth tester on the web will show you have a steller connection, especially on Comcast which has the PowerBoost for the first 10Mb of a file(15Mb on Speed Tier) you will show nice speeds which doesn't reflect your poor SIP protocol performance. Unfortunately there is no easy way to test a SIP connection speeds or performance.
  • by cfulmer ( 3166 ) on Friday April 13, 2007 @11:00AM (#18718551) Journal
    First of all, everybody should recognize that most Fax-over-IP use a different codec (typical T.38, if I recall) for encoding the fax signal. If you just plug your fax machine into a plain-old VoIP port, there's a good chance that your gateway will do some lossy audio compression that isn't noticable for speech, but destroys a fax signal. That's one of the reasons that Vonage sells fax as a separate type of line.

    Second, IIRC, the initial part of a fax call does some measurement and negotiation -- this is where the two endpoints determine how fast they'll communicate, exactly which protocol they'll use, what capabilities each other have and (most importantly here) test their connection, including round-trip time. But, this negotiation assumes a circuit-switched network, not a packet-switched network.

    One of the core things about IP is that the round-trip time can change. Normally, each side would put in a buffer to balance it out, but if the delay changes, the buffer may need to be increased. For people, that's not a big deal -- add an additional 10ms delay midway though a call, and we don't even notice. But, that increase will kill a fax machine.

    Think about what you're doing with fax: you are scanning an image, converting into data, then encoding that data as analog, which then gets re-encoded as data for transmission over IP. On the other end, just the reverse happens. Why not skip the extra steps by getting a scanner and emailing it? Or, subscribe to efax, which does it for you.

    But, since a lot of people still have fax machines, a better technological solution might be to have your gateway decode the fax signal to get to the underlying image data, and then just transmit THAT to the other end. This is approximately what the T.37 fax standard does (again, IIRC). Unfortunately, it's not particularly well supported anywhere yet.

  • Re:Nice Logic... (Score:4, Informative)

    by mikeisme77 ( 938209 ) on Friday April 13, 2007 @11:06AM (#18718633) Homepage Journal
    That's still a neutral network though as all the data packets have equal chance of reaching their destination. It would only be a problem if you were prioritizing your own VoIP service and/or penalizing data packets for Google Talk/Gizmo/Vonage voice data packets. Or in some other way prioritizing data packets from the Internet that effects all of your customers (not just those abusing your ToS).
  • What do I know? (Score:1, Informative)

    by Anonymous Coward on Friday April 13, 2007 @11:26AM (#18718931)
    All this stuff about compression and packet prioritixation is nice, but the fact is I've had Vonage for about 3 years now, along with Comcast -- and I've never had a problem sending or receiving dozens of faxes.
  • by The_Quinn ( 748261 ) on Friday April 13, 2007 @12:13PM (#18719609) Homepage

    The customer paid for the internet
    What do you mean that the customer 'paid for the internet'? What the customer paid for was access to a long chain of telecom equipment provided by businesses who engineered, deployed, and marketed their services.

    Tiered services are a part of many industries, including Customer Service, Shipping, Transportation (first class anyone?), and many others.

    Forcing businesses into government-mandated business models is wrong. It only stifles the creation of new business and innovation, while increasing the control of politicians over citizens lives.

  • by xoyoyo ( 949672 ) on Friday April 13, 2007 @12:15PM (#18719653)
    I should have done my Googling before I posted... turns out this ground has been covered extensively elsewhere and a> yes, Vonage's voice codec is reputedly so bad that faxes are known to have a problem with it but, b> you can sometimes get fax to work by switching you fax into the slowest most error-correcting mode it has available. It is almost exactly the same as TCP over a really lossy network. On a lossy network like narrowband wireless TCP goes into ultra pedantic error correction and fragments packets to atoms to ensure delivery. The end result is that at the application layer (say a Web browser on a phone) the service becomes effectively unusable: I suspect much the same is happening here.
  • Re:Nice Logic... (Score:3, Informative)

    by malfunct ( 120790 ) * on Friday April 13, 2007 @07:16PM (#18726331) Homepage
    If he didn't pay vonage for fax service the reason his fax does not work is that vonage filters out anything outside of human vocal frequency ranges and fax signalling is outside that range. This is done for compression reasons to save thier bandwidth and improve vocal call quality over lower bandwidth lines. Did the dude read the manual which says right in it that faxes and modems will not work on standard vonage lines?

    That said I have seen wierd things with vonage over verizn dsl such as my routes all going through dozens of hops for a route with high latency while vonage phone adapter was up and running and then nearly instantly getting low hop numbers and low latency when the vonage phone adapter got disconnected. It could have been coincidence but it was pretty reproducable over a period of a week which is why I didn't end up getting vonage.

And it should be the law: If you use the word `paradigm' without knowing what the dictionary says it means, you go to jail. No exceptions. -- David Jones

Working...