Slashdot Mirror
Questionable "Best Effort" Copyright Enforcement
pmdubs writes "Princeton University Professor Michael Freedman, creator of CoralCDN, discusses how he received around 100 pre-settlement letters in one month from various copyright agencies after invalid BitTorrent tracker requests were issued through CoralCDN's proxies. Interestingly, the participating agencies made no effort whatsoever to verify that the Coral nodes were actually running BitTorrent, which they weren't! He questions just how much effort agencies take to reduce false positives when it comes to DMCA notices. Considering the credence that network operators give to such notices (they'll often cut your service upon receipt), it would seem that the answer is 'not enough.'"
From what I understand, the notices are not being sent because of traffic, but because of IP logs (which are not the same). Specifically, they look at the IP logs on the torrent tracker to identify which machines have the content. Any machine is able to register itself with the tracker and say it has any content, regardless of whether it does or not, and regardless of whether it's even running BitTorrent. That's how the guy got his printer DMCA'd - he manually registered his printer's IP address with one or more trackers.
Considering the fact that it's possible to do that, I am completely confused as to how it is possible that every single IP address that the RIAA, MPAA, Congress, or Senate uses has not been registered with as many trackers as possible. Sure, it would degrade BitTorrent performance on those trackers, but it would be worth it to have the RIAA flood the house or senate with takedown notices when no illegal activity has taken place. Then we might start to see that "under the penalty of perjury" clause get enforced.
If they aren't actually connecting to those machines and verifying that 1) they are receiving traffic and 2) they are distributing content, then they haven't exactly made a good-faith effort.
"Our two-party system is like a bowl of shit looking at itself in a mirror." - Lewis Black
...requests to BitTorrent trackers can also use CoralCDN, as these are simply HTTP GETs with a client's relevant information encoded in the tracker URL's query string, e.g., http://denis.stalker.h3q.com.6969.nyud.net/announce?info_hash=(hash)&peer_id=(name)&port=52864&uploaded=231374848&downloaded=2227372596&left=0&corrupt=0&key=E0591124&numwant=200&compact=1&no_peer_id=1. Notice that the HTTP request includes a peer's unique name (a long random string) and a port number, but notably does not include an IP address for that client. It's an optional parameter in the specification that many BitTorrent clients don't include. (In fact, even if the request includes this IP parameter, some trackers ignore it.) Instead, the tracker records the network-level IP address from where the HTTP request originated (the other end of the TCP connection), together with the supplied port, as the peer's network address.
In this case CoralCDN was effectively acting as a proxy - the IP address wasn't being falsified. Although these guys did appear to have some luck with falsified IP addresses: Why My Printer Received a DMCA Takedown Notice.
The way it sounded to me from TFA, this is fraud. Here's the legal definition (not TFA):
To establish a claim of fraud, plaintiffs must show by clear and convincing evidence (1) a representation; (2) its falsity; (3) its materiality; (4) knowledge of its falsity or a reckless disregard for its truth or falsity; (5) intent that the plaintiff act upon the representation; (6) the hearer’s ignorance of its falsity; (7) the hearer’s reliance on its truth; (8) the hearer’s right to rely thereon; and (9) the hearer’s consequent and proximate injury. King v. Oxford, 282 S.C. 307, 311, 318 S.E.2d 125, 127 (Ct. App. 1984).
Could be an interesting case to argue in court.