<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Is Comcast (still, really) blocking BitTorrent?</title>
	<atom:link href="http://bennett.com/blog/2008/05/is-comcast-still-really-blocking-bittorrent/feed/" rel="self" type="application/rss+xml" />
	<link>http://bennett.com/blog/2008/05/is-comcast-still-really-blocking-bittorrent/</link>
	<description>A personal blog</description>
	<lastBuildDate>Sun, 11 Sep 2011 14:57:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Richard Bennett</title>
		<link>http://bennett.com/blog/2008/05/is-comcast-still-really-blocking-bittorrent/#comment-5456</link>
		<dc:creator>Richard Bennett</dc:creator>
		<pubDate>Thu, 22 May 2008 17:17:54 +0000</pubDate>
		<guid isPermaLink="false">http://bennett.com/blog/?p=4420#comment-5456</guid>
		<description>Good question.</description>
		<content:encoded><![CDATA[<p>Good question.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brett Glass</title>
		<link>http://bennett.com/blog/2008/05/is-comcast-still-really-blocking-bittorrent/#comment-5455</link>
		<dc:creator>Brett Glass</dc:creator>
		<pubDate>Thu, 22 May 2008 13:31:53 +0000</pubDate>
		<guid isPermaLink="false">http://bennett.com/blog/?p=4420#comment-5455</guid>
		<description>I would like to know how they could possibly have gathered any usable data if their tester does not work.</description>
		<content:encoded><![CDATA[<p>I would like to know how they could possibly have gathered any usable data if their tester does not work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Bennett</title>
		<link>http://bennett.com/blog/2008/05/is-comcast-still-really-blocking-bittorrent/#comment-5454</link>
		<dc:creator>Richard Bennett</dc:creator>
		<pubDate>Thu, 22 May 2008 09:49:21 +0000</pubDate>
		<guid isPermaLink="false">http://bennett.com/blog/?p=4420#comment-5454</guid>
		<description>It didn&#039;t work for me either. This is starting to look like the Max Prank Institute.</description>
		<content:encoded><![CDATA[<p>It didn&#8217;t work for me either. This is starting to look like the Max Prank Institute.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brett Glass</title>
		<link>http://bennett.com/blog/2008/05/is-comcast-still-really-blocking-bittorrent/#comment-5453</link>
		<dc:creator>Brett Glass</dc:creator>
		<pubDate>Thu, 22 May 2008 04:25:50 +0000</pubDate>
		<guid isPermaLink="false">http://bennett.com/blog/?p=4420#comment-5453</guid>
		<description>I just tried the Max Planck (&quot;walk the Planck?&quot;) test. It failed. It said:

We are sorry, the test failed due to a problem.

The connection to the measurement server timed out. This can happen if it takes too long to load the applet.</description>
		<content:encoded><![CDATA[<p>I just tried the Max Planck (&#8220;walk the Planck?&#8221;) test. It failed. It said:</p>
<p>We are sorry, the test failed due to a problem.</p>
<p>The connection to the measurement server timed out. This can happen if it takes too long to load the applet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Bennett</title>
		<link>http://bennett.com/blog/2008/05/is-comcast-still-really-blocking-bittorrent/#comment-5452</link>
		<dc:creator>Richard Bennett</dc:creator>
		<pubDate>Tue, 20 May 2008 18:00:49 +0000</pubDate>
		<guid isPermaLink="false">http://bennett.com/blog/?p=4420#comment-5452</guid>
		<description>I measured the upload and download rates, Paul. That&#039;s data. My point is that the upload and download rates are important, but the fact that random RSTs may or may not be injected to prune excess connections is not important.

It&#039;s the result that matters, not the method.</description>
		<content:encoded><![CDATA[<p>I measured the upload and download rates, Paul. That&#8217;s data. My point is that the upload and download rates are important, but the fact that random RSTs may or may not be injected to prune excess connections is not important.</p>
<p>It&#8217;s the result that matters, not the method.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://bennett.com/blog/2008/05/is-comcast-still-really-blocking-bittorrent/#comment-5451</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Tue, 20 May 2008 15:08:04 +0000</pubDate>
		<guid isPermaLink="false">http://bennett.com/blog/?p=4420#comment-5451</guid>
		<description>As a good engineer, you will realise you tested exactly nothing.

You downloaded a torrent and it got to you. You did not determine if your download had been throttled because you cannot quantify it by downloading - you need to inspect raw packets to find the resets that comcast use as their mechanism to limit it.

You draw a false conclusion that a website that is currently &#039;busy&#039; has problems - did it ever occur to you that the website operators, by limiting the number of concurrent tests are ensuring that any results they do obtain are not affected by overutilisation?

Your article is what we in the professional tech world call &#039;Intellectual Masturbation&#039; - zero in-depth analysis and conclusions drawn on false assumptions and proven through shoddy testing methodolgy.

Comcast DID say they were doing nothing - the Network Neutrality Group that many /.&#039;ers are involved with have verified and documented it. When caught they changed their story to &#039;we&#039;re delaying&#039; -&gt; a euphamism for &#039;we&#039;re actively resetting bittorrent connections so that it takes the end use longer to download something&#039;. 

The issue is not and never has been &#039;comcast are blocking ALL bittorrent traffic&#039; - but they are actively interfering with it. We don&#039;t need any other proof beyond the forged packets themselves to know that comcast are interfering. 

To use one of Mr Glass&#039; style of overexaggerated analogy - The community has reported a rapist and have caught the rapist on camera - while the rapist&#039;s supporters are screaming &#039;He didn&#039;t murder anyone!&#039;.</description>
		<content:encoded><![CDATA[<p>As a good engineer, you will realise you tested exactly nothing.</p>
<p>You downloaded a torrent and it got to you. You did not determine if your download had been throttled because you cannot quantify it by downloading &#8211; you need to inspect raw packets to find the resets that comcast use as their mechanism to limit it.</p>
<p>You draw a false conclusion that a website that is currently &#8216;busy&#8217; has problems &#8211; did it ever occur to you that the website operators, by limiting the number of concurrent tests are ensuring that any results they do obtain are not affected by overutilisation?</p>
<p>Your article is what we in the professional tech world call &#8216;Intellectual Masturbation&#8217; &#8211; zero in-depth analysis and conclusions drawn on false assumptions and proven through shoddy testing methodolgy.</p>
<p>Comcast DID say they were doing nothing &#8211; the Network Neutrality Group that many /.&#8217;ers are involved with have verified and documented it. When caught they changed their story to &#8216;we&#8217;re delaying&#8217; -&gt; a euphamism for &#8216;we&#8217;re actively resetting bittorrent connections so that it takes the end use longer to download something&#8217;. </p>
<p>The issue is not and never has been &#8216;comcast are blocking ALL bittorrent traffic&#8217; &#8211; but they are actively interfering with it. We don&#8217;t need any other proof beyond the forged packets themselves to know that comcast are interfering. </p>
<p>To use one of Mr Glass&#8217; style of overexaggerated analogy &#8211; The community has reported a rapist and have caught the rapist on camera &#8211; while the rapist&#8217;s supporters are screaming &#8216;He didn&#8217;t murder anyone!&#8217;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brett Glass</title>
		<link>http://bennett.com/blog/2008/05/is-comcast-still-really-blocking-bittorrent/#comment-5450</link>
		<dc:creator>Brett Glass</dc:creator>
		<pubDate>Sun, 18 May 2008 17:40:14 +0000</pubDate>
		<guid isPermaLink="false">http://bennett.com/blog/?p=4420#comment-5450</guid>
		<description>Two interesting points I neglected to mention in my posting just above. Firstly, if you look at the &quot;results&quot; page of that German &quot;test&quot; site, at http://broadband.mpi-sws.mpg.de/transparency/results/, you will notice an interesting pattern. If you believe their data (and, of course, it really should be independently verified), the US is, once again, on the technological forefront -- ahead of nearly every country in the world. It shows that nearly 25% of the tested Internet connections in the US had some form of P2P throttling in place. This is a good thing; it means that we as a nation are doing a better job of stopping network abuse, and preventing bandwidth hogs from degrading our networks, than any other country in the world except Singapore. Good for us!

The second point I didn&#039;t mention above is that I&#039;ve tried to contact Peter Svensson, whom Richard dubs &quot;Free Press&#039; personal reporter,&quot; and give him accurate information about the practice of P2P throttling by ISPs. I got through once and spoke to him for a few minutes, offering him more data if he was interested. But he never contacted me, and has continued to write stories which are biased and inaccurate (and which repeat false statements made by Free Press). Therefore, Richard&#039;s characterization appears (alas) to be quite accurate.</description>
		<content:encoded><![CDATA[<p>Two interesting points I neglected to mention in my posting just above. Firstly, if you look at the &#8220;results&#8221; page of that German &#8220;test&#8221; site, at <a href="http://broadband.mpi-sws.mpg.de/transparency/results/" rel="nofollow">http://broadband.mpi-sws.mpg.de/transparency/results/</a>, you will notice an interesting pattern. If you believe their data (and, of course, it really should be independently verified), the US is, once again, on the technological forefront &#8212; ahead of nearly every country in the world. It shows that nearly 25% of the tested Internet connections in the US had some form of P2P throttling in place. This is a good thing; it means that we as a nation are doing a better job of stopping network abuse, and preventing bandwidth hogs from degrading our networks, than any other country in the world except Singapore. Good for us!</p>
<p>The second point I didn&#8217;t mention above is that I&#8217;ve tried to contact Peter Svensson, whom Richard dubs &#8220;Free Press&#8217; personal reporter,&#8221; and give him accurate information about the practice of P2P throttling by ISPs. I got through once and spoke to him for a few minutes, offering him more data if he was interested. But he never contacted me, and has continued to write stories which are biased and inaccurate (and which repeat false statements made by Free Press). Therefore, Richard&#8217;s characterization appears (alas) to be quite accurate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brett Glass</title>
		<link>http://bennett.com/blog/2008/05/is-comcast-still-really-blocking-bittorrent/#comment-5449</link>
		<dc:creator>Brett Glass</dc:creator>
		<pubDate>Fri, 16 May 2008 17:20:56 +0000</pubDate>
		<guid isPermaLink="false">http://bennett.com/blog/?p=4420#comment-5449</guid>
		<description>Comcast would be 100% justified if it DID block BitTorrent, because BitTorrent and other P2P programs violate its terms of service and take its bandwidth without compensation. They also degrade the performance of the network for legitimate users.</description>
		<content:encoded><![CDATA[<p>Comcast would be 100% justified if it DID block BitTorrent, because BitTorrent and other P2P programs violate its terms of service and take its bandwidth without compensation. They also degrade the performance of the network for legitimate users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Bennett</title>
		<link>http://bennett.com/blog/2008/05/is-comcast-still-really-blocking-bittorrent/#comment-5448</link>
		<dc:creator>Richard Bennett</dc:creator>
		<pubDate>Fri, 16 May 2008 09:23:17 +0000</pubDate>
		<guid isPermaLink="false">http://bennett.com/blog/?p=4420#comment-5448</guid>
		<description>Comcast has always said that they only prune TCP connections for BitTorrent in seeding mode, and only then when the segment is highly loaded. The effect of this is to take bandwidth from BT seeders and re-distribute it to other applications. The main beneficiary of this is actually BitTorrent itself, in the typical sharing mode. So it&#039;s simply a matter of throttling BT in one condition to aid BT in another.

The &quot;study&quot; by the Germans didn&#039;t measure BT throughput, and that&#039;s the important statistic.</description>
		<content:encoded><![CDATA[<p>Comcast has always said that they only prune TCP connections for BitTorrent in seeding mode, and only then when the segment is highly loaded. The effect of this is to take bandwidth from BT seeders and re-distribute it to other applications. The main beneficiary of this is actually BitTorrent itself, in the typical sharing mode. So it&#8217;s simply a matter of throttling BT in one condition to aid BT in another.</p>
<p>The &#8220;study&#8221; by the Germans didn&#8217;t measure BT throughput, and that&#8217;s the important statistic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Ou</title>
		<link>http://bennett.com/blog/2008/05/is-comcast-still-really-blocking-bittorrent/#comment-5447</link>
		<dc:creator>George Ou</dc:creator>
		<pubDate>Fri, 16 May 2008 06:12:19 +0000</pubDate>
		<guid isPermaLink="false">http://bennett.com/blog/?p=4420#comment-5447</guid>
		<description>Jim, Comcast didn&#039;t change their message; they always maintain that they&#039;re delaying BitTorrent.

This report only confirms that individual TCP connections are being blocked; it&#039;s being misreported as BitTorrent being blocked.  BitTorrent uses dozens of TCP streams so blocking a few of those streams has the effect of slowing down BitTorrent thus &quot;delay&quot;.  Furthermore, as TCP streams are broken, BitTorrent will naturally open up more connections automatically within seconds of connections being broken.</description>
		<content:encoded><![CDATA[<p>Jim, Comcast didn&#8217;t change their message; they always maintain that they&#8217;re delaying BitTorrent.</p>
<p>This report only confirms that individual TCP connections are being blocked; it&#8217;s being misreported as BitTorrent being blocked.  BitTorrent uses dozens of TCP streams so blocking a few of those streams has the effect of slowing down BitTorrent thus &#8220;delay&#8221;.  Furthermore, as TCP streams are broken, BitTorrent will naturally open up more connections automatically within seconds of connections being broken.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

