January 16, 2025

Eavesdropping as a Telecom Profit Center

In 1980 AT&T was a powerful institution with a lucrative monopoly on transporting long-distance voice communications, but forbidden by law from permitting the government to eavesdrop without a warrant. Then in 1981 Judge Greene took its voice monopoly away, and in the 1980s and 90s the Internet ate the rest of its lunch. By 1996, Nicholas Negroponte wrote what many others also foresaw: “Shipping bits will be a crummy business. Transporting voice will be even worse. By 2020 … competition will render bandwidth a commodity of the worst kind, with no margins and no real basis for charging anything.

During the 1980s and 90s, AT&T cleverly got out of any business except shipping commodity bits: in 1981 it (was forced to) split off its regional phone companies; in 1996 it (voluntarily) split off its equipment-making arm as Lucent Technologies; in 2000-2001 it sold off its Wireless division to raise cash. Now AT&T long-distance bit-shipping is just a division of the former SBC, renamed AT&T.

What profit centers are left in shipping commodity bits? The United States Government spends 44 billion dollars a year on its spy agencies. It’s very plausible that the NSA is willing to pay $100 million or more for a phone/internet company to install a secret room where the NSA can spy on all the communications that pass through. A lawsuit by the EFF alleges such a room, and its existence was implicitly confirmed by the Director of National Intelligence in an interview with the El Paso Times. We know the NSA spends at least $200 million a year on information-technology outsourcing and some of this goes to phone companies such as Verizon.

Therefore, if it’s true that AT&T has such a secret room, then it may be simply that this is the only way AT&T knows how to make money off of shipping bits: it sells to the government all the information that passes through. Furthermore, economics tells us that in a commodity market, if one vendor is able to lower its price below cost, then other vendors must follow unless they also are able to make up the difference somehow. That is, there will be substantial economic pressure on all the other telecoms to accept the government’s money in exchange for access to everybody’s mail, Google searches, and phone calls.

In the end, it could be that the phone companies that cooperated with the NSA did so not for reasons of patriotism, or because their arms were twisted, but because the NSA came with a checkbook. Taking the NSA’s money may be the only remaining profit center in bit-shipping.

Comcast Blocks Some Traffic, Won't Explain Itself

Comcast’s apparent policy of blocking some BitTorrent traffic, which has been discussed on tech sites [example] for months, has now broken out into the mainstream press. Comcast is making things worse by refusing to talk plainly about what they are doing and why. (This is an improvement over Comcast’s previously reported denials, which now appear to be inconsistent with the facts.)

To the extent that Comcast has explained itself, its story seems to be that it is slowing traffic from heavy users in order to keep the network moving smoothly. This would be a reasonable thing for Comcast to do (if they were open about it) – but it’s not quite what they’re actually doing.

For starters, Comcast’s measures are not aimed at heavy users but rather at users of certain protocols such as BitTorrent. And not even all users of BitTorrent are targeted, but only those who use BitTorrent in a particular way: uploading a file to non-Comcast users while not simultaneously downloading parts of the same file. (In BitTorrent jargon, this is called “seeding”.) To get an idea of how odd this is, consider that an uploader who is experiencing blocking can apparently avoid the blocking by adding some download traffic.

It would likely be easier for Comcast to simply measure how much traffic each user is generating and drop the heaviest users’ packets, or just to discard packets at random (a tactic that falls most heavily on those who send and receive the most packets).

Beyond its choice of what to block, Comcast is using an unusual and nonstandard form of blocking.

There are well-established mechanisms for dealing with traffic congestion on the Internet. Networks are supposed to respond to congestion by dropping packets; endpoint computers notice that their packets are being dropped and respond by slowing their transmissions, thus relieving the congestion. The idea sounds simple, but getting the details right, so that the endpoints slow down just enough but not too much, and the network responds quickly to changes in traffic level but doesn’t overreact, required some very clever, subtle engineering.

What Comcast is doing instead is to cut off connections by sending forged TCP Reset packets to the endpoints. Reset packets are supposed to be used by one endpoint to tell the other endpoint that an unexplained, unrecoverable error has occurred and therefore communication cannot continue. Comcast’s equipment (apparently made by a company called Sandvine) seems to send both endpoints a Reset packet, purporting to come from the other endpoint, which causes both endpoints to break the connection. Doing this is a violation of the TCP protocol, which has at least two ill effects: it bypasses TCP’s well-engineered mechanisms for handling congestion, and it erodes the usefulness of Reset packets as true indicators of error.

People have apparently figured out already how to defeat this blocking, and presumably it won’t be long before BitTorrent clients incorporate anti-blocking measures.

It looks like Comcast is paying the price for trying to outsmart their customers.

The ease of applying for a home loan

