It is fitting that I am writing this portion of this series on the morning following the AT&T merger approval in the FCC as it provides ample material for this section dealing with problems with Network Neutrality. This is part two of a three part series (outlined below) dealing with Net Neutrality; section 1 is recommended reading before continuing.
1. Why is Network Neutrality essential?
2. Problems with Network Neutrality?
3. How to achieve Net Neutrality: the regulation question?
Problems with Network Neutrality?
Regardless of the industry, any sort of regulatory approach by the government is difficult at best. There are several problems inherent in regulation–forced changes in large, complex, chaotic systems always have unforeseen side effects (IE the Chaos theory) that are often negative; defining regulations is a nearly impossible task of describing a broad range of market behavior in specific legal terms that opens up new loopholes that become economic markets in and of themselves. A quick survey of blogs shows the difficulty of even clearly defining Network Neutrality in a journalistic sense; although I do think that a simple definition of no preference or hindering of traffic suffices and is easy enough to frame in legal terms. Still, the premise itself leaves big loopholes, as we will discuss.
The first major battle on Net Neutrality will be over video delivery. There are rumblings from the voice over IP world about occasional network provider induced problems as well. Still, voice over IP takes little to no traffic (several simultaneous calls can conceivably be carried over a dial up connection) compared to video, which even the low definition streams available on the Internet now can severely tax most broadband connections. These network infrastructure implications gives some measure of legitimacy for current and future arguments FOR a non-neutral network environment; coupled with the potential revenue involved, this will be the fight to watch over the next 5 years. Because of the immediacy of this particular facit of Network Neutrality, I will be focusing on it for the purposes of this section; other types of content have some of their own pecular caveats.
Technical Problems with Network Neutrality
The real problem with the concept of Network Neutrality comes from the technical details of data delivery. Network Neutrality aside, prioritizing network traffic is good networking practice and already employed by many independent ISPs, even the negative control of hindering peer to peer traffic. Fundamentally, it is good network practice to assure priority delivery to real time traffic such as video and voice over non-real time traffic such as file transfers, web browsing (although web 2.0 applications increasingly need some degree of prioritization), and so forth. Although some audio and video applications can be written to compensate–Real Player does this for example with buffering, and does a fairly admirable job of delivering content from CBS’s Innertube)–this is simply not possible with real-time interactive applications such as Internet telephony and video conferencing.
To some extent, issues can be mitigated by prioritizing the connection between the end user and the ISP, using a router at the customer premises that supports QoS (Quality of Service). As a side note, there is some indication from AT&T’s wording of their Network Neutrality concessions to the FCC that this is intergral to their IPTV delivery (more on this later). This does not do anything about congestion problems on the Internet at large, as this only affects a single piece of the connection and does not provide end-to-end reliability. Still, for our current generation of Internet content, this method of QoS does work, for the most part, most of the time. It also has the additional benefit of providing end-user control over their own connection.
Nevertheless, the viability of this method is at best short-lived. Current Internet television and video content is, simply put, a major regression in terms of signal quality compared to traditional television delivery systems. No one is really willing to watch the Matrix on You-Tube quality video–we may enjoy watching college students stuff Mentos in a coke bottle, but most of the videos are also 1-2 minutes in length because that’s about as long as we can stand watching low-quality, pixelated, jerky, mis-synced videos that inherently remind us of Aunt Gertrude’s vacation videos. At some point, the quality of the content in terms of viewability MUST increase to really become a replacement delivery method for television.
It is currently not even feasible to deliver SD television via the Internet; as we migrate to HD television, the network infrastructure implications are far from trivial and DO require extensive design considerations to be able to deliver a good customer experience, even from the providers own network. AT&T’s U-Verse product is somewhat of an engineering feat in and of itself, and it doesn’t have to compete with the congestion of best effort Internet traffic. A world where high-definition video content streams delivered over the Internet DOES require some prioritization in order to be viable; furthermore, delivering 5 million identical 10Mb/s streams to 5 million households (a reasonable scenario if everyone is watching their Tuesday night sitcoms over the Intenet) necessitates multi-cast delivery which mandates some level of integration between the content provider and the network service provider in order to really work in the immediate future.
Simply put, wide-scale high-definition video distribution does require some technical concessions that fundamentally violate Network Neutrality; given current (and immediate future) technology, I am simply unconvinced that there is a workable solution for using the Internet for significant video delivery that fits within the principle of Network Neutrality. We will discuss some solutions to this problem in part three of this series.
Legal Problems with Network Neutrality
The much greater problem with Network Neutrality, though, is that it is really a moot point–network providers already bypass any and all Network Neutrality arguments and will continue to bypass any and all regulations passed by FCC, Congress, or otherwise. As long as video traffic remains separate from the Internet traffic, it is somewhat of a pointless discussion. Hence, there are no bloggers crying foul against Comcast or Time-Warner on Network Neutrality grounds even though the video content available through their cable connection is generations better quality than the video content that their cable modem can handle; likewise, no one calls foul against BellSouth or AT&T because telephone calls placed over POTS are generally better quality than telephone calls placed over the Internet.
Even as the telcos are deploying their next generation networks that support triple play, their fundamental design simply technically and legally neatly sidesteps most of the Network Neutrality argument. In effect, they don’t give preference to their own services; they go much further and create two separate networks, one with guaranteed delivery (for their own services) and a small capacity, best effort network for third party services (Internet).
AT&T
AT&T’s U-Verse product is likewise sidestepping the whole issue by simply making a 25Mb/s ADSL2 connection a 5Mb/s U-Verse Internet connection; the other 20 Mb/s is used for their video delivery. They have absolutely no need to block, restrict, or degrade competing video traffic–simply put, they can always deliver a better video experience in their 20Mb/s portion than can be obtained from third parties in the 5Mb/s Internet portion. In effect, they are immune to legislation mandating an unrestricted Internet pipe (which may come sooner or later) and would only be affected IF the legislation went as far as to actually mandate use of the entire ADSL2 connection as “Internet”; I’m not sure of the feasibility of anti-monopolistic based legislation mandating MORE services to be offered by a corporation.
Verizon
Verizon’s FTTH solution also sidesteps the problem, although they are even clearer than AT&T. They deliver the video portion of their triple-play solution using RF (what cable uses) over fiber rather than using IP. Any legislation dealing with IP traffic (ie Net Neutrality) would entirely miss them.
It is important to note that, by using the right CPE (customer premise equipment), the methods mentioned above in use by cable companies, AT&T, and Verizon can be used (and are) in use for other types of content–be it voice, video, or even web applications. It especially can be an effective strategy because it also creates a disincentive to provide quality Internet access–indeed, if the Internet access is universally bad for real time content (and, as long as it is universally bad, it still is acceptable from a Network Neutrality viewpoint), then it simply steers usage of real-time applications to the network provider’s products and leaves the generic web-surfing relatively unhindered. Well designed CPE can make this transparant to the end-user while maintaining seperate networks for technical and legal reasons.
Although this is currently to some degree the status-quo and will be solidified over the next few years, this is not how it has to be. Stay tuned for part 3 in which we will start discussion on how to really ensure a free and open Internet.
Uncategorized