<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Streetfighter Blog &#187; FCC</title>
	<atom:link href="http://streetfighterblog.com/tags/fcc/feed/" rel="self" type="application/rss+xml" />
	<link>http://streetfighterblog.com</link>
	<description>A man and his motorcycle</description>
	<lastBuildDate>Mon, 25 Jan 2010 06:43:40 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>FCC opens a can of worms in defining broadband</title>
		<link>http://streetfighterblog.com/2009/09/fcc-opens-a-can-of-worms-in-defining-broadband/</link>
		<comments>http://streetfighterblog.com/2009/09/fcc-opens-a-can-of-worms-in-defining-broadband/#comments</comments>
		<pubDate>Thu, 03 Sep 2009 21:05:11 +0000</pubDate>
		<dc:creator>Matt</dc:creator>
				<category><![CDATA[Geek Stuff]]></category>
		<category><![CDATA[broadband]]></category>
		<category><![CDATA[FCC]]></category>
		<category><![CDATA[ISPs]]></category>

		<guid isPermaLink="false">http://streetfighterblog.com/?p=29</guid>
		<description><![CDATA[<p>I just read an interesting article over on Ars Technica summerizing the debacle the FCC has gotten itself into when it asked for feedback from the public on how to define &#8220;Broadband&#8221;. You see, up until recently broadband was defined as any internet service with a bandwidth of 768Kbps or better. This made perfect <span style="color:#777"> . . . &#8594; Read More: <a href="http://streetfighterblog.com/2009/09/fcc-opens-a-can-of-worms-in-defining-broadband/">FCC opens a can of worms in defining broadband</a></span>]]></description>
			<content:encoded><![CDATA[<p>I just read an interesting article over on Ars Technica summerizing the debacle the FCC has gotten itself into when it asked for feedback from the public on how to define &#8220;Broadband&#8221;. You see, up until recently broadband was defined as any internet service with a bandwidth of 768Kbps or better. This made perfect sense. Anyone can understand that. Now the FCC decided to expand on that definition and asked two basic questions: 1) How should the speeds be determined (actual or advertised) and 2) Should the FCC take an &#8220;application-based&#8221; approach (meaning features not speed).</p>
<p>Here&#8217;s my take:</p>
<ol>
<li> Broadband should be defined as a bandwidth range. Lets say a minimum average bit-rate. If &#8216;X&#8217; service can provide &#8216;Y&#8217;-Kbps averaged out over a month, then it is a broadband service. There could even be classes of broadband. An example would be class-1 = 768k, class-2 = 1.5m, class-3 = 5m, and so on. That would still allow providers to use the term &#8220;Broadband&#8221; for differing levels of service, and also provide a reliable and easy to compare reference for consumers.</li>
<li>Defining &#8220;Broadband&#8221; as a set of features or capabilities will royally screw the consumer. Here&#8217;s why: First, it creates a loophole for ISPs to block services that don&#8217;t fall neatly into the FCC&#8217;s feature list. Second, it could allow ISPs to cap speeds to the bare minimum necessary for the said listed services. Third, it would open the doors for providers to tack-on &#8220;premium&#8221; capabilities to their broadband service. Hey, you&#8217;ve got Web and Email&#8230; Oh you want bit-torrent? that&#8217;s extra. Oh you need usenet? that&#8217;s extra. You can see where I&#8217;m going with this. Imagine the FCC made this list of basic capabilities. What happens as usage on the internet changes in the future?</li>
</ol>
<p>I think that having the FCC define broadband as anything other than an <em>actual</em> bandwidth capability is asking for trouble. It&#8217;s not accurate for an ISP to be considered a broadband provider based on their <em>advertised</em> speeds. It would be much more fair to have the determination of broadband speeds be based upon an average of what the provider&#8217;s network actually supplied. Even more important is keeping the definition of broadband limited to bandwidth. Imagine we defined our roadways based upon their features. I&#8217;ve been on 2-lane highways and ridden 85MPH the whole way. I&#8217;ve also been on 4-lane city streets that have lights at every intersection and not gotten over 35MPH. Imagine that city street could be called a highway just because of the number of lanes it had.</p>
<p>I was lucky enough to be one of the original testers of cable-based broadband when it was first introduced to my neighborhood back in 1996 or so. Since that time &#8211; 13-years now &#8211; I have never once experienced an actual download that was equal to the advertised rate. As a tech person I get asked a lot of questions about one service versus another and what the &#8220;real&#8221; speed on that service is. It always leads to a long conversation about the differences between theoretical limits and RealWorld™ limits. It should be easier than that.</p>
<p>Ultimately I agree with the author, <a href="http://arstechnica.com/authors/matthew-lasar/" target="_blank">Matthew Lasar</a>, in that broadband should be defined as a data rate and not a set of features.</p>
<p>Here&#8217;s the original article: <a href="http://arstechnica.com/telecom/news/2009/09/big-cable-to-fcc-dont-define-broadband-by-its-actual-speed.ars">Big cable to FCC: don&#8217;t define broadband by its actual speed &#8211; Ars Technica</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://streetfighterblog.com/2009/09/fcc-opens-a-can-of-worms-in-defining-broadband/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
