Slashdot Mirror


Cisco Opposes Net Neutrality

angry tapir writes: All bits running over the Internet are not equal and should not be treated that way by broadband providers, despite net neutrality advocates' calls for traffic neutral regulations, Cisco Systems has said. Some Web-based applications, including rapidly growing video services, home health monitoring and public safety apps, will demand priority access to the network, while others, like most Web browsing and email, may live with slight delays, said Jeff Campbell, Cisco's vice president for government and community relations. "Different bits do matter differently. We need to ensure that we have a system that allows this to occur."

64 of 337 comments (clear)

  1. Somewhere in my mind... by symbolset · · Score: 5, Insightful

    Somehow in my mind Cisco and Oracle are the same company. Maybe I have reached my dotage, but when I see one mentioned the other may as well be there too. They are like Satan had identical twins separated at birth.

    --
    Help stamp out iliturcy.
    1. Re:Somewhere in my mind... by symbolset · · Score: 5, Funny

      They should merge and call the result Oracicle.

      --
      Help stamp out iliturcy.
    2. Re:Somewhere in my mind... by symbolset · · Score: 3, Funny

      Such a dumb setup.

      Not as dumb as paying more per gigabyte of RAM on your Cisco server for the privilege of paying more per gigabyte of RAM and Gigabit of network bandwidth on your Oracle software so you can pay extra for the ports on your Cisco network switch. With mandatory support contracts all 'round.

      --
      Help stamp out iliturcy.
    3. Re:Somewhere in my mind... by L4t3r4lu5 · · Score: 5, Informative

      Cisco are a networking company, right? They should know the difference between net neutrality and QoS.

      The crux of net neutrality is bits from different providers being given the same priority. Nobody is arguing that we can afford to drop some Bittorrent packets in exchange for VOIP / video streaming. What the cable companies want to do, however, is prioritise their video streaming, for example, over someone elses. That is the net neutrality issue.

      --
      Finally had enough. Come see us over at https://soylentnews.org/
    4. Re:Somewhere in my mind... by Anonymous Coward · · Score: 5, Funny

      Oral-co + Cicko = Oralsicko.

      Anyway, Jeff Campbell is a fucking idiot. Who the fuck is he to say that someone's stupid YouTube video experience is more important than someone else's business email? He's astroturfing because his company sells networking equipment that handles filtering which is only needed in a world without net neutrality.

    5. Re:Somewhere in my mind... by Monoman · · Score: 5, Insightful

      Cisco also knows where their income comes from.

      --
      Keep the Classic Slashdot.
    6. Re:Somewhere in my mind... by sirlark · · Score: 3, Funny

      I would have gone with Orafisco myself

    7. Re:Somewhere in my mind... by jedidiah · · Score: 2

      Once again. It's all fine so long as everyone's packets of a particular type are all treated the same.

      Prioritizing VOIP over my Netflix packets is not and has never been the issue.

      Cable companies are masquerading as ISPs. They want to sabotage the competition in ways we would not tolerate if they were a phone company.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    8. Re:Somewhere in my mind... by therealkevinkretz · · Score: 4, Insightful

      Because several-second delays in video packets will make it unwatchable (or require a lot of buffering) and a drop of a significant percentage of a phone call's UDP will make it unusable, but the effects of neither of those will be noticed by the recipient of that business email.

      To me there's a significant difference between "Net Neutrality" and QOS.

    9. Re:Somewhere in my mind... by L4t3r4lu5 · · Score: 4, Informative

      According to the CW article, Cisco didn't mention NN at all. Grant Gross, the IDG journo, made that connection himself. Cisco don't use the term "net neutrality" at all in their press release

      Shoddy journalism to blame for this, I'm afraid.

      --
      Finally had enough. Come see us over at https://soylentnews.org/
    10. Re:Somewhere in my mind... by LordLimecat · · Score: 5, Insightful

      Here's the difference, in two sentences:

      QoS is about prioritizing and filtering traffic based on type .
      Net Neutrality is about prioritizing and filtering traffic based on source .

      You could possibly say that QoS is layer 4-7 (port, application, transport) while Net Neutrality is layer 3 (address).

    11. Re:Somewhere in my mind... by Bengie · · Score: 2

      Routers have buffers measured in milliseconds. Everything else gets dropped. Even at a slow 10gb rate, 1 seconds of buffering is over 1GB of memory. Once you start getting into the terabit ranges, the bandwidth coming off those links is faster than the L1 cache on your 5ghz OC'd Intel CPU. You couldn't buffer that to memory if you wanted to.

      The points of congestion are typically the hardest to QoS. Once you start getting into the 400gb+ link speeds, you can't do real time QoS anymore. Enabling QoS slows you down to ~150gb/s. I assume it'll be much worse at terabit speeds. When you're talking about moving one bit every 1/1000th of a nanosecond, you don't have time to QoS. Eventually we'll be doing photonic routing. It will be interesting trying to "buffer" photons.

      We're already reaching the point of physics where the only way to route data is first-in-first-out. Anything else is nearly impossible or comes at a huge performance hit.

    12. Re:Somewhere in my mind... by Bengie · · Score: 2

      Not China anymore.

    13. Re:Somewhere in my mind... by LordLimecat · · Score: 2

      Wrong.

      QoS isnt about bandwidth, its about queues and latency.

    14. Re:Somewhere in my mind... by LordLimecat · · Score: 3, Insightful

      To be blunt, you dont know what you are talking about.

      Video traffic isnt generally like voice, and doesnt need to be prioritized. It is NOT latency sensitive; it can be buffered. It would be classified as "bulk", unless it were part of a teleconference (in which case it would share several of the below characteristics, like being UDP).

      Voice traffic can come from any number of sources; whether it is Skype, or GoToMeeting, or WebEx, or a privately run Jabber server, it will share a number of characteristics:
        * The traffic needs to arrive quickly, and reliably, or not at all. If a voice packet takes longer than ~100ms to arrive, it might as well be dropped and just cause a slight blip.
        * It will almost always be UDP, because TCP is only useful for re-transmits; a missing packet in a webpage means the page doesnt render, whereas a missing packet in voice just causes a minor blip.
        * Latency will kill a connection. 500ms of additional latency means each side will perceive a 1 second delay in responses. That is completely unworkable, and means that theres a pretty hard cap on the amount of latency that is allowable. Bulk traffic does not have this problem; a 0.5 second delay just means a 0.5 second delay.

      QoS is about types of traffic that cannot fulfill their function if they are not reliably delivered; it is generally used for protocols that require fast response times. It also generally will have no perceivable impact on "everyone else".

  2. I prefer by fredprado · · Score: 5, Insightful

    I prefer my bits non optimized than someone else deciding how they should be "optimized" for me. Thank you!

    1. Re:I prefer by tepples · · Score: 2, Interesting

      I don't think a lot of people would agree with you. People don't want 3-second beats inserted into their video calls.

    2. Re:I prefer by NoKaOi · · Score: 2

      All your bits are belong to Comcast.

    3. Re:I prefer by fredprado · · Score: 4, Insightful

      Sure, but they don't have 3 second latency now and they won't have it ever if the ISPs invest the necessary amount of money in infrastructure. Japan and Korea ISPs do...

      I would rather prefer to open the market to anyone who wants to provide the service without unnecessary restrictions as government concessions. Failing that I can be satisfied with legislation that forces the providers to offer a service of reasonable quality to the user as a condition to their concessions.

    4. Re:I prefer by jargonburn · · Score: 5, Insightful

      I thought the point wasn't that some bits should/shouldn't be prioritized, but rather that SOURCES shouldn't be prioritized. I'm fine with VoIP traffic being prioritized.
      I would take issue with, say, my ISP's VoIP application working fine while delays are introduced to Skype traffic. Prioritizing certain types of traffic make sense and can be provider-agnostic; prioritizing specific companies/sources, however, is chock-full of problems.

    5. Re:I prefer by fredprado · · Score: 2, Insightful

      Realistically you can't have one without the other, and either way it should not be their decision what should be prioritized, they are selling the band, you should be able to use it as you wish and give priority to whatever you feel that deserves it.

    6. Re:I prefer by NoKaOi · · Score: 4, Insightful

      I'm not sure that I like having my web pages load slowly so that somebody else can watch Keeping Up With The Kardashians jitter-free.

      And without net neutrality, those web pages will load even slower unless they are coming from somebody who has given your ISP extortion money (in addition to the money you're already giving them each month) to not slow them down.

    7. Re: I prefer by bemymonkey · · Score: 3, Informative

      This! Cisco doesn't actually oppose net neutrality, just the abolishment of QoS prioritization... but who the hell wanted to get rid of that anyway?

    8. Re:I prefer by skids · · Score: 5, Interesting

      It's a giant sticky mess. Many advocates for net neutrality have only a vague idea of how things work so their proposals are vague. Many with the experience to produce more detailed proposals have ulterior motives.

      Anyway, if you assume honoring protocol priorities is OK, then you end up with abusive situations where an ISP that runs video protocol 1 can sink traffic from a competitor based on the fact that they use video protocol 2. Add to that that protocols can be patented, and you'd end up with an incentive to create and patent stupid protocols just to do exactly that.

      Also there are services whose availability would benefit the customer/public/economy that involve prioritizing packets between privately administered device networks, and not by protocol, and defining the difference between those services and unfair competitive practices leads us down a road to byzantinism.

      Really we need to get to a point where end-users can send ToS bits into the network and have them honored as long as they are below a fair usage level for ToS packets, and a certain percent of the network is kept free for best effort, allowing the consumer some level of live control. Before we even do that, though, we need to just move towards "ISPs and other providers must make X% of all built capacity available at a (possibly tariffed) basic rate for public best effort use" and apply that principle across all areas of bandwidth, pps processing power, and -- the toughest sell but very important -- CDN capacity. The cash flow through CDNs really needs to be further regulated to eliminate the perverse incentive of making money off congested pipes on the back end. The restriction on sales of prioritized services in the other 100-X% part of the pipe would provide appropriate incentive for expansion of the entire pipe, benefiting the basic rate users not just the premium arrangements. The X could be adjusted by policy changes until the sweet spot is found or as the ecosystem changes.

      Now if the above was TLDR, a solid proposal would be 100x more complicated.

    9. Re:I prefer by wardred · · Score: 2

      Video and "internet radio" probably doesn't need "jitter free" downloads since, once you have a small buffer, it doesn't matter if it comes in relatively small spits and furts. I.P. calls, teleconferencing, videoconferencing, gaming, and anything that is truly sensitive to latency; however, should have priority. (Gaming is so particular to the game that ISPs wouldn't regulate this, if anybody did, it would be the individual.) Even in big corporate networks at least their phones generally get a lot of attention paid to them so your calls don't sound like you're out in the boonies on a cell phone with 1/2 a bar of reception. Your web pages probably wouldn't download noticeably slower to allow better phone traffic anyway. Certainly that 5G - 150G game download wouldn't matter if it arrived 5 seconds later if it means clearer calls. If web pages are loading noticeably slowly, even with certain services prioritized over others, it's probably for the same reason they're loading slowly without the prioritization: a poorly designed page waiting for that congested banner add to load before displaying the rest of their content. Or a massive number of plugins on a Wordpress page. Or a huge flash only page, etc.

    10. Re:I prefer by Darinbob · · Score: 4, Insightful

      Ya, this argument feels like an end run to provide an argument for Quality of Service in an attempt to discredit net neutrality, when those are different things.

    11. Re:I prefer by riverat1 · · Score: 2

      This is exactly what I came here to say. Net neutrality doesn't mean giving every kind of packet equal priority but giving every source equal priority.

    12. Re:I prefer by L4t3r4lu5 · · Score: 5, Insightful

      I absolutely want my traffic optimised. Your Bittorrent traffic can wait, whereas my VOIP call cannot.

      That, however, is a quality of service issue. I'm very happy for their to be QoS on my connection. However, I don't want your Verizon StreamTV or whatever service getting priority over my Netflix service. That is a net neutrality issue.

      We should not dilute the issue by confusing the two, or even discussing the two together. They are not the same thing.

      --
      Finally had enough. Come see us over at https://soylentnews.org/
    13. Re:I prefer by L4t3r4lu5 · · Score: 2

      How fast can you read your web page?

      There would be no appreciable difference in render time of your website should QoS be implemented correctly; We're talking about introducing milliseconds of delay while a few HTTP packets are dropped in favour of RTP, because RTP is latency-sensitive and HTTP isn't. Your page will still get to you, you will not miss out on anything, your experience will not suffer.

      Besides, this isn't about competing with web page rendering. This is about two streaming services competing, and the one owned by the cable company receiving priority. I've had to explain this three times so far on this story; How are so many people getting this confused?! Net Neutrality != Quality of Service.

      --
      Finally had enough. Come see us over at https://soylentnews.org/
    14. Re: I prefer by Jason+Levine · · Score: 2

      Nobody, but the ISPs buy a lot of Cisco gear so Cisco wants to side with them. Plus, if the ISPs want to build a "Usain Bolt" lane and a "Usain Bolted To An Anchor" lane, they'll need some shiny, new networking gear to implement it. Cue Cisco's executives getting cartoon dollar signs in their eyes.

      --
      My sci-fi novel, Ghost Thief, is now available from Amazon.com.
  3. Of course by NoKaOi · · Score: 3, Insightful

    This means Comcast & TWC will be purchasing more network equipment from Cisco. They won't upgrade infrastructure to deliver better service, but they'll happily buy equipment that prioritizes traffic (slows down traffic coming from non-paying sources) for the purpose of double dipping by charging both you and Netflix/Amazon/Google/etc.

    1. Re:Of course by Anonymous Coward · · Score: 2, Insightful

      Don't be ridiculous. Every network hardware supplier has QoS for their customers. What Cisco describes here, makes sense: some protocols are more urgent than others.

      What does not make sense is crap like Comcast is pulling: "Oh, these guys using HTTP didn't pay me more, but the other guys using HTTP did -- guess I'll have to employ some mafia tactics!"

      Please don't mix these two cases up...

  4. its a shame... by johnsnails · · Score: 5, Insightful

    Its a shame they don't have a vested interest in hardware capable of making such a thing possible.

  5. What About Electricity? by Bob9113 · · Score: 5, Insightful

    Some Web-based applications, including rapidly growing video services, home health monitoring and public safety apps, will demand priority access to the network,

    Do health monitoring devices get priority access to electricity? Does the electric company get to decide which devices will be shut down first? Can they shut down your devices before they shut down your neighbor's, because you bought Sony instead of Samsung? Would it be good for the electric company to be allowed to negotiate priority access to electricity with the appliance manufacturers?

    Net neutrality is about protecting the more important free market -- the free market in information -- by requiring the carriers to compete only on price and overall performance of their network.

    1. Re:What About Electricity? by negge · · Score: 2

      Does the electric company get to decide which devices will be shut down first?

      When one of the nuclear reactors in Finland had to be powered down unexpectedly about a year ago the grid operators call the biggest electricity consumers and tell them that they have to power down some of their machinery ("You'll have to cut your consumption by 40 MW, right now") so that the rest of the country can keep functioning.

    2. Re:What About Electricity? by havana9 · · Score: 3, Informative

      Does the electric company get to decide which devices will be shut down first? Can they shut down your devices before they shut down your neighbor's, because ?

      Actually yes. For industrial uses there are there are different categories of avaliability: high availability, standard and interruptible. An interruprible contract means that the electic company could disconnect the transformer serving your factory if the power demand is too high. Conversely high availability contracts will be disconnected last: normally they have also ne transformaer in stand by in the case the main one fails. By the way if yuo have a 100 kW contract you'll get more power than a 10 kW contract...

  6. This is absolutely correct by williamyf · · Score: 4, Insightful

    The internet had, since IPv4, provisions for exactly this, and whole careers have been built by this. It goes by different names, Type of Services, QoS, Traffic Engineering. IPv6 has also provisions for this, so did ATM in its time. MPLS has a HUUUUGE component of this...

    Having said that:

    Video on Demand traffic from, say comcast, should have the same priority as video on Demand traffic from youtube or netflix (or some future cash strapped start-up).
    Videoconferencing traffic from skype should have the same priority as videoconferencing trafffic from google+ o Cisco (or some future cash strapped start-up).
    Web traffic from yahoo should have the same (slighty lower) priority as the web traffic from "mom & pop web server".

    You get the drift, not because some big company is willing to pay more, or the ISP wants to double dip you can play with the priorities.

    And THAT is net neutrality for y'all!
     

    --
    *** Suerte a todos y Feliz dia!
    1. Re:This is absolutely correct by WaffleMonster · · Score: 2

      The internet had, since IPv4, provisions for

      Only small 'i' internets.

      exactly this, and whole careers have been built by this. It goes by different names, Type of Services, QoS, Traffic Engineering. IPv6 has also provisions for this, so did ATM in its time. MPLS has a HUUUUGE component of this...

      By all means prioritize intra-domain traffic within an organization. This makes sense and is widely deployed as you point out.

      None of this has ever worked inter-domain on a big "I" Internet of untrustworthy users with competing interests.

      Any and all traffic markings will be instantly gamed RFC3514 style reducing to classification based entirely on ownership (shady deals between mega content and mega ISPs) rather than actual need/merit.

  7. This is NOT a net neutrality issue by Rosco+P.+Coltrane · · Score: 5, Insightful

    Net neutrality is the idea that data from any provider (rich or poor, powerful company or a single guy, corrupt or honest) is treated the same way on the network.

    Cisco's comment concerns the prioritization of data depending on its type. I see nothing wrong with that.

    --
    "A door is what a dog is perpetually on the wrong side of" - Ogden Nash
  8. Unfortunately, we have a problem... by fuzzyfuzzyfungus · · Score: 5, Insightful

    Architecturally, Cisco's point has merit (aside from being purely an excuse to sell higher-margin fancy-shaping hardware, rather than brutally commodified really-fast-switching hardware). Some applications are more latency sensitive than others.

    However, there's a serious complication that Cisco is either ignoring or doesn't have any reason to care about: the mechanisms for doling out 'priority access to the network' and 'slight delays' are more or less target agnostic. There is nothing magic about hypothetical VOIP-911, Granny Accelerometer, or whatnot that makes it easy to identify them as "justified" prioritization and leave everything else alone.

    If you have the system set up to promote and demote traffic based on type, origin, destination, (or any similar set of parameters sufficient to plausibly identify 'important' traffic, rather than just basic TCP congestion behavior), you can promote and demote whatever you feel like writing rulesets for. Given that the last-mile is pretty much buttoned up by a cozy oligopoly of incumbent telco and cable outfits, does anybody seriously expect the shaping to stop at making sure those 'public safety apps' get the message out in time, rather than paying lip service to ensuring that 911 calls go through and then moving on to the actually profitable business of chopping the internet up and attempting to reach optimum price discrimination and suppress competition?

    So, barring major changes in the competitive landscape, or some sort of regulation-indistinguishable-from-magic, agreeing with Cisco on architectural grounds;but still rejecting the idea on the balance, is a perfectly cogent position(you can argue that it isn't correct; but it's not contradictory): Yes, traffic prioritization will allow better performance of latency sensitive applications (if they are in fact prioritized) all else being equal. However, once you have the architecture in place for that, the economic incentives to go nuts with it are absurdly compelling. By comparison, 'just grow your way out of it' isn't architecturally elegant; but it provides a nice, aligned, incentive for ISPs to build out and people who want more performance to buy fatter pipes, rather than for ISPs to let the infrastructure rot and focus on squeezing every penny out of every user.

  9. Re:At my own peril by rtb61 · · Score: 3, Insightful

    Always read the fine print, in this case pay attention to way he says. Slight delay, now what does that really mean. Like email, is the slight delay a reference to postal services, or the electronic transfer of data, so milli seconds or minutes to complete.

    I pay for bandwidth, I expect that bandwidth to be usable, what I do with that bandwidth as long as it is within the law is up to me not the providers choice. I do not accept the ISP monitoring, controlling and censoring my. I do not accept the ISP crippling my choices of content suppliers in preference for their own. I do not accept my ISP to purposefully crippling the services of companies who do not contract with them in preference for those that do.

    It is obvious laws are required to protect the provision of services to ensure anti-competitive monopolistic tactics can not be used to artificially inflate profit margins.

    --
    Chaos - everything, everywhere, everywhen
  10. I prefer by gronofer · · Score: 4, Funny

    I'm not sure that I like having my web pages load slowly so that somebody else can watch Keeping Up With The Kardashians jitter-free.

  11. Well. . . by Anonymous Coward · · Score: 4, Insightful

    If you're doing anything as critical as home-based life support system monitoring and you're literally trusting your life to your ISP, then you're already well past the point of screwed.

  12. Cisco and Self-interest by Jack9 · · Score: 3, Insightful

    Wait, Cisco wants to support a new network paradigm that would result in a market for new hardware, worldwide? This is America where lobbying new product lines into existence, is routine.

    --

    Often wrong but never in doubt.
    I am Jack9.
    Everyone knows me.
  13. Density Myth. . . by wardred · · Score: 4, Interesting

    Except that even where U.S. city/suburb densities are as high or higher than said small country, internet access still sucks. This probably accounts for %60-%80 of the U.S. population. (Maybe not E. Asia, but certainly a good chunk of Europe.)

    Other things small countries can do that may be more difficult for the U.S. to do:
    1 - Have a true national plan for rolling out internet, rather than Country, State, County, Municipality, Neighborhood, and Individual plans. (Individuals in this case being people who object, maybe with some merit, to unsightly telco boxes on or near their property and do something about it, messing up the plan, either requiring the telco box to be moved or for them to go through city planners and/or court to get permission to place the box on the person's property.)
    2 - Dictate how the internet is going to be rolled out. Similar to 1, but not quite the same. Possibly have "country wide" municipal broadband, with individual providers riding off of state owned infrastructure.
    3 - Not deal with U.S. Corporate lobbyists. It seems we have world class corporate lobbying. Our lobbyists are so strong that they can convince us the price we're paying for Internet, Health Care, Cell Service, pick your overpriced product is as good or better than the rest of the world, that the reduced service we often receive along with the high prices is really better than the rest of the world, and that all the multiple ways we pay our ISPs to improve their infrastructure, through taxes, directly through our internet bills, through "back door deals" like Netflix paying both their ISP and the end user's ISP to deliver content will actually improve much of anything. (The latter seems to have, but only because that one entertainment provider has paid to improve that one service on that one monolithic ISP.)
    4 - Laying down new infrastructure rather than dealing with a hodgepodge of existing infrastructure. This one is actually pretty important. Especially since some of that old infrastructure - land lines - are something ISPs/telcos are still federally mandated to maintain. . . unless this has recently changed. Also, they may have more uniform wiring, and access to that wiring, in their larger buildings.

    1. Re:Density Myth. . . by symbolset · · Score: 5, Interesting
      Population density is why we don't have gigabit fiber to tiny little rural towns in the middle of nowhere like Ephrata, WA (pop 7000). No, wait. They have had gigabit fiber to the home since 2001. Back when that cost a metric boatload of money. And yet the network made an embarassingly large profit they had to pay back to their customers because they are a nonprofit. How is that even possible?

      It is possible because your density story is a lie. It is made up. There is no truth to it. If Ephrata, and even smaller towns in that county, can have gigabit at a reasonable price 14 years ago then we all can now. The tech is 100x cheaper now. There is no excuse for not fibering up the whole country.

      --
      Help stamp out iliturcy.
    2. Re:Density Myth. . . by Jason+Levine · · Score: 4, Informative

      I'd also add my example. I live in a decent sized city. We're no New York City, by far, but we're not suburbs either. When Verizon was laying their FIOS cables, they went to the suburbs and bypassed the city. The population density of the city was higher, but they avoided us entirely. Of course, the reason wasn't population density, but income. Suburbs are more likely to have middle class/high middle class/affluent individuals who can pay Verizon more money. Cities might have poorer individuals and they might not be able to afford FIOS. So they made a business decision and avoided the poorer locations.

      The problem with this is that, in the 21st century, knowledge of how to use the Internet is crucial to many jobs. Use of the Internet can help lift a person up from poverty. Sticking the poor regions with slower speeds is exasperating the income separation.

      Of course, Verizon is free to build where they like and avoid poorer areas. It's not like they took billions of taxpayer money to wire states, reneged on their promises, and kept the money, right? (Oh, wait. They did.)

      --
      My sci-fi novel, Ghost Thief, is now available from Amazon.com.
    3. Re:Density Myth. . . by wardred · · Score: 2

      Similar to water, sewer, and electrical lines wired internet cabling is a "natural monopoly". There are 3 different cabling standards to bring wired internet to the home. Twisted pair for POTs, which may also bring some form of DSL, cable, and fiber. I'm not certain that I want ISPs to own the wiring for these services, but that ship has largely sailed. In a properly networked setup once you have access to the single twisted pair, coax, or fiber, you'd have your choice of ISP. I could be mistaken, but I believe that's how it's done where countries have competition. I don't believe there's a crazy quilt of redundant wiring to each residence. TWX's statement about ISPs and cable companies needing to be common carrier, and needing to allow competition on their wires, since our municipalities don't own them, is spot on.

      As far as the downsides to letting everybody run their own wiring?
      1 - For telephone poles having a crowded and unsafe tangle of cables.
      2 - For underground, it's even worse. I don't want my streets dug up every time there is an ISP startup.
      A - It's just a nightmare when street maintenance is already a strained and underfunded beast in many U.S. cities.
      B - If the ISP goes out of business, there's the potential for a bunch of "dark last mile wiring". This doesn't benefit anybody.
      C - We have enough trouble keeping track of the wiring that's currently out there without adding a bunch more.
      D - As you trench more, at some point it'll be impossible to put in new wiring without cutting somebody else's connection, even if temporarily.
      E - It's wasteful. In the case of copper which is already in pretty high demand, it's highly wasteful to run redundant connections.

      Ideally I'd like to see municipalities owning the last mile and leasing the wiring to any ISP that wants a piece of it. Alas, the private companies own the wiring, and our regulations are so wishy washy that with the exception of phone service, it typically means that the ISP that owns the wiring is the only one that gets to use it. With proper legislation to treat any ISP similar to a telco common carrier, it needn't be that way and smaller entities could ride on the same wiring as the big incumbents.

  14. Oh God by symbolset · · Score: 2

    Now they are both going to sue me for the slander of associating each with the other. They'll probably both win too, and have to sue each other over fractions of my soul. But the judge will be in on it and award both the same soul three times each.

    --
    Help stamp out iliturcy.
  15. QOS != NetNutrality by tonywestonuk · · Score: 2

    nuff said.

  16. Surprised by WaffleMonster · · Score: 2

    Who would have thought Cisco prefers the world attempt to deploy foolish and hopelessly complex inter-domain prioritization schemes requiring $$$$$$ Cisco solutions to implement?

  17. TWC is already screwing customers using fast lanes by msoftsucks · · Score: 3

    I have a customer who is currently with Time Warner Cable and their speeds have gone down significantly over the last 6 months. They used to be able to access web sites with split-second response times. Now the average is at least 5 seconds before a web page comes up. I have placed numerous support calls, they come out and run their own hosted speed test which claims they are meeting speeds. They then leave saying there is nothing wrong, yet browsing is almost unusable. I believe they have QoS turned on so that their own speed tests run fine, yet the overall browsing experience is significantly worse. If they are playing these games now, what will happen when net-neutrality is eventually abolished by these big souless corporations?

    --
    Quit playing Monopoly with Bill.
    Linux - of the people, by the people, and for the people.
  18. Abuse of the internet architecture by dutchwhizzman · · Score: 3, Insightful

    This is abusing the internet architecture. The whole idea is that services don't rely on speed and delivery, but work with the network architecture to ensure that whatever service they provide is able te deal with delays. This means that if ISPs want happy customers and companies want their internet product to work properly, they have to ensure that there's enough room on the entire network to deliver those services adequately.

    Now some company that sells equipment that can prioritize packets of certain services so network providers can get away with saturating the data links more starts flipping the principle of the internet around. Sorry, no, that's not the *internet* you are talking about Cisco. That's a private network in which some company gets to say what they think is important.

    Every individual company owning a network will have different priorities. Try connecting thousands of private networks with different priorities and different technologies to achieve those and make that work. This is what Cisco is proposing we do to the internet and it will be a pain to try it and chances that it will ever work are close to zero. Part of why the internet works is because we have a global goal of just routing packets without prejudice. Don't mess with that, it will end in tears, unhappy customers and only a few rich C level executives at router producing companies.

    --
    I was promised a flying car. Where is my flying car?
  19. Re:In that case by TWX · · Score: 5, Insightful

    Don't confuse quality-of-service in general for anti-net-neutrality in particular.

    Cisco is technically correct in that real-time or near-real-time services need higher priority than data transfers that don't need real-time synchronization or timing. If I'm watching a live TV program I need the network traffic carrying that program to get to me correctly, in real time, or watching the program live doesn't work. If I'm surfing the Internet to use web forums, mild reductions in performance won't really impact my experience. I do not have a problem with an ISP attempting to shape its traffic to give priority to content requiring real-time capability.

    Opposing "Net Neutrality" seems to be opposite-ville to me. I see the goal of ending net neutrality being for ISPs to force payment from large real-time content providers in order to keep that content flowing with enough priority to make watching it practical. Even though the customer is already paying for enough bandwidth to receive everything if the ISP doesn't intentionally break it.

    --
    Do not look into laser with remaining eye.
  20. Stuff and nonsense. by kheldan · · Score: 2

    If there's sufficient bandwidth for everyone then net neutrality won't be a problem now will it? Either someone light a fire under these goddamn ISPs and make them stop stalling on upgrading shit, or force them to stop lying to their customers about how much bandwidth they're actually paying for. Also Cisco is a shit company and can go fuck themselves.

    --
    Are YOU using the TOOL, or is the TOOL using YOU? Think about it!
  21. Title is a bit sensationalist... by Drakonblayde · · Score: 5, Interesting

    Of course a network vendor is going to point out that some packets needs preferential treatment over others. It's something they've worked to engineer into their product lines because their customers demand the capability to do so. For an ISP, 911 VoIP packets are a much higher priority than World of Warcraft packets.

    Too many folks are caught up in the idea that prioritization is bad. There's a difference between between the philosophy of Network Neutrality and the operational reality of packet prioritization.

    Saying Cisco opposes Net Neutrality just because they're pointing out some simple truths on how network operate today is like saying Glock supports terrorism just because they make guns.

    Of course, if the title weren't sensational, no one would probably read it.

    It saddens me that Slashdot seems to have decided that they need to resort to the same tactics as the National Enquirer

    1. Re:Title is a bit sensationalist... by WaffleMonster · · Score: 2

      Too many folks are caught up in the idea that prioritization is bad. There's a difference between between the philosophy of Network Neutrality and the operational reality of packet prioritization.

      There is a difference between intra-domain and inter-domain prioritization and the operational futility of the latter.

      It saddens me that Slashdot seems to have decided that they need to resort to the same tactics as the National Enquirer

      In this case they are warranted. Cisco's statements cannot possibly be applied to the real world without picking winners and losers.

  22. Re:In that case by Anonymous Coward · · Score: 4, Insightful

    Agreed.

    QoS = Different types of application/service, with different latency/bandwidth/reliability requirements, being treated differently = Good.

    Net Neutrality = Similar applications/services, with identical latency/bandwidth/reliability requirements, being treated equally = Good.

    In my view, they're not mutually exclusive.

  23. Bad headline by Captain_Chaos · · Score: 2

    The headline is up to Slashdot's usual standards I see. They are talking about quality-of-service, which is a common and uncontroversial measure to prioritise traffic which needs low latencies over traffic for which that is less important. They aren't talking about prioritising Comcast's video streams over Netflix' video streams! This has nothing to do with "opposing net neutrality", it's just bad, sensationalistic reporting.

  24. Its all about sales by Loki_666 · · Score: 2

    Cisco simply see a big profit to be made by selling new kit that is specially designed to be able to determine which traffic is from where and priorotize (a bit like QoS but for providers rather than traffic type).

    They don't give a shit about the whole neutrality debate really... just more sales. Who cares who or what it harms? Sales comes first!

  25. Re:In that case by Monoman · · Score: 2

    QoS is a standard and there seem to be some industry best practices to handle things like VoIP and video. Net Neutrality is not based on any standards and merely appears to be a legal way to extort money.

    --
    Keep the Classic Slashdot.
  26. Conspiracy-theory rubbish ... by golodh · · Score: 4, Insightful
    @Symbolset

    Before you lose yourself in flights of fancy, consider this. Cisco sells network gear, i.e. the stuff you need to implement multiple tiers of traffic. Only the more advanced, expensive, and high-margin gear will do that of course. Think: deep-packet inspection.

    And you were actually wondering why Cisco is in favour of an Internet that needs advanced kit and against an Internet that doesn't need special gear to implement multiple tiers?

    A bit slow at arithmetic, are you?.

  27. Re:In that case by Anonymous Coward · · Score: 2, Insightful

    And now you know how high frequency trading works.

  28. inter-subscriber priority by Chirs · · Score: 2

    Why should your videoconferencing packets get priority over my netflix stream?

    If we've both paid for equivalent plans, then we should have equal use of the network.

    The only truly fair option is for ISPs to weight traffic between subscribers based on their plans, without looking at traffic type. Then within the traffic belonging to a single subscriber they could (if approved by the subscriber) do QoS based on traffic type.