Nearly impossible to enforce. There are a few different ways they could be doing this - title, file checksum, maybe even content sampling - and nearly all of them can be trivially defeated. I find it really hard to envision how an ISP is going to identify, say, a torrent of a video that has the title as a random string, has been re-encoded, RAR-compressed, and when the torrent client is using protocol encryption. They may take some steps such as trying to identify .torrent files originating from their own networks and so forth, but I can't see how it can be terribly effective.
This is much more about the ISP's trying to ward off lawsuits from the content providers than it is about actual effective content filtering. They need to say they're doing *something* so they can wash their hands of the issue. -- Durf On Jan 10, 2008 9:00 AM, Rob Bonfiglio <[EMAIL PROTECTED]> wrote: > > > I saw this and thought it was an interesting article. There isn't really > any technical detail, but I thought some of you might find it interesting. > I'm not sure how I feel about the whole subject. If it starts here how long > will it take to get out of control? Currently ISP's do some filtering, > especially with consumer accounts (port 80 in to your home network etc.) I > see some of that as a protection to their network though, especially when it > comes to e-mail. I'm not sure if the same argument could be made for > filtering out MP3's, MPG's, etc. I'd have to look more closely at the law I > suppose. > > Anyway, here is the article. I'm curious to hear some of your responses: > http://bits.blogs.nytimes.com/2008/01/08/att-and-other-isps-may-be-getting-ready-to-filter/index.html > > > > > > > > > -- -------------- Give a man a match, and he'll be warm for a minute. But set a man on fire, and he'll be warm for the rest of his life. ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
