Award Winning Blog

Showing posts with label subscription agreements. Show all posts
Showing posts with label subscription agreements. Show all posts

Friday, November 9, 2007

Response to Two Columns on Comcast’s Traffic Management Tactics

Two columnists have offered their perspective on the Comcast peer-to-peer traffic management issue. See Larry Seltzer, eWeek.com, Network Policies Should Be Open, Not Neutral (Nov. 6, 2007) available at: http://www.eweek.com/article2/0,1895,2213092,00.asp and George Ou, ZDNet Blog, A Rational Debate on Comcast Traffic Management (Nov. 6, 2007); available at: http://blogs.zdnet.com/Ou/?p=852,

I agree with much of what they wrote, particularly the view that an ISP has a duty to disclose to subscribers what traffic management tactics the ISP can elect to use. Apparently Comcast and others do not want to commit to disclosing what traffic management tactics it might use ostensibly to preclude the onset of actual congestion. No one has disputed that Comcast forged TCP reset packets even though it appears that Comcast could have handled the actually occurring traffic volume without having to degrade anyone’s traffic.

On the other hand I endorse traffic management tactics that respond to actual congestion. I probably part company with some network neutrality advocates by endorsing an ISP offering premium services at a higher rate to power users, provided the ISP does not deliberately degrade service to standard service subscribers.

Neither of the authors addressed whether the current language, or the likely replacement language in subscription agreements, constitutes full disclosure that is fair. From my perspective ISPs cannot have it both ways by marketing “All You Can Eat” unlimited service and “blazing fast” bit rates only to establish, but not disclose quotas and bit rate throttle scenarios. That comes across as a classic “bait and switch” maneuver. ISPs should not be able to insert binding, “take it leave it” terms and conditions that include reserving the option of using “traffic management, “traffic shaping” and “rate-limiting” without defining the terms. ISPs should have to specify what these terms mean specifically as relates to monthly throughput quotas and bit rate throttling, and when such service degradation kicks in.

As the Internet matures and diversifies ISPs should have the option of targeting different consumer segments. As a light to moderate user of Internet access, I do not want to subsidize heavy users, nor do I want them bogging down the network and adversely impacting my service. But I also do not want a trigger happy ISP ready to punish power users regardless of whether these users have made it impossible or even difficult for the ISP to provide an adequate level of service.

I appreciate that ISPs need to recoup their sizeable network investments that seem to grow as more subscribers access bandwidth intensive services. But forging TCP resend packets comes across as a sneaky way to delay having to upgrade networks, or to establish the need for surcharges or rate increases.

Tuesday, October 23, 2007

Empirical Evidence of Net Bias—Now What? (part two)

ISPs now acknowledge that they may meddle with subscribers’ traffic streams, but only to “manage” and “shape” traffic. ISPs typically reserve the option for such meddling in their contract with subscribers. Should you ever take the time to read this document, and a second documents about “Acceptable Use” you will see language that does reserve to the ISP the right to manage their network, ostensibly to optimize it for the benefit of subscribers. The subscriber agreement also attempts to foreclose litigation as an option by stating that subscribers can only seek arbitration to settle any grievance.
In reality the subscriber contract constitutes a unilateral, non-negotiable contract of adhesion, i.e., a “take it or leave” it proposition. In a truly competitive world, disgruntled subscribers could “vote” with their feet and dollars by taking their business elsewhere. But contrary to the FCC’s fantasy statistical reports about double digit service alternatives in most zip codes, consumers have limited options. Taking ones business from DSL to cable modem would not solve the problem if all carriers—through collusion or “conscious parallelism” had the same network management contractual language.
Because the FCC considers ISPs information service providers, the Commission offers no traditional consumer safeguards applicable to telecommunications service providers under Title II of the Communications Act., ISPs must use contracts in lieu of filed tariffs. However, ISP contracts must pass muster with general law and equity principles regarding the fairness of the terms, consumer protection and fraud. In other words, ISPs cannot unilaterally set any terms and conditions and have them stick.
While the FCC may have limited jurisdiction to examine ISP contracts, state and federal courts can lawfully assess whether an ISP has lawfully interpreted the terms of the contract it created and more broadly whether the agreement violates the court’s sense of fairness. In light of the FCC’s deregulation of information service providers, the Commission cannot readily claim that it should preempt judicial review because it still has “primary” jurisdiction to resolve fairness and consumer protection issues.
We may soon see an onslaught of individual and class action law suits against ISPs on grounds that they have not complied with the clear language of their service agreements. For example ISPs have cut off or throttled service to customers for using too much network resources despite an agreement that offers unlimited and unmetered “all you can eat” service. Peer-to-peer customers experience artificial network congestion—a hard thing to prove—may claim that the ISP has violated the service agreement.
A court may serve as the forum for assessing whether an ISP’s reserve right to manage its network includes preemptive strategies that mimic network congestion even when actual traffic conditions do not necessitate network conservation tactics.