[CRTech] Christian Radio Tech [MSG 82802]
[Thread Prev] [-- Thread Index --] [Thread Next] [Date Prev] [-- Date Index --] [Date Next]
Re: SBE Regulatory Alert - Apr 23, 2018
To: CRTech <crtech@crtech.org>
Subject: Re: SBE Regulatory Alert - Apr 23, 2018
From: JIm Turvaville <jimturbo61@yahoo.com>
Date: Fri, 27 Apr 2018 20:20:51 +0000 (UTC)
Content-length: 11829
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1524860453; bh=NPLbOLJm6lAJvb9zofYMOFlMuQKHbQZfeRQGa0UNegQ=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=Wya3IYLuaxltU/US8fod67/2ymSAgy+PvdOu/iQ9rPipXO/tv2tc2GQ9RBrtgGz7wgHyK9tTyAa1Hm7JyrBddc9Hc2acC5K8hK7wqNXZqyWeXI8IMB2FnXdwlr1GiExdW/R2R+PZDe99DWxu5tYMqy5TS3yRwUyGXcJ7KE5FupcuQlMMc5xprKUdOPc9bkTJgiBX2D4mGEteIHep6FJZqDX7vRlDeX0AYYuEUuspnIY55XuVSohzH6JUhHQRD3gVv7ok8ShyTZpFJTZj+ixc51smwmfvvtRdHOn/FTjpGcZ9+iMNRZUtZnLVMK259J7eX/Iva3rmOwn3WUSRVxLLAQ==
In-reply-to: <CAKr2A_ugku9ZsRROtVZnqBaGvKES3OMdEgAT_8s1OPWi+v+bpg@mail.gmail.com>
References: <CAAthHBZBXWTdLRxSXhgciKCOeariGQkiSN0xgHZFbMMgCUDEoQ@mail.gmail.com> <e058b127-4f6d-941c-9de0-c4a6d04efdff@knlr.com> <332291e1-422a-08a0-9861-d6fffe8a9116@reyware.us> <835ec0ff-912d-a1e7-99a8-9b3306941381@bosscher.org> <DM5PR20MB19778FBA65414B3A6691B8E8A48F0@DM5PR20MB1977.namprd20.prod.outlook.com> <4FF72227-3B28-434E-97FD-CD36031F917A@icloud.com> <BY1PR0801MB096743A01A483E9D47F247A3EF8F0@BY1PR0801MB0967.namprd08.prod.outlook.com> <6B1C3C77-7125-4920-BF82-641C473EC578@ieee.org> <CACci8U7jDGEahmhDSFZjc42hLweFG5u50qcpG67CC2EgK_2jdw@mail.gmail.com> <423C2102-AE5A-43E5-9CFE-F800EDC46DEB@ieee.org> <F67F4BF0-FA5E-4A72-99EE-FCB782292E6F@icloud.com> <003f01d3de54$e380bb00$aa823100$@pilgrimradio.com> <CAKr2A_sZefNrfpS7xDnWmgftrjgceWY7WA4QCjLgqtic2P1spQ@mail.gmail.com> <CAAthHBZ+UJLMQ9JSM==6M3T+P2te=p=3M7d786p_GuYRFPE84g@mail.gmail.com> <CAKr2A_ugku9ZsRROtVZnqBaGvKES3OMdEgAT_8s1OPWi+v+bpg@mail.gmail.com>
Reply-to: JIm Turvaville <jimturbo61@yahoo.com>
Mind you I've not a dog in this hunt - I do not have a downlink of any kind at my radio stations.  

But have many clients who do that are considering what to do in this situation.  I find it hard to counsel a broadcaster in rural West Texas with a single C-band dish receiving WW1 news that he needs to coordinate or register a dish in a location where the possibility of future broadband use of the spectrum is small to nill.  He's struggling enough as it is, without this tossed on top of his financial woes.  

In any urban area, it's blind foolishness not to register your downlink and get some protection; that's where the spectrum is already crammed and getting more every day. 

But the truth is that none of this is "out of the blue", it's always been an FCC regulation that we register our downlink dishes... we just never have done it is all.  

And it's never mattered until now... when the FCC thinks we don't have very many dishes out there because, well, we did not register any of them like we were supposed to. So when someone wants to use that spectrum, the FCC thinks it's not being used because, well, we never registered out dishes with them. 




