<?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: Nothing Wrong with Higher Charges for High Volume Users</title>
	<atom:link href="http://blog.cdt.org/2008/05/08/nothing-wrong-with-higher-charges-for-high-volume-users/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.cdt.org/2008/05/08/nothing-wrong-with-higher-charges-for-high-volume-users/</link>
	<description>Digital Policy in Process</description>
	<lastBuildDate>Fri, 16 Oct 2009 17:02:16 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: barry payne</title>
		<link>http://blog.cdt.org/2008/05/08/nothing-wrong-with-higher-charges-for-high-volume-users/comment-page-1/#comment-6077</link>
		<dc:creator>barry payne</dc:creator>
		<pubDate>Mon, 12 May 2008 03:21:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cdt.org/?p=248#comment-6077</guid>
		<description>this is off the mark on several levels ... bandwidth cost at the network level is not &quot;caused&quot; by GB use over time except by coincidence - it&#039;s caused by the coincident use of Mbs within a bandwidth tier which has an &quot;up to&quot; maximum and in that context, neither is it an &quot;all you can eat&quot; condition - from which the myth of &quot;exafloods&quot; and &quot;bandwidth hogs&quot; is bandied about as nonsense to undermine net neutrality - each time the burst speed is hit, it&#039;s &quot;all that can be eaten&quot; and absent congestion, it&#039;s &quot;always on and available&quot; as marketed and paid for from the customer&#039;s perspective

capping GBs is a crude measure of bandwidth cost because it doesn&#039;t track bandwidth cost 1:1, including congestion cost in peak periods - consequently, &quot;small&quot; users don&#039;t &quot;subsidize large&quot; users or vice versa when both pay the same for bandwidth - nor do &quot;large&quot; users cause more congestion in peak periods than equivalent amounts of bandwidth use in Mbs by &quot;small&quot; users, regardless of total GB use over time - this is another myth made up by opponents of net neutrality to justify arbitrary and intimidating management to suppress the effects of oversold bandwidth and its consequences of manufactured shortages and congestion caused by major network providers - not the customers - rather than pricing it transparently and uniformly

the 250GB cap for Comcast does act in conjunction with &quot;up to&quot; maximums of bandwidth to replace the blatant discrimination with neutral access and pricing, and also functions as a &quot;dumb pipe&quot; in agnostic fashion among content use up to that maximum, beyond which selective discrimination kicks in again - it is designed as a calculated &quot;sweet spot&quot; to retain a maximum revenue base of &quot;low&quot; users while either losing high users or forcing them to a higher grade, while deterring competition for its cable tv content</description>
		<content:encoded><![CDATA[<p>this is off the mark on several levels &#8230; bandwidth cost at the network level is not &#8220;caused&#8221; by GB use over time except by coincidence &#8211; it&#8217;s caused by the coincident use of Mbs within a bandwidth tier which has an &#8220;up to&#8221; maximum and in that context, neither is it an &#8220;all you can eat&#8221; condition &#8211; from which the myth of &#8220;exafloods&#8221; and &#8220;bandwidth hogs&#8221; is bandied about as nonsense to undermine net neutrality &#8211; each time the burst speed is hit, it&#8217;s &#8220;all that can be eaten&#8221; and absent congestion, it&#8217;s &#8220;always on and available&#8221; as marketed and paid for from the customer&#8217;s perspective</p>
<p>capping GBs is a crude measure of bandwidth cost because it doesn&#8217;t track bandwidth cost 1:1, including congestion cost in peak periods &#8211; consequently, &#8220;small&#8221; users don&#8217;t &#8220;subsidize large&#8221; users or vice versa when both pay the same for bandwidth &#8211; nor do &#8220;large&#8221; users cause more congestion in peak periods than equivalent amounts of bandwidth use in Mbs by &#8220;small&#8221; users, regardless of total GB use over time &#8211; this is another myth made up by opponents of net neutrality to justify arbitrary and intimidating management to suppress the effects of oversold bandwidth and its consequences of manufactured shortages and congestion caused by major network providers &#8211; not the customers &#8211; rather than pricing it transparently and uniformly</p>
<p>the 250GB cap for Comcast does act in conjunction with &#8220;up to&#8221; maximums of bandwidth to replace the blatant discrimination with neutral access and pricing, and also functions as a &#8220;dumb pipe&#8221; in agnostic fashion among content use up to that maximum, beyond which selective discrimination kicks in again &#8211; it is designed as a calculated &#8220;sweet spot&#8221; to retain a maximum revenue base of &#8220;low&#8221; users while either losing high users or forcing them to a higher grade, while deterring competition for its cable tv content</p>
]]></content:encoded>
	</item>
</channel>
</rss>
