[CRTech] Christian Radio Tech [MSG 82806]
[Thread Prev] [-- Thread Index --] [Thread Next] [Date Prev] [-- Date Index --] [Date Next]
Re: SBE Regulatory Alert - Apr 23, 2018
To: CRTech <crtech@crtech.org>, James Richardson <jreelectronics@gmail.com>
Subject: Re: SBE Regulatory Alert - Apr 23, 2018
From: dave allen <crtech-mail@reyware.us>
Date: Fri, 27 Apr 2018 19:10:28 -0600
Content-language: en-US
In-reply-to: <CAKr2A_umZjn4KDFGoQvrMgkbQoCT5P+n4bXidrOaJ56f7OF4GA@mail.gmail.com>
References: <CAAthHBZBXWTdLRxSXhgciKCOeariGQkiSN0xgHZFbMMgCUDEoQ@mail.gmail.com> <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> <CAA8ua=x1EOfRNJ3SvOZPQsut5NDp-ZqxoWBxq42p059N8swzkg@mail.gmail.com> <CAKr2A_umZjn4KDFGoQvrMgkbQoCT5P+n4bXidrOaJ56f7OF4GA@mail.gmail.com>
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
well, and seems to me the Ku band is already pretty full. too full to absorb all the c-band traffic if that's the way they go. and you ca only put so many satellites up there, unless they go with 1-degree. yipes...

dave allen

On 4/27/2018 2:21 PM, James Richardson wrote:
Trouble with KU is the wavelength, especially in snow and rain fade conditions.  Also there is a lot of money
that has been invested in receivers and uplinks.

In other words, my head hurts!


On Fri, Apr 27, 2018 at 4:16 PM, Pat Wahl <pwahl@wwib.com> wrote:
Here's part of why this is muddy and scary. Consider this snippet from
the recent Radio World interview quoting commissioner O'Reilly:

"I’m looking at how we would best go about the 3.7 to 4.2, how would
we make that happen without disrupting service to local broadcasters.

You also raised the point: We don’t know exactly who’s operating
today. You get interference protection if you’re registered; you don’t
if you aren’t. We’re trying to figure out how we protect those we
don’t know about. “Tell us if you exist.” It’s hard to protect people
we don’t know about.

C Band, itself, may not be the way to offer service. Maybe it could be
done through fiber. It can be other bands, satellite. I’m open to
looking at different ways to make sure that broadcasters — or whomever
is operating in the band, there are multiple players — aren’t
disrupted and are not harmed in the process."

So, commissioner O'Reilly is saying service to radio stations should
maybe be removed from C Band. But, then he suggests fiber, other bands
and satellite. The text almost makes it look like he is treating us as
terrestrial and not satellite. Either way, he is for moving radio
elsewhere, maybe from C Band to Ku? Based on this, I wouldn't entirely
trust even the full registration with study to protect our C Band
future. At the same time, I am not suggesting anyone wait this out by
not registering.

Pat

On Fri, Apr 27, 2018 at 2:52 PM, James Richardson
<jreelectronics@gmail.com> wrote:
> 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
>>
>>
>

---------------------------------------------------------------------
For CRTech resources visit http://CRTech.org/
To unsubscribe, e-mail: crtech-unsubscribe@crtech.org
List problems?  E-mail: TechStaff@CRTech.org



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
(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)
Re: SBE Regulatory Alert - Apr 23, 2018
(Pat Wahl <pwahl@wwib.com>, 27 Apr 2018 20:16:50 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(James Richardson <jreelectronics@gmail.com>, 27 Apr 2018 20:22:10 -0000)
Prev by date: Re: Re: Remotes
(Bob Morris, 28 Apr 2018 00:04:32 -0000)
Next by date: Re: Re: Remotes
(Alex McKenzie, 28 Apr 2018 13:25:24 -0000)
Prev by thread: Re: SBE Regulatory Alert - Apr 23, 2018
(James Richardson, 27 Apr 2018 20:22:10 -0000)
Next by thread: Re: SBE Regulatory Alert - Apr 23, 2018
(JIm Turvaville, 27 Apr 2018 20:20:59 -0000)
CRTech.org