SoylentNews is people
SoylentNews
Submitted via IRC for SoyCow1937
Net neutrality advocates are planning two days of protest in Washington DC this month as they fight off plans to defang regulations meant to protect an open internet.
A coalition of activists, consumer groups and writers are calling on supporters to attend the next meeting of the Federal Communications Commission on 26 September in DC. The next day, the protest will move to Capitol Hill, where people will meet legislators to express their concerns about an FCC proposal to rewrite the rules governing the internet.
The FCC has received 22 million comments on "Restoring Internet Freedom", the regulator's proposal to dismantle net neutrality rules put in place in 2015. Opponents argue the rule changes, proposed by the FCC's Republican chairman Ajit Pai, will pave the way for a tiered internet where internet service providers (ISPs) will be free to pick and choose winners online by giving higher speeds to those they favor, or those willing or able to pay more.
The regulator has yet to process the comments, and is reviewing its proposals before a vote expected later this year.
(Score: 3, Insightful) by NotSanguine on Thursday September 21 2017, @08:18AM (9 children)
In a nutshell, QOS (Quality Of Service [wikipedia.org] which has a very specific meaning in the context of TCP/IP networking) is setting priority based on network header options. Those options are read (or not) by each gateway (router) that a packet passes through, and if that device is configured to do so, will prioritize traffic marked for such treatment over other traffic. This is often used to prioritize VOIP and video traffic across enterprise networks. However, I am unaware of *any* IP transit providers that will honor such QOS tags from other entities. As such, even if you tag your traffic as high priority, other entities will just ignore those tags.
Another (and ubiquitous among network transit providers) mechanism for prioritization (which you mentioned) is traffic shaping [wikipedia.org]. This is used by most network providers. This mechanism (most often, but can take other forms too) looks at application (HTTP, p2p, VPN, SMTP, etc.) network flows and adjusts the bandwidth available to specific applications to fit the requirements of the entity performing the traffic shaping. This can be done by limiting the bandwidth (and increasing latency) for some protocols, or by silently dropping packets to match the traffic profile desired.
Again, there is no requirement that any ISP or transit provider shape network traffic in any particular way (that's true within a net neutrality regime, by the way). Many enterprises (as well as ISPs and transit providers) use devices which perform traffic shaping both internally, as well as at Internet connection points.
All of this is defined by each entity which controls the network infrastructure along the path of any network connection. No overarching design or traffic-shaping profile exists for the greater Internet. As an example, There are at least four (given current routing paths) network providers whose networks I need to traverse from the device on which I'm writing this comment to the soylentnews.org site.
Let's just say for the sake of argument that I wasn't writing a comment on Soylent, but playing an FPS game (as you mentioned earlier). Which network provider should I contact to have those packets prioritized? My ISP? That might work, assuming they care enough to want to make me happy.
The ISP of the end node where the FPS game server is? That is definitely a possibility, especially if the FPS is a commercial entity willing to pay their ISP for prioritization. That's great! Now we're all set to have high bandwidth and low latency, right?
Not so fast. There are two other network providers that my packets need to traverse in order to communicate with the FPS game server. I have no relationship with those network providers, nor does the host of the FPS game server. Those guys have their traffic shaping configured to support *their* needs and have no incentive to prioritize your packets.
That doesn't mean that prioritization at the ends won't help, it just illustrates the fact that the decentralized nature of the internet makes end-to-end prioritization highly problematic.
Which is why many enterprises purchase links from a single network provider (which traffic does *not* traverse the Internet) to provide VOIP and video services between across their various sites. That way, they can prioritize VOIP traffic or video conferences over backups, email, file transfers, etc.
I guess I gave more than a nutshell explanation, but I hope it gives you an idea as to how Internet-wide prioritization is impractical and unlikely.
Which leads us to Net Neutrality. Which specifically requires network providers *not* to implement specific QOS or traffic shaping, within their own networks, unless it's necessary for congestion control and/or network management.
Actually, at least in the U.S., you do. It is illegal for the Government (ala the First Amendment to the U.S. Constitution, although that's been spotty over the past couple hundred years). There is no law that forbids (at least none of which I am aware) private entities to censor whatever they want on their premises (or in this case, their pipes).
"No shirt. No shoes. No service."
"We reserve the right to refuse service to anyone, at the discretion of management."
Private entities are not bound by the strictures of the U.S. Constitution. Only the Federal government and (with the Supremacy clause and the 14th Amendment) the several states.
As I mentioned, the net neutrality doctrine disallows traffic shaping/QOS (inside the provider's network) for anything other than network congestion or management. If there is no more net neutrality, ISPs could do *exactly* as I suggested in my example.
What's more, what if I'm not a corporation streaming video or audio, but a human rights or political activist? Without net neutrality, ISPs who disagree with me could just refuse to pass my network traffic. And without net neutrality, ISPs could, with impunity. block your access to the websites of political candidates you support or make access so slow that the site is unusable. Alternatively, they could give preferential access to those you dislike.
Yes, it's about streaming media. But make no mistake, it's also about censorship.
Let's focus on those streaming services for a moment. I don't use Netflix. But if I did, I *pay* my ISP to deliver the bits I request within the limits of the bandwidth I pay for. Guess what? Netflix pays their ISP for the bandwidth they use too. So. Everyone is paying to have the bits they want transmitted to/from them. Why is that somehow unfair to ISPs?
And if ISPs can pick and choose who they accept bits from (or who you send bits to) for their customers, what's to stop them from deciding what is acceptable traffic on their network and what it isn't?
A few scenarios of what could happen without net neutrality:
ISP A's management are devout Catholics. They do not support abortion rights, so they block access to Planned Parenthood for their customers. Without net neutrality, that's a possibility.
ISP B's management are staunchly Republican (or Democratic). Without net neutrality, they could decide that they don't wish to support Democrats (or Republicans) and block (or throttle) access to the group they disfavor. Or they give priority access to the those from the group they favor.
So you see, whether it's streaming media that competes with an ISPs own content or sites (or even you) that don't comport with their ideas about what's proper, it's all the same principle. You many not care about streaming media, but there are much bigger issues at stake with net neutrality.
Allowing ISPs to pick and choose content to favor and disfavor, you open the door to exactly the censorship you say you oppose.
I don't pretend (okay, maybe I do :) ) to have all the answers, but despite what some folks may tell you, net neutrality is, in fact, a big deal.
No, no, you're not thinking; you're just being logical. --Niels Bohr
(Score: 0) by Anonymous Coward on Thursday September 21 2017, @02:24PM (8 children)
Not trying to beat a dead horse, but Netflix (at least in the past, using "net neutrality" to try to justify the behavior) did not pay for the data it was generating and sending into others' networks, but instead tried to abuse no-fee peering agreements (the backbone version of ISPs' "unlimited" Internet access). Here's an arstechnica article [arstechnica.com] that speaks to Netflix' schemes.
(Score: 2) by NotSanguine on Thursday September 21 2017, @03:03PM (7 children)
I've already gone through this several times. Netflix paid for their own bandwidth. Comcast is responsible for having enough bandwidth to support their customers.
The congestion was all on Comcast's side, because they did not have sufficient capacity to support its contractual obligations to their customers.
I addressed this in more detail here [soylentnews.org] and here [soylentnews.org].
Once more, Netflix pays for its bandwidth and Comcast pays for its bandwidth. One of the two didn't have enough bandwidth capacity to support their customers. That was Comcast.
I'd say the horse is beaten to a bloody pulp by now.
No, no, you're not thinking; you're just being logical. --Niels Bohr
(Score: 0) by Anonymous Coward on Thursday September 21 2017, @03:15PM (6 children)
No, Netflix didn't pay. Netflix tried to drive a dump truck up to a buffet table that explicitly disallowed taking food outside. Netflix tried to use unpaid peering agreements that explicitly demand a balance of incoming and outgoing traffic to dump their huge load of unbalanced traffic on.
Netflix did not pay for the data they sent.
(Score: 2) by NotSanguine on Thursday September 21 2017, @03:44PM (5 children)
Bullshit. You are either ignorant, misinformed or a shill for the ISPs.
No, no, you're not thinking; you're just being logical. --Niels Bohr
(Score: 0) by Anonymous Coward on Thursday September 21 2017, @04:22PM (4 children)
Nope. As repeatedly explained, as as you claim to grasp, no-fee peering agreements require that inbound and outbound traffic be roughly balanced. Netflix was demonstrably making use of no-fee peering agreements to send its traffic around the Internet.
If you disagree, then you are claiming that Netflix generates roughly the same incoming traffic to its own networks as it sends in streaming video out to others' networks. That idea is, in your own word, bullshit.
(Score: 2) by NotSanguine on Thursday September 21 2017, @06:19PM (3 children)
Netflix was not a party to those peering agreements, either ones between Level 3 and Comcast or Cogent and Comcast.
No, no, you're not thinking; you're just being logical. --Niels Bohr
(Score: 0) by Anonymous Coward on Thursday September 21 2017, @06:35PM (2 children)
True, but irrelevant, as Netflix paid Level 3 and Cogent for access to their no-fee peering agreements with Comcast, which Netflix' traffic load then violated. Comcast isn't the bad guy IN THIS CASE no matter which way you slice it. In my book, Level 3, Cogent, AND Netflix are all scumbags IN THIS CASE.
(Score: 2) by NotSanguine on Thursday September 21 2017, @07:23PM (1 child)
You're welcome to your opinion. I respectfully disagree.
Cogent and Level 3 *unbalanced* the peering agreement with Comcast. That it was traffic from Netflix is the part (from a legal standpoint) that's irrelevant. What's more, unbalanced perring isn't generally considered a *violation* of a peering agreement. It likely can annoy people and require a re-negotiation of the peering agreement, but traffic fluctuates significantly from month to month and discussions/changes are a normal part of managing the relationship between network peers.
I have no great love for any of these players, although I will say that having used Level 3, Cogent *and* Comcast as ISPs at the same time in various locations around the US both before, during, and after this debacle, Cogent had, hands down, the best service, up-time and customer support of the three. Comcast was so bad that we tried to replace them, but aside from (IIRC) XO (our primary ISP at that location), Comcast was the only local provider at that time who could provide the bandwidth we required at a reasonable cost.
My experience with these ISPs isn't really relevant to the Netflix debacle, but it does inform my understanding of the regard in which they hold their customers.
No, no, you're not thinking; you're just being logical. --Niels Bohr
(Score: 0) by Anonymous Coward on Thursday September 21 2017, @07:57PM
You're trying to pick at the smallest of nits in an attempt to avoid admitting that Comcast was the only rational actor among it, Netflix, Cogent, and Level 3.
Netflix viewers won't suddenly start sending Netflix streaming video next month. That traffic imbalance is huge and one way only.
That Comcast is also a giant ball of sucked scum is irrelevant to this specific situation. You hang a murderer for the murder, not because he smelled like poop and was a huge jerk.