Slashdot Mirror


Vonage's CEO Says VoIP Blocking Is 'Censorship'

Avantare writes "CEO of leading VoIP provider says port blocking of VoIP traffic is one potential small step toward an unwanted future of IP-based censorship. According to Vonage Holdings Corp. CEO Jeffrey Citron, intentional blocking of Voice over IP traffic is more than just a competitive dirty trick -- it's an act of censorship against free speech. In an exclusive interview here Tuesday [March 1], Vonage's chief executive said the issue of the company's recent incident of having some VoIP traffic blocked reaches beyond the market for IP-based voice communications and into the realm of free speech -- and as such, should be protected by the courts, the FCC, or by new telecom regulation that ensures free and open access over the Internet."

21 of 386 comments (clear)

  1. There *could* be a way around this. by Slartibartfast · · Score: 5, Interesting

    I was thinking about issues along these exact same lines, and a way to get arround the inherent issue -- an issue that occurs in many other places -- came to me: expand the functionality of DNS. As it is, when you perform a DNS query, you are given an IP address, a hostname, or an MX record. Would it be that much more difficult to extend it a little bit, and have an optional "service 'FOO' can be found at port 12345"? Initially, clients would still expect to find their services at traditional ports (eg., http at port 80), but anyone who truly cared could distribute modified client software, such as Firefox (or Vonage phones) with the additional functionality. This would make port blocking ridiculous, because, for example, Vonage could have a VoIP system on port 80 -- making ISPs have to start block hosts to disable VoIP, and that would truly be flagrant censorship, and disallowed. Yes, there are some complications, but I think it's something that should be considered.

    1. Re:There *could* be a way around this. by msblack · · Score: 4, Interesting

      With only 65,534 ports available, I don't think we want to start allocating *too* many of them to individual applications beyond the well-known port numbers below 1024. Use whatever ports you like. However, if your activity is disruptive to the ISP's ability to provide a minimal level of service to all their customers--not just you--they have every right to place limitiations. Free reign over the Internet is not an inherent right. Free speech doesn't even come close to applying here as it is a private network...boo hoo hoo.

      --
      signature pending slashdot approval
    2. Re:There *could* be a way around this. by Anonymous Coward · · Score: 1, Interesting

      Port 443 (https) would be better. It's used for secure data anyway.

    3. Re:There *could* be a way around this. by cbrocious · · Score: 3, Interesting

      What you've described is precisely how multicast DNS (mDNS... branded Rendezvous (now Bonjour) by Apple) does service broadcasting and browsing. You have a name for the service (foobar.raop_.apple.local. or whatever) and txt records to go along with the service (and an optional service name like 'My webserver')

      --
      Disconnect and self-destruct, one bullet at a time.
    4. Re:There *could* be a way around this. by TilJ · · Score: 2, Interesting

      Not too mentiun tcpmux (check your ientd.conf man page). DNS SVC records are a related idea.

      --
      "The purpose of argument is to change the nature of truth." -- Bene Gesserit Precept
    5. Re:There *could* be a way around this. by werelnon · · Score: 2, Interesting

      Not if Cringely is correct and telcos start to use COS (Class of Service) to prioritize chosen traffic above all others (like their own voip traffic).

  2. I don't know... by winstonmeister · · Score: 3, Interesting

    if I'd go so far as to call it cenorship, per se, but it certainly is a scummy thing to do. Broadband companies shouldn't cherry-pick what ports they'll use, especially if they want to keep their "common carrier" status. Isn't that the defense they like to use against releasing P2P customer information to the MPAA? Or is that more of a /.-ism than something said by the companies themselves?

    1. Re:I don't know... by Richard_at_work · · Score: 2, Interesting

      Phone companies can block what numbers you can call or receive calls from, and that hasnt affected thier common carrier status. As such, ISPs dont have common carrier status - that privilege needs to be bestowed upon an industry by a Judge I think, you dont automatically get it just because you handle other peoples traffic.

    2. Re:I don't know... by MBCook · · Score: 2, Interesting
      As far as I know (and I have basically no knowledge here) there are no cases on this. If there are cases, they are probably quite old. That said, if a phone company (let us assume SWB) just started blocking people from calling random number (or Sprint PCS/Cingular/NexTel stores to be more like the issue at hand) I think it would be clear that unless they could make an argument it protected the consumer (i.e. those three companies were know fraud schemes, which they aren't despite what you may think of their prices/service ;), they would get in BIG trouble. While this may not technically be censorship (I believe it's not "censorship" unless the Government is doing it), it's scummy (as others have pointed out) and the courts will end up intervening on the public's behalf (whether that is due to a Vonage lawsuit, a class action case, or a government probe started by some agency).

      Cute trick guys. Now pay up for messing with your customers service. Let's not forget that phone companies block numbers because someone requested it, not because it messes with their business. If person A can't call person B that's because person A had the number blocked from that phone, person B had the number blocked from that phone, or a court ordered it so due to somee legal preceding (say a restraining order). That would be like someone calling up AOL and saying "Make it so my computer can't talk to Yahoo's computers anymore.", not AOL just saying "Sorry, Yahoo is off limits for (pathetic reasons X and Y)." as the ISP in this case is doing.

      PS: Not only that, they are (among other things) intefering with interstate commerce, breaching contract (I'd imagine), and any decent lawyer could probably think up about 20 more.

      --
      Comment forecast: Bits of genius surrounded by a sea of mediocrity.
  3. Stop whining Vonage by winkydink · · Score: 2, Interesting

    and get creative about masking your traffic. Sheesh.

    --

    "I'd rather be a lightning rod than a seismometer." -Ken Kesey

    1. Re:Stop whining Vonage by miu · · Score: 2, Interesting
      and get creative about masking your traffic. Sheesh.

      I may have missed the sarcasm of that post, but...

      That is a battle that Vonage cannot win, the ISP is the ultimate "man in the middle" of security literature. Suppose Vonage switched to SRV records - ISP looks for SRV requests for SIP services and redirects or fails them, or they could block RTP streams themselves (even encrypted ones) with characteristics other than those of the ISP, since the ISP is guaranteed to be privy to all communications they can observe or change *anything* the customer sends or receives. Ultimately an ISP with no competition could even make using competing VOIP providers a violation of the TOS.

      --

      [Set Cain on fire and steal his lute.]
  4. Congress isn't happy by moofdaddy · · Score: 5, Interesting

    I work in DC as a lobbyist for the VOIP industry and let me tell you that this is not somethign we are sitting idly by and letting go unnoticed. I have been making a lot of calls today to various senators and congress trying to get their support and it has not been too difficult at all. Many were outraged at the idea and asked what our recomendation was on what to do. At the moment we are drafting a bill and a number of senators (Biden, Lehey, Kennedy) have expressed interest in introducing it.

    The bottom line is that the telecoms have a strangle hold and they are not willing to let go but they have over stepped their boundries this time. Expect to see hearings announced soon.

    --
    Be better in bed. Wikiafterdark!
  5. At what level? by Jace+of+Fuse! · · Score: 3, Interesting

    Blocking at what level?

    Is it restricting free speech if a company blocks VoIP outside of their network?

    Is it restricting if one ISP decides to block it for all of their customers?

    In the first situation, it's not really any different than a company policy forbidding personal phone calls on company time.

    In the second situation, switch ISPs to someone mroe reasonable.

    I think before we can go around saying that blocking VoIP is denying free speech, we should look at each situation individually.

    And of course, when possible, vote with dollars.

    --

    "Everything you know is wrong. (And stupid.)"

    Moderation Totals: Wrong=2, Stupid=3, Total=5.
  6. Re:leave it to the market by Skye16 · · Score: 2, Interesting

    Ah, but if only the market were broad enough. My choices are either Cable, dial-up, or copying information to a disk and sending it through the mail. If only we all had the options you have :(

  7. freedom talk by Doc+Ruby · · Score: 4, Interesting

    I asked around some VoIP execs I know, and it seems like only Vonage is being blocked this way - though their packets are exactly the same as Vonage's (except for the to/from bits). I don't know about "censorship", but it's clearly unfair competition from telcos seeking to offer competing VoIP.

    --

    --
    make install -not war

  8. Hmmm... maybe I'll wait by ylikone · · Score: 3, Interesting
    I was thinking about cancelling my Bell telephone land line and just using my cable internet and vonage. I only have the options of bell sympatico ultra-high speed and rogers cable internet... if both of these services were to block voip ports then I would be left with no phone at all. We really need more high-speed broadband providers in this area (southern ontario, canada) if I will make the switch to vonage. Sure there are a lot of standard DSL choices, but I find them to be too slow for my needs.

    Also, just realized vonage doesn't support calling 911 in canada yet! WTF is up with that? I have kids and it is important to have them be able to pick up the phone and just dial 911 (as they have been taught at school, the media, etc...). Yet another factor to consider before I make the switch.

    --
    Meh.
  9. How is Vonage protecting free speech ... by jephthah · · Score: 1, Interesting

    when they charge $30-something a month?

  10. Bubble Packets, IPv6 by shapr · · Score: 2, Interesting

    First of all, bubble packets let you get around blocked incoming ports.
    Second of all, how is this different from disallowing any incoming or outgoing connections?

    Some ISPs don't allow any incoming connections, some don't allow port 25 outgoing.
    Blocking port 25 outgoing would be easy to fix, only block it for microsoft mailer agents. (try this on your spam filter).

    Why don't ISPs upgrade to IPv6 so users have the most useful technology available to them?
    ISPs don't upgrade to IPv6 because they maximize profit, not user services.

    As for IPv6 being the 'most useful', it would mean every user could have a public static IP, and run their own services.
    Every user could use true multicast (BitTorrent is fake multicast) meaning webcasts, online games, and many other applications would use a tiny fraction of the bandwidth they use now.

    --

    Shae Erisson - ScannedInAvian.com
  11. Re:Don't use those ISPs then... by Rude+Turnip · · Score: 2, Interesting

    Since Comcast is running a *government-granted* monopoly in my town, it is censorship. Same goes for Verizon.

  12. Re:Umm.... by LionMage · · Score: 3, Interesting
    It's the ISPs network. They can do whatever they want with it.

    Yes, but the more restrictive the ISP is, the less they look like a common carrier. You can't have your cake and eat it too -- and common carrier status confers all kinds of protections (legal and otherwise) that the ISP runs the risk of losing if it starts censoring specific kinds of traffic.
  13. Re:Internet Provider != Government by Fareq · · Score: 2, Interesting

    You would be correct, expcept that ISPs qualify as common carriers.

    This means that they get things like protection for bad stuff people do on their network in exchange for not being allowed to ask what people will do on their network...

    If they want to give up that protection (and have the ??IA sue *them* instead of end-users, they are welcome to do so -- then they would be legally allowed to restrict that sort of thing in [almost] any anti-competitive way they like.