No announcement yet.

Are bandwith hogs a myth?

  • Filter
  • Time
  • Show
Clear All
new posts

  • Are bandwith hogs a myth?

    This is probably better off in the Value Added News thread, but I do not have permission to post there.

    ISP’s are limiting users that "use more than their fair share" of data. In doing so, they are limiting the freedom of the Internet. However, are power users really harming the experience of other users at all?

    Not very many people have questioned the ISP’s right to limit these users. The consensus has been that if these users are ruining it for everyone, then they should be banned. Do these users really limit access to the Internet to others though? Is the bandwith hog a myth?

    "TCP/IP is by definition an egalitarian protocol. Implemented well, it should result in an equal distribution of available bandwidth in the operator's network between end-users; so the concept of a bandwidth hog is by definition an impossibility. An end-user can download all his access line will sustain when the network is comparatively empty, but as soon as it fills up from other users' traffic, his own download (or upload) rate will diminish until it's no bigger than what anyone else gets."
    For those of you interested in networking, TCP/IP is a protocol suite. Although it involves TCP from the transport layer and IP from the Internet layer (or Network Layer in OSI model), it is commonly misrepresented as just pertaining to those two layers. It really refers to the entire TCP/IP model which includes the Link, Internet, Transport, and Application layers. Basically, it’s an alternative naming convention to the OSI model, just with a shitty, misleading name.

    To simplify it, it basically combines the OSI’s Application, Session and Presentation layers into an application layer and Physical and Data Link Layers into a Link layer. So compared to the OSI it would be something like this…

    Application layer: Examples... HTTP,FTP,IRC
    Transport layer. Examples… TCP, UDP (Yup you can use udp in TCP/IP…ug, I know)
    Internet. Examples… IP, ICMP
    Link. Examples… ARP, NDP

    Application Layer Examples... HTTP,FTP
    Presentation Layer Examples... MIME, XDR
    Session Layer Examples... NetBIOS, SAP
    Transport Layer Examples... TCP, UDP
    Network Layer Examples... IP, ICMP
    Data Link Layer Examples... ARP, NDP
    Physical Layer Examples... Ethernet, POTS, DSL, 802.11g

    So why would I bother going through that long explanation of networking? Well, you are all hackers and probably want to know. Also, I really wanted to separate in your minds the commonly misguided concept of the TCP/IP model and TCP or IP by themselves.

    Why? Well because people are on the net arguing asinine comments like "What about the users of Voice over IP? They use UDP instead of TCP. Wouldn’t that change everything?" Well, no it wouldn’t. This is because TCP doesn’t have to be used in TCP/IP.

    All in all, this is a wonderful article, which I highly suggest. I especially recommend it to us hackers that can be users of higher bandwidth than the average user.