The main point of contention appears to be that the EFF is defining "server" as any process that opens listening sockets, while ISPs use definitions based more on traffic patterns and uptime requirements.
Can I run a server from my home?
Our Terms of Service prohibit running a server. However,
use of applications such as multi-player gaming,
video-conferencing, home security and others which may
include server capabilities but are being used for legal
and non-commercial purposes are acceptable and encouraged.
Exactly. The EFF and the TOS terms are clearly using different jargon.
The problem, though, is that the EFF's definition is the "correct" one at least as commonly understood by technical people. The license is using the term to connote things that it doesn't define, and that's a frustrating place to be if you as a user want to know if your gadget is permitted.
The linked FAQ is a great clarification, and Google should be commended for adding it (they may be alone among broadband ISPs in having language like this, I don't know). But they really need to get that clarity into the license itself.
"Unless you have a written agreement with Google Fiber permitting you do so, you should not host any type of server using your Google Fiber connection ..."
So, basically: "You can't run a server, unless it's a server-ish thing that most people use, in which case we encourage it." Really wish there was a clearer distinction they could make.
Maybe they're drawing a clear line at "legal and non-commercial"?
I said it before, and I'll say it again, but any attempt to differentiate packets based on use rather than quantity is a violation of network neutrality. All packets are created equally, why should any ISP care why my packets exist?
Network Neutrality is typically defined in terms of traffic sources, not use. It's both expected and encouraged that ISPs will differentiate between different types of packets based on what they contain.
For example, it would be obviously bad for Comcast to place Netflix at the bottom of the QOS stack, but perfectly reasonable to do so with Bittorrent.
You are using a definition of net neutrality that differs from everyone else's. In the interest of conversational clarity, you ought to pick a different term.
All residential ISPs sell more aggregate consumer capacity than total peering capacity, because very few users require the full use of their connection at all times. This permits their users' bills to be much lower, a tradeoff that is obviously beneficial to almost everyone.
Overprovisioning absolutely requires the use of QOS and throttling. If my neighbor decides to torrent a hundred terabytes of ATLAS data, that should (ideally) not cause any of my DNS or RTP packets to be dropped.
"Net neutrality (also network neutrality or Internet neutrality) is the principle that Internet service providers and governments should treat all data on the Internet equally, not discriminating or charging differentially by user, content, site, platform, application, type of attached equipment, and modes of communication."[0]
My understanding is that net neutrality is when the ISP does not prioritize/throttle/block traffic based on sender or recipient.
This definition permits traffic shaping based on content, such as dropping bittorrent packets to preserve dns/rtp latency on a link shared between customers.
Frankly the dancing around the term "server" stinks. It can be resolved quite easily by stipulating that one cannot operate a commercial business out of a home internet connection.
Or are we talking about something a little more fine-tuned: Using the listening ports of a computer on the network to facilitate the selling of goods/services for commercial reasons.
Is a business license the limiting factor? We need clearer terms before any argument has merit here.
> Using the listening ports of a computer on the network to facilitate the selling of goods/services for commercial reasons.
Sounds about right. We can take it a step further and explicitly state that a customer is prohibited from living on the avails of their residential internet connection, rather than simply "facilitating the selling of goods/services for commercial reasons."
The main point of contention appears to be that the EFF is defining "server" as any process that opens listening sockets, while ISPs use definitions based more on traffic patterns and uptime requirements.
Google's FAQ addresses this issue. From https://fiber.google.com/help/ :
See also: http://arstechnica.com/information-technology/2013/07/google...