<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: FCC Opens &#8220;White Space&#8221;</title>
	<atom:link href="http://www.geeknewscentral.com/2008/11/05/fcc-opens-white-space/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.geeknewscentral.com/2008/11/05/fcc-opens-white-space/</link>
	<description>Geek News Central is the technical site for Geeks. We Spin tech for the common man. With a Family of Tech Shows and Content.</description>
	<lastBuildDate>Wed, 08 Feb 2012 16:38:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Mike Staples</title>
		<link>http://www.geeknewscentral.com/2008/11/05/fcc-opens-white-space/comment-page-1/#comment-4280</link>
		<dc:creator>Mike Staples</dc:creator>
		<pubDate>Thu, 06 Nov 2008 17:09:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.geeknewscentral.com/2008/11/05/fcc-opens-white-space/#comment-4280</guid>
		<description>I&#039;m a career broadcast engineer, and what I am about to say comes from 35 years of dealing with interference issues, not out of any provincial turf-defending viewpoint. My job is to make things work, not to prevent them from working.
&lt;span class=&quot;mt-export2wp&quot;&gt;&lt;/span&gt;
Identifying sources of interference and resolving the problems is usually a difficult task at best. The concept that exists in most peoples&#039; minds of riding around with a magical direction-finding device, quickly locating the interfering device and having it shut off is really a fantasy. In reality, most interference is hard to pinpoint (even when from a stationary source) and having it shut off is fraught with legal and practical difficulties.
&lt;span class=&quot;mt-export2wp&quot;&gt;&lt;/span&gt;
The problem with unlicensed white space devices is - not being glib - that they are unlicensed. That means that in the event of interference problems, there is little or nothing that can (or will) be done by the FCC. In the unlikely event that the source of interference is located - *very* difficult at best, even supposing the FCC would attempt it - there isn&#039;t much that can be done. No license to revoke, and no way to prevent the user from obtaining another device even if their is confiscated (extremely unlikely), so what does that leave, sending them to bed early?
&lt;span class=&quot;mt-export2wp&quot;&gt;&lt;/span&gt;
The regulatory debacle that was CB radio, and the present-day problems with marine emergency radio services being disrupted by truck drivers using marine transceivers as long-range CB&#039;s are only two examples of the FCC&#039;s lack of ability or desire to conduct serious interference enforcement, so it&#039;s hard to see white space devices being any more carefully overseen.
&lt;span class=&quot;mt-export2wp&quot;&gt;&lt;/span&gt;
The &quot;safe zone&quot; idea is at best naive; users of white space devices are likely to take them wherever they wish, totally disregarding the &quot;safe zones&quot; - supposing they even know where the &quot;safe zones&quot; are in the first place.
&lt;span class=&quot;mt-export2wp&quot;&gt;&lt;/span&gt;
Please understand that I&#039;m not saying white space devices can&#039;t or shouldn&#039;t exist; I see them as a huge boon, but simply believe that in its rush to bring this service into being, the FCC has failed to correctly assess the real-world implications and put in place measures that will assure peaceful coexistence between the new devices and those already in service.
&lt;span class=&quot;mt-export2wp&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;mt-export2wp&quot;&gt;&lt;/span&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;m a career broadcast engineer, and what I am about to say comes from 35 years of dealing with interference issues, not out of any provincial turf-defending viewpoint. My job is to make things work, not to prevent them from working.<br />
<span class="mt-export2wp"></span><br />
Identifying sources of interference and resolving the problems is usually a difficult task at best. The concept that exists in most peoples&#8217; minds of riding around with a magical direction-finding device, quickly locating the interfering device and having it shut off is really a fantasy. In reality, most interference is hard to pinpoint (even when from a stationary source) and having it shut off is fraught with legal and practical difficulties.<br />
<span class="mt-export2wp"></span><br />
The problem with unlicensed white space devices is &#8211; not being glib &#8211; that they are unlicensed. That means that in the event of interference problems, there is little or nothing that can (or will) be done by the FCC. In the unlikely event that the source of interference is located &#8211; *very* difficult at best, even supposing the FCC would attempt it &#8211; there isn&#8217;t much that can be done. No license to revoke, and no way to prevent the user from obtaining another device even if their is confiscated (extremely unlikely), so what does that leave, sending them to bed early?<br />
<span class="mt-export2wp"></span><br />
The regulatory debacle that was CB radio, and the present-day problems with marine emergency radio services being disrupted by truck drivers using marine transceivers as long-range CB&#8217;s are only two examples of the FCC&#8217;s lack of ability or desire to conduct serious interference enforcement, so it&#8217;s hard to see white space devices being any more carefully overseen.<br />
<span class="mt-export2wp"></span><br />
The &#8220;safe zone&#8221; idea is at best naive; users of white space devices are likely to take them wherever they wish, totally disregarding the &#8220;safe zones&#8221; &#8211; supposing they even know where the &#8220;safe zones&#8221; are in the first place.<br />
<span class="mt-export2wp"></span><br />
Please understand that I&#8217;m not saying white space devices can&#8217;t or shouldn&#8217;t exist; I see them as a huge boon, but simply believe that in its rush to bring this service into being, the FCC has failed to correctly assess the real-world implications and put in place measures that will assure peaceful coexistence between the new devices and those already in service.<br />
<span class="mt-export2wp"></span><br />
<span class="mt-export2wp"></span></p>
]]></content:encoded>
	</item>
</channel>
</rss>

