On Thu, 23 Feb 2012 11:26:45 -0800, Phil Kane
<Phil...@nov.shmovz.ka.pop> wrote:
>On Wed, 22 Feb 2012 22:03:38 -0800, Jeff Liebermann <
je...@cruzio.com>
>wrote:
>
>>>>Public
>>>>safety and land mobile enforcement are certainly under the DHS, as the
>>>>FCC EB won't make a move without prior DHS approval.
>>>
>>>Where are you getting this nonsense from?
>>
>>Personal experience. I've ranted on the topic in the past:
>><
http://groups.google.com/group/alt.internet.wireless/msg/42ec7b6bff63b373>
>>See paragraph starting with "Nope". Bottom line was that the FCC
>>didn't move until DHS was involved. I don't know if DHS was
>>contacted, or if the FCC EB did it on their own.
>
>You are correct that you are ranting, again from a position of little
>or no knowledge of how the FCC operates. You confuse the DHS, a
>cabinet department, with the FCC's Public Safety and Homeland Security
>Bureau (note the correct spelling).
That's possible. The information I received was that the driver of
the monitoring van mentioned that authorization was required from
"Homeland Security" was required before he could engage in any
enforcement actions. He either didn't specify whether it was the FCC
or the Federal bureau, or something got lost in the translation. The
person passing the info to me definitely thought it was the DHS. I
can ask those more closely involved in case I misunderstood.
>There are established enforcement priorities that have existed long
>before "terrorism" was a knee-jerk hot-button thing in the law
>enforcement and political communities. Top of the heap is
>interference to White House Communications. Interference to amateur
>radio is very much down at the bottom of the pile. As a licensed
>amateur operator of 60 years' experience I could wish that it was
>otherwise but it is not.
Yep. However, you might want to read my rant again. The interference
was on the local sheriff's repeater input. Ham radio only became
involved because the local county comm shop somehow decided it must be
caused by hams because it was only one week before Field Day.
Basically, we were asked to help, with an implied (not expressed)
threat that our use of county and state land and facilities might be
jeopardized. My part was figuring out the interference mechanism.
Once that was determined, we arranged to have the frequency monitored
and recorded. Translating the voice inversion scrambled traffic, we
determined that it was fishermen using ham radio equipment on marine
channels. Some direction finding was attempted, with limited results.
Eventually, we found, photographed, and even briefly spoke to the
fishermen in question. All this was passed to the FCC which did
nothing. It was only when we played the terrorist card, did we get
anyone's attention. Of course, little was passed on to the driver of
the monitoring van, who showed up in the afternoon, not knowing that
fishing is usually done in the early morning hours. He heard nothing
and drove back to wherever. The conversation with him, where homeland
security was mentioned, was on his way back.
Let's just say that the general impression and reputation of the FCC
was not exactly enhanced by this incident.
Incidentally, the county comm shop never really understood what was
happening and why. One person continued to blame hams for the
interference, but ceased when the fishermen either stopped using the
offending channel, or sailed away to another location. I may have
helped when I identified the marine radio store that probably had
programmed the radios and explained the him the situation.
>The FCC routinely coordinates enforcement actions with other Federal,
>state, and local agencies and very often acts on cases brought to them
>by those agencies. This is not "being run by" them.
Ok. However, I have only knowledge of this one incident, which did
not require the participation of other agencies.
>As far as the "fisherman" problems go, the last time that the FCC had
>an enforcement boat was in the 1980s, manned by several agents whose
>hobby was sailing. Not my thing.... <G> With the capability ending
>at the dock, it's up to the US Coast Guard to carry the ball, and
>resolving amateur radio interference problems is not on their plate.
The USCG was contacted at one point by someone, who reported back that
they did not have the staff and equipment to deal with small vessel
maritime radios causing interference, and referred us back to the FCC.
They did indicate that if there was to be a vessel boarding by the
FCC, it would desirable, but not necessary for the UCSG to be present.
The FCC web pile isn't very helpful:
<
http://wireless.fcc.gov/services/index.htm?job=operations&id=ship_stations#Ship%20Inspections>
>>I also know of an enforcement action that reeked of local
>>political pressure.
>
>Welcome to the real world of dealing with governments.
Make that about 3 such FCC actions. I'm not sure how it works, but if
the right person pulls the right strings, the FCC EB arrives on
someone's doorstep bearing citations.
Thanks for the info clarifying the FCC EB operation and broadcast
enforcement.