3 ms·
If you phrase it as just "don't prioritize traffic", you've just broken most CDNs, as well as QoS that optimizes for latency/bandwidth to improve VoIP and simil
by JoshTriplett 10y ago
If you phrase it as just "don't prioritize traffic", you've just broken most CDNs, as well as QoS that optimizes for latency/bandwidth to improve VoIP and similar.
There's absolutely nothing wrong with, for instance, a content provider handing an ISP a box that sits on their network, mirrors/caches content, and serves it up to that ISP's customers. That helps the content provider, the ISP, and the ISP's customers. And I don't think the majority of "net neutrality" advocates want to break that.
When people talk about "net neutrality", the problems they have in mind tend to look like either an ISP extorting content providers to extract extra revenue, or an ISP giving their own first-party services an advantage by deliberately degrading third-party services. For instance, see Comcast and Netflix.
But even then, how do you draw a bright line between "deliberately degrading", "not giving an advantage to", and "not doing anything to address bandwidth problems when they arise"? (Comcast could claim the latter regarding Netflix, even though it seems obvious what it means when they don't arrange additional bandwidth on those saturated links.) What if the ISP provides the CDN infrastructure, rather than the content provider? What if the ISP contracts with a third-party CDN?
How would you suggest writing a regulation that doesn't break CDNs and similar, and that can tell the difference between "deliberately hurting" and "not helping"? How will that regulation adapt when people come up with new ideas to make the web faster?
(One angle I could imagine working: limiting the ability of one company or family of companies to run both an ISP and network services via that ISP. Still hard to write something robust, though.)
- AnthonyMouse 10y ago> There's absolutely nothing wrong with, for instance, a content provider handing an ISP a box that sits on their network, mirrors/caches content, and serves it up to that ISP's customers. That helps the content provider, the ISP, and the ISP's customers. And I don't think the majority of "net neutrality" advocates want to break that. ...until the ISP decides to charge a large amount of money for the ability to do that, and then under-provision their peering links so that there is no other way to have adequate performance. But there is a simple way to fix that. Require last mile ISPs to do free peering with anyone who has traffic for their last mile customers. If you bring traffic directly to their local central office, they have to take it and deliver it up to the speed that they've sold to their customers. Then they can offer all the CDN service they like, which people will use as long as they're charging market rates but decline and rely on peering (and install their CDN equipment across the street) if they try to charge monopoly prices.
- JoshTriplett 10y ago> ...until the ISP decides to charge a large amount of money for the ability to do that, and then under-provision their peering links so that there is no other way to have adequate performance. The latter is the primary problem here. > Require last mile ISPs to do free peering with anyone who has traffic for their last mile customers. What does "last mile ISP" mean here? DSL is no longer competitive, and most implementations of cable and fiber have no separation between "infrastructure provider" and "bandwidth provider". > If you bring traffic directly to their local central office, they have to take it and deliver it up to the speed that they've sold to their customers. What if their central office isn't connected to anyone else directly, because they get all their bandwidth and peering from one or more of the major backbones? Presumably they can say "go to those backbones", rather than having to start making peering arrangements with individual services. > but decline and rely on peering (and install their CDN equipment across the street) if they try to charge monopoly prices What if their central office doesn't have an "across the street" where you can put servers? Or what if they don't have a "central office", period?
- and0 10y agoI appreciate that you bring these questions up but your overall point seems to be "this is complicated and you can't provide logically / morally perfect arguments", which seems a little pointless. All legal matters are complicated, but we're a modern society full of a lot of bright people and "free market lol ISPs get to be highway robbers now" doesn't seem like the best we can do. I also disagree with the notion that inconveniencing some billionaires is less moral than hurting millions of consumers and setting a horrible precedent, so: regulate the shit out of them. If poor people can bootstrap huge medical bills then ISPs can handle some simple regulation. e: you didn't make that point about prioritizing rich over poor etc, that was directed more broadly at net neutrality opponents
- JoshTriplett 10y agoMy argument isn't "this is complicated so let's not"; it's "this is complicated and needs to be handled with care, not with a trivial attempted fix like 'dumb pipes only' the way people often seem to think". Together with a healthy dose of "regulation has historically failed to adapt to future technologies". And we don't really want regulations that privilege the tech we currently know over the future tech we don't; that tends to lead in unpleasant directions, including regulatory capture and blocking of future competitors. I think the fundamental problem here is that in most locations we don't have a market at all, free or otherwise. We're looking at all these restrictions in an effort to work around the fundamental problem of "people have little to no choice in ISPs". If you're going to have one ISP in an area and regulate its behavior heavily, you might as well just have the government run it. (Note: that's not a recommendation.) I'd be entirely in favor of solving the problem by saying "last-mile infrastructure (from customers all the way to the nearest meet-me room) is a public utility, all ISPs have to remain separate from the last-mile infrastructure". If the average customer had a choice of half a dozen or more ISPs, none of these problems would arise, because any ISP stupid enough to make services deliberately worse would get dropped in favor of ISPs that don't. ISPs could then compete on everything from services provided, customer service, neutrality, geek-friendliness, IPv6 availability, CDNs/mirrors, or anything else they think people want.
- and0 10y agoThanks for the robust answer. I think the CDN fix could be built right into net-neutrality laws: If you're going to support that functionality then also do it equally to any CDN that is also willing to foot the bill and/or meets certain criteria. For example, don't only let Netflix's smaller competitors let that box sit on your network. (No, this regulation wouldn't be burdensome either.) QoS is something I'm unfamiliar with when it comes to ISPs. I personally wouldn't be offended if some small % of bandwidth was dedicated to services consumers and businesses use that require priority, such as VoIP. As long as that applied to all VoIP services and apps equally, though I'm not sure how you would be able to tell.
- JoshTriplett 10y ago"Apply the same requirements to all services" certainly seems plausible, though that relates more to antitrust than net neutrality. Defining "willing to foot the bill and/or meets certain criteria" would still require very careful drafting to avoid breaking things, though.
- wtallis 10y ago> As long as that applied to all VoIP services and apps equally, though I'm not sure how you would be able to tell. The only fair way to do this is to use port numbers and protocols and endpoint IP addresses only for the purpose of telling which packets belong to which traffic flow or customer. For deciding which flows get priority, you should look only at the actual pattern of traffic: sparse low-rate flows should be assumed to be interactive, in the same manner that your operating system's CPU scheduler assumes that processes with intermittent load are more latency-sensitive than long-running sustained loads. To see how this kind of packet scheduling works in the real world, look at the fq_codel and cake queue disciplines in Linux. The former has become the default for many Linux distributions and is used by some of the more modern commercial wireless routers. This will have the side effect that my ssh session will get the same preferential treatment as your VoIP, unless I'm using it to tunnel rsync.
- amazon_not 10y ago> If you phrase it as just "don't prioritize traffic", you've just broken most CDNs, as well as QoS that optimizes for latency/bandwidth to improve VoIP and similar. This is simply incorrect. CDNs are not prioritized on any ISP network. CDNs work because they have a shorter route to the end user, not because they have a higher priority. ISPs should not and do not apply QoS in their core for VoIP or anything else when it's part of generic Internet traffic. It's the end users responsibility to QoS police VoIP or other traffic on their WAN interface. The ISP just shifts the bits. Not privatizing traffic does not break CDNs nor customer QoS. Neither of these things have anything to do with net neutrality. > But even then, how do you draw a bright line between "deliberately degrading", "not giving an advantage to", and "not doing anything to address bandwidth problems when they arise"? It's pretty obvious how you draw that bright line. Don't prioritize and don't congest interfaces. > How would you suggest writing a regulation that doesn't break CDNs and similar, and that can tell the difference between "deliberately hurting" and "not helping"? Easy. As I already wrote, forbid prioritizing and saturation of network interconnects. > How will that regulation adapt when people come up with new ideas to make the web faster? It does not need to when done right, as explained above. > One angle I could imagine working: limiting the ability of one company or family of companies to run both an ISP and network services via that ISP. Still hard to write something robust, though.) Nothing hard about it. It's called functional separation and it's a widely applied remedy to the anticompetitive nature of telecom markets in other countries.
- JoshTriplett 10y ago> CDNs are not prioritized on any ISP network. CDNs work because they have a shorter route to the end user, not because they have a higher priority. So, anyone who can successfully define what they're doing as "not prioritizing" can entirely sidestep any regulation you have in mind. Putting a server in the ISP's datacenter is a common approach. Traffic to those servers doesn't have to go over any external peering links. > ISPs should not and do not apply QoS in their core Many do. As one simple example, look at the ISPs that accelerate the first N bytes of connections, to prioritize interactive requests over bulk transfers/downloads. Other ISPs apply more sophisticated approaches. > It's pretty obvious how you draw that bright line. Don't prioritize and don't congest interfaces. > forbid prioritizing and saturation of network interconnects So, receive and deliver all traffic, regardless of available capacity or financial constraints? Provision every part of the network so it can handle all the traffic passing over any other part, because they're not allowed to limit bandwidth in any way at any point? A saturated interconnect might mean "we're trying to screw Netflix", or it might mean "we can't afford it right now" (either because they're a small ISP and don't have the money, or because they're spending it on something their customers want more).