From: James Richardson <jreelectronics@gmail.com>
To: CRTech <crtech@crtech.org>
Sent: Friday, April 27, 2018 2:52 PM
Subject: Re: [CRTech] SBE Regulatory Alert - Apr 23, 2018

It is still muddy to have to out of the blue, register a receive dish.  Pay to not get interfered with.

Thank you for your input.

J.R.Richardson


On Fri, Apr 27, 2018 at 3:39 PM, Michael Barnes <barnmichael@gmail.com> wrote:
James Richardson,

Actually, there is a lot of programming that does not require any authorization. The uplink provider would have little or no knowledge of all the receivers. In the cases that do require authorization, the only thing the program provider would typically know is the name of the user and the serial number of the receiver. They would have no information on the facility, such as actual dish location, dish technical parameters, etc. Further, the uplink provider is only the licensee of the uplink, not the program provider who is simply passing through his facility.

For example, in the case of the Salem Radio Network, there are something like 13 satellite channels, most of which require no authorization. SRN sends the programming from facilities in Dallas, Texas and Nashville, Tennessee through the MicroSpace uplink facilities in Garner, North Carolina. MicroSpace is the licensee of the uplink, but has zero knowledge of any downlink facilities. The SRN folks keep track of the users of the subscription channels and manage the control channel that authorizes users to receive the paid programming. The only information they have is the user's identification and the serial number of the receiver. The user's address may be very different from the dish location. SRN provides recommended specifications on the user's dish, but otherwise has no knowledge of what the user actually has.

Hope that clears things up for you.

Michael


On Fri, Apr 27, 2018 at 12:18 PM, James Richardson <jreelectronics@gmail.com> wrote:
4.27.2018

So count me in on the confused side.  If the satellite uplink is licensed by the FCC, the uplink facility should have the information
of who is receiving the signal.  I can receive the satellite all day long rf wise, but cannot utilize what is on the signal until the 
satellite master control authorizes my receiver.  

Seems to me that the uplink people should be responsible and not the down link recipients.  My FM yagi in the back yard is not
licensed?

What am I missing?

J.R.Richardson
contract engineer
Westminster, MD




References: SBE Regulatory Alert - Apr 23, 2018
(Michael Barnes <barnmichael@gmail.com>, 24 Apr 2018 22:40:48 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(Terry Cowan <tcowan@knlr.com>, 24 Apr 2018 23:18:55 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(dave allen <crtech-mail@reyware.us>, 24 Apr 2018 23:32:50 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(Tom Bosscher <tom@bosscher.org>, 25 Apr 2018 00:15:38 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(Gregg Richwine <gmsnrich@live.com>, 25 Apr 2018 03:23:29 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(Mark Johnson <linkupsat@icloud.com>, 25 Apr 2018 04:24:39 -0000)
RE: SBE Regulatory Alert - Apr 23, 2018
(Scott Foster <Scott.Foster@SalemMedia.com>, 25 Apr 2018 15:10:32 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(Sherrod Munday <smunday@ieee.org>, 25 Apr 2018 18:00:38 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(Dave Land <dave@klvv.com>, 25 Apr 2018 18:13:43 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(Sherrod Munday <smunday@ieee.org>, 25 Apr 2018 18:34:36 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(Mark Johnson <linkupsat@icloud.com>, 25 Apr 2018 20:53:34 -0000)
RE: SBE Regulatory Alert - Apr 23, 2018
("Bill Hurne" <billhurne@pilgrimradio.com>, 27 Apr 2018 18:24:17 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(James Richardson <jreelectronics@gmail.com>, 27 Apr 2018 19:18:28 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(Michael Barnes <barnmichael@gmail.com>, 27 Apr 2018 19:39:49 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(James Richardson <jreelectronics@gmail.com>, 27 Apr 2018 19:52:25 -0000)
Prev by date: Re: SBE Regulatory Alert - Apr 23, 2018
(Pat Wahl, 27 Apr 2018 20:16:50 -0000)
Next by date: Re: SBE Regulatory Alert - Apr 23, 2018
(James Richardson, 27 Apr 2018 20:22:10 -0000)
Prev by thread: Re: SBE Regulatory Alert - Apr 23, 2018
(dave allen, 28 Apr 2018 01:10:38 -0000)
Next by thread: Re: SBE Regulatory Alert - Apr 23, 2018
(Terry Cowan, 25 Apr 2018 15:50:04 -0000)
CRTech.org