Verizon, Comcast Say They Are P2P Friendly
An anonymous reader writes "Verizon and Comcast announced they will not 'block or throttle Internet traffic delivered via peer-to-peer networks' — essentially proclaiming that they are now P2P friendly. The decision came as a result of a test conducted with Verizon and Pando Networks, testing the benefits of a P2P/ISP partnership. During the test, the amount of P2P content delivered to Verizon subscribers from inside its network grew from 2 percent to 50 percent. This shows ISPs need to work with P2P companies to improve content delivery and manage traffic. Verizon also announced it will be looking at ways to use P2P technology to deploy new features on FiOS TV." Just the same, read on for one approach to mitigating likely tightening restrictions on P2P network use.
Another anonymous reader writes "RIAA/MPAA have recently been targeting torrent aggregators like PirateBay, because the aggregators are the vulnerable components of the BitTorrent protocol. A new open-source project to thwart such attacks was announced on p2p-hackers and released yesterday:
Cubit, a new open-source p2p overlay, enables the Azureus BitTorrent client to look up torrents via approximate keyword search... Cubit completely decentralizes the lookup process through an efficient, light-weight peer-to-peer overlay that can perform approximate matches. It performs searches without relying on any centralized components, and therefore is immune to legal and technical attacks targeting torrent aggregators."
I'll believe it when I see it.
ISP conflict will remain, it will just become more subtle and more neutral.
You see, 50% is not good enough from the ISPs viewpoint: That still requires just as many bits crossing the ISP's boundry as if the content provider used UNCACHED HTTP.
In practice, many (most?) ISPs use transparent HTTP caches, so having 50% of the data stay internal is still no good, as on popular files (eg, a big youtube video), 99% of the traffic stays internal for HTTP.
Even PERFECT P2P requires at least one outbound copy for each inbound copy, so a PERFECT P2P system will require 2x the traffic crossing the border when compared with HTTP thats cached.
Test your net with Netalyzr
Jeepers, no more bandwidth throttling? Thanks Comcast!
How much extra will you be charging us for that?
My torrent stops registering massive packet forgery and my uploads stop getting throttled to 1/5 the original speed after 5 seconds from initialization. As well as my web-browsing speed, and my gaming speed, and my windows/ubuntu updates speed...
What would really be great is if Cubit would eliminate all the nasty tracker ads. They are very annoying for people like me who are just after software, not porn.
And looking at the current batch of lawsuits, I'd say now is the time to start supporting Cubit in all the major clients (I'm thinking particularly of KTorrent...) So please work on it if you have the skills, and bug people who do if you don't (that would be me).
The government can't save you.
Most consumer level service comes with an Acceptable Usage Policy. Mine says that (this is paraphrased) "At the sole discretion of big cable company (not comcast), users may be terminated for abuse or excessive usage".
So, we'll move from throttling to arbitrary caps. Maybe after XXGB your speeds are cut to 1/10th. Or maybe (like my cable company), they can just say "Well, we don't want you as a customer any more".
Explicit caps? We can complain or not subscribe if they're low- I'm for that if somebody is downloading 300GB+ per month, using my node. But the idea of "Well, you downloaded 'too much'" is just as bad as lying about throttling.
It has been my experience that in some ways DSL is superior to cable. I remember when cable first came out everyone who got it thought it was great. Then their neighbor got it, and their other neighbor got it, and suddenly it became obvious that the entire neighborhood was on one shared pipe and a single bandwidth hog could ruin it for everyone. It doesn't seem like much has changed in the last decade. With DSL you can count on getting the bandwidth that you pay for but the peak available bandwidth isn't as high as cable. On cable you might get some really high peak speeds, but the cable networks haven't been designed to sustain high transfer rates for long periods of time.
He's obviously a spinmeister working for the company.
When people buy a product or service they expect it to work reasonably. It's like saying that a car that doesn't anymore explode into flames is now 'friendly'... The word he so boldly uses don't even appear on the FA. Save your spam for eggs and bacon.
I believe in actions, not words and hope more people would follow suit.
Interestingly enough, this Team Fortress issues seems to have resolved itself in the last week and a half. I imagine this is due to a Team Fortress update, as I did not update the firmware in my router-- but this is an extreme coincidence.
Is BitTorrent traffic on a well-known BitTorrent port (6881) throttled?
* 2 out of 2 BitTorrent transfers were interrupted while uploading (seeding) using forged TCP RST packets. It seems like your ISP hinders you from uploading BitTorrent traffic to our test server.
* The BitTorrent download worked. Our tool was successful in downloading data using the BitTorrent protocol.
* There's no indication that your ISP rate limits your BitTorrent downloads. In our tests a TCP download achieved minimal 713 Kbps while a BitTorrent download achieved maximal 720 Kbps.
Is BitTorrent traffic on a non-standard BitTorrent port (4711) throttled?
* 2 out of 2 BitTorrent transfers were interrupted while uploading (seeding) using forged TCP RST packets. It seems like your ISP hinders you from uploading BitTorrent traffic to our test server.
* The BitTorrent download worked. Our tool was successful in downloading data using the BitTorrent protocol.
* There's no indication that your ISP rate limits your BitTorrent downloads. In our tests a TCP download achieved minimal 661 Kbps while a BitTorrent download achieved maximal 741 Kbps.
Is TCP traffic on a well-known BitTorrent port (6881) throttled?
* There's no indication that your ISP rate limits all downloads at port 6881. In our test, a TCP download on a BitTorrent port achieved at least 713 Kbps while a TCP download on a non-BitTorrent port achieved at least 661 Kbps.
* There's no indication that your ISP rate limits all uploads at port 6881. In our test, a TCP upload on a BitTorrent port achieved at least 1353 Kbps while a TCP upload on a non-BitTorrent port achieved at least 1403 Kbps.
If you read the article carefully, this is not about allowing unfettered P2P on their networks at all. They are deliberately obfuscating the issue. They leave the door open for blocking, filtering and "shaping" (ie. TCP resetting) any protocols they want. This is kind of like Verizon Wireless proudly announcing "We are radio phone call friendly" when the issue is whether to support GSM or CDMA.
Verizon's senior technologist talks about "working with P2P companies", which is radically different than allowing anyone to write a P2P networking app that does (fill in the blank.) Then goes on to say that work needs to be done on P2P DRM.
All in all, the tone of the article seems to confirm that the fight for network neutrality is far from over.
In the final analysis, protecting aggregators won't matter unless we get genuine 'net neutrality. The ISPs will switch to a 'whitelist' of content providers. In other words, if you want your content delivered, you will pay, become a 'partner', host ISP banner ads or whatever. All others will grovel with the lowest QoS. This sidesteps accusations of throttling 'undesirable' services. Everyone gets throttled and will have to pay to get out of jail.
I don't think the big ISPs have anything special against P2P services (that they don't have against anyone else). They just want to extract money out of them. With big players like Google, Yahoo, and MSN, that's easy to do. There's advertising revenue that can be quantified and the ISPs can skim off of. P2P just happens to be a big enough consumer of bandwidth that the ISPs would like them to pay to play as well.
Have gnu, will travel.
If you're around Ottawa or feel like going there, there's a "Net Neutrality Rally" on May 27: www.netneutralityrally.ca.
My ISP (Teksavvy) emailed me a couple hours ago saying apparently most of the Teksavvy staff is taking the day off to go to the rally so please only call in with tech support questions if it's really important.
That's pretty cool if you ask me.
- Andrew.
www.clarke.ca
Fox, Wolf Say They Are Rabbit Friendly
And steve balmer aint gonna throw any more chairs.
Read radical news here