I’m currently in the process of purchasing a new house. I called up a well-known national bank and said I wanted a mortgage. In the space of 30 minutes, I was pre-approved, had my rates locked in, and so forth. Pretty much the only identifying information I had to provide was the employer, salary, and social security number for myself and my wife, as well as some basic stats on our investment portfolio. Interestingly, the agent said that for people in my situation (sterling credit, paying more than 20% of the down payment out of our own pocket), they believe I’m highly unlikely to ever default on the loan. As a result, they do not need me to go the trouble of documenting my income or assets beyond what I told them over the phone. They’ll take my word for it.

(In an earlier post, I discussed my name and social security number having been stolen from where they had been kept in Ohio. Ohio gave me a free subscription to Debix, which claims to be able to intercept requests to read my credit report, calling my cell phone to ask for my permission. Why not? I signed up. Well, my cell phone never buzzed with any sort of call from Debix. Their service, whatever it does, had no effect here.)

Obviously, there’s a lot more to finalizing a loan and completing the purchase of a home than there is to getting approved for a loan and locking a rate. Nonetheless, it’s striking how little personal information I had to divulge to get this far into the game. Could somebody who knew my social security number use this mechanism to borrow money against my good credit and run away to a Carribean island with the proceeds? I would have to hope that there’s some kind of mechanism further down the pipeline to catch such fraud, but it’s not too hard to imagine ways to game this system, given what I’ve observed so far.

Needless to say, once this home purchase is complete, I’ll be freezing my credit report. Let’s just hope the freezing mechanism is more useful than Debix’s notification system.

(Sidebar: an $18 charge appeared on my credit card last month for a car rental agency that I’ve never used, claiming to have a “swipe” of my credit card. I challenged it, so now the anti-fraud division is allegedly attempting to recover the signed charge slip from the car rental agency. The mortgage agent, mentioned above, saw a note in my credit report on this and asked me if I had “challenged my bank”. I explained the circumstances and all was well. However, it’s interesting to note that the “challenge”, as it apparently appears in my credit report, doesn’t have any indication as to what’s being challenged or how significant it might be. Again, the agent basically took my word for it.)

Grokster Case Lumbers On; Judge To Issue Permanent Injunction

Remember the Grokster case? In which the Supreme Court found the filesharing companies Grokster and StreamCast liable for indirect copyright infringement, for “inducing” infringement by their users? You might have thought that case ended back in 2005. But it’s still going on, and the original judge just issued an interesting ruling. (Jason Schultz has a two part summary of the ruling.)

The issue now before the judge is what relief to grant the copyright-owner plaintiffs against StreamCast, which is the only defendant still standing. It’s apparently a given that the judge will eventually assess monetary damages against StreamCast. And you’d think these damages would be enough to kill StreamCast, so it’s not clear why StreamCast hasn’t just thrown in the towel, shut its doors, and handed over all its assets to the plaintiffs. Instead, StreamCast fought on, so the judge had to decide what kind of injunction, if any, to impose on StreamCast – that is, what rules would govern StreamCast’s future behavior.

The judge first considered the question of whether he could impose on StreamCast obligations (beyond payment of damages) that go beyond what the law requires of ordinary companies. Would he just award money damages and sternly command StreamCast not to break the law again; or would he go further and impose a permanent injunction? After a detailed legal analysis, he concluded that a permanent injunction was appropriate. StreamCast had actively promoted itself as a haven for infringement and “that bell cannot be unrung”.

The copyright-owner plaintiffs had asked for an injunction requiring StreamCast to apply all feasible anti-infringement technologies and to stop all infringment. StreamCast had built its own filtering technology which it said was effective enough, and much cheaper and more practical than commercially available alternatives.

The judge first rejected the plaintiff’s proposal that StreamCast be required to stop all infringement using its software. He recognized, correctly, that that would be impossible, so that such an injunction would be a death sentence for StreamCast.

Instead, the judge will require StreamCast to set up a filtering system that reasonably balances effectiveness and cost, with the strong emphasis on effectiveness. The precise details will be worked out with the help of a special master: an independent technical expert to be appointed by the judge. Which means yet more legal process to choose the special master, wait for the special master’s advice, and then order specific action from StreamCast.

All of this may be proper from a legal standpoint, but it seems unlikely to matter in practice. It’s hard to see how StreamCast can sustain a business given the legal and financial strain they must be under, and the likely ruinous monetary damages they’re still facing. I can understand why the plaintiffs might want to keep StreamCast on life support, in the hope of getting legal rulings that prove helpful elsewhere. But why does StreamCast keep fighting?

Online Symposium: Future of Scholarly Communication

Today we’re kicking off an online symposium on The Future of Scholarly Communication, run by the Center for Information Technology Policy at Princeton. An “online symposium” is a kind of short-term group blog, focusing on a specific topic. Panelists (besides me) include Ira Fuchs, Paul DiMaggio, Peter Suber, Stan Katz, and David Robinson. (See the symposium site for more information on the panelists.)

I started the symposium with an “introductory post. Peter Suber has already chimed in, and we’re looking forward to contributions from the other panelists.

We’ll be running more online symposia on various topics in the future, so this might be a good time to bookmark the symposium site, or subscribe to its RSS feed.