My reset rate according to vuze is actually anywhere between 50 and 85% when I am seeding…so I cannot believe that people are trying to discredit in such an inaccurate fashion. I am on comcast in a NW suburb in Illinois, and I can track and still recreate to this day logs of this occurring.

In fact, the only reason why the reset rate isn’t even showing as high is that when you average in my DOWNLOADS during which there are minimal to no resets (see: 3% range), and how large some of my downloads are (anime subs or linux distros, etc – legal and licensed stuff), it only averages out to like 25% overall.

"Expertise is a journey"

And sometimes you go up a dead end, and drive into a wall. It’s evident Robb doesn’t understand TCP or Bittorrent.

"Did you go to the Torren

The AP not only trumped up, but also misrepresented, your findings. And you and the "Save the Internet" people misled them into doing so. What you are doing is morally repugnant and simply wrong, and stands to harm untold millions of people by eliminating competition and forcing increases in rates for Internet service. You deserve no respect. I’m amazed that you’re brazen enough to show up here.

Rare seeders become healthy seeds if they’re popular even if the initial seeder is reset a few times; it just takes a little longer to light the fire so to speak. Once the torrent becomes more distributed, it is less affected by TCP resets. Furthermore, it’s quite possible to get a complete download from a torrent with zero seeders. That’s because various people will have various pieces of the puzzle but not necessarily all the pieces. You put them together and it produces a complete file. Comcast current system doesn’t go after the pre-seed peers so just because the only seeder gets temporarily blocked doesn’t mean the torrent dies since you’re still pulling data from other partially completed peers.

"Ou: ‘Simone, do you not understand the difference between a professional Network Engineer who designs and builds networks to someone who merely sat in on a few network infrastructure meetings?’

So basically you’re saying that anyone who doesn’t have your experience in networking cannot possibly bring anything to the table regarding this issue."

I’m saying that someone who arrogantly and incorrectly claims the real networking experts are wrong deserves to be called out and deserve to have their credentials scrutinized. All the assertions that Topolski raised here and elsewhere along with the assertions made by Jon Peha have been debunked point by point here. Nothing more needs to be said or explained.

Ou, do you not understand that 16 peers on a single torrent is a low figure for "normal torrents"? Healthy torrents can have well upwards of 3000 peers. So whether or not a single P2P seeder is capped at a 384 Kbps upload speed is irrelevant, because the "aggregate upload bandwidth" by all peers of a single torrent can easily saturate the download bandwidth of a single peer.

Besides, would you like me to quote you from the FCC hearing at Stanford? I was there. You said that the speeds advertised by ISPs like Comcast are "peak speeds" not average speeds. This means that it does not even require 16 peers to saturate the download bandwidth of someone on the Comcast network. At home, we subscribe to Comcast’s internet service with an advertised download bandwidth. In my experience, I have not seen download speeds in excess of 300 KB/s or so, which would translate to a 2.4 Mbps average connection. That means that it’ll probably take only 7 peers on a single torrent to saturate my download bandwidth. If you have any experience with torrents, you’ll know that 7 peers on one torrent is an extremely *low* number.

This *still* does *not* address the fundamental point that has been made and that you have so far refused to address. *Every* *single* *torrent* starts out as a "rare torrent". If Comcast essentially blocks "rare torrents" from being able to seed to other peers, then these "rare torrents" cannot *ever* become "normal torrents". So in carrying out its "network management policies", Comcast effectively blocks any new content from its users to be provided via BitTorrent.

Ou: "Simone, do you not understand the difference between a professional Network Engineer who designs and builds networks to someone who merely sat in on a few network infrastructure meetings?"

So basically you’re saying that anyone who doesn’t have your experience in networking cannot possibly bring anything to the table regarding this issue. Users, hackers who like to tinker with technology, open-source developers, even FCC commissioners who cannot hope to understand the depths of TCP networking in a few hearings — none of these people have the resume to satisfy your demands of what constitutes someone informed enough to comment on these issues.

This is practically the poster-child for an "elitist". It’s funny that you tout your credentials, yet the history of the computer and of the internet is littered with people who were just hackers working out of their garage who had no formal experience in the field whatsoever, who were interested in something and gained knowledge and learned something simply by tinkering with it.

Debunked Topolski claim #2: BitTorrent is restricted to ONLY 3 or 4 upstream TCP sessions.
FALSE: BitTorrent defaults to 4 upstream sessions soft cap per torrent which can be exceeded by default and it can be user reconfigured. Multiple torrents mean even more upstream sessions which give BitTorrent and other P2P applications a huge advantage on a congested network over non P2P users. This explains why 10% of Japan’s population using P2P can account for 75% of all Internet traffic.

Debunked Topolski claim #3: Comcast conclusively issues TCP resets when the network isn’t congested.
FALSE: Topolski cannot make any such claim. No forensic data was submitted. Even if it were submitted, it’s not a large enough data sample. Even if the resets came from Comcast, Topolski can’t know whether the network is congested at 1:45AM in the morning.

Debunked Jon Peha claim #1: A TCP reset TCP session constitutes blockage.
FALSE: P2P utilizes tens of TCP streams and a few temporarily blocked streams constitute a delay.

Debunked Jon Peha claim #2: Users must take an action and manually redial to reestablish P2P connection
FALSE: P2P clients like BitTorrent will automatically resume where they left off without user interaction. Topolski’s attempt to redefine "user" as an application is feeble.

You guys have debunked nothing. Simply claiming that you have "debunked" something without providing any evidence or artifacts that would be contrary, is not debunking. For example, countering something I said with a statement that "all routers issue resets" proves nothing at all.

My 15 minutes should have been over in May of 2007. Instead, Comcast took half a year to turn from an outright denial to weasel-worded admission. Like so many events in life, it isn’t the bad deed that causes the stir, it’s the attempt to cover it up that really causes problems.

Brett, I can’t "trump up" the truth. The Associated Press covered the story because it was news, nor did anyone "trump up" their own independent confirmation. Comcast implemented this secretly to avoid scruitiny, not because every agreed "Duh! We know they do this. So what?" The FCC held two hearings (with more to come, probably) because this behavior is so entirely questionable.

George, the Comcast officer told the FCC that he was not an engineer and did not have first-hand knowledge of what was really happening. When he reiterated that canned paragraph, I stewed on it for a week while it sat unchallenged before I finally decided that it demanded a response and that Cohen deserved the benefit of the doubt. Perhaps, he really did not know.

Richard, my bio is simply my bio. I summed it up at the top of this thread in my SIXTH point. Based on my skills and experience to the best of my ability, I continue to stand by every fact that I have posted. When I’m wrong, I have the decency to readily admit it.

That’s it. If your mission today was to waste a lot of my time, rest peacefully knowing that you’ve accomplished your goal.