[CRTech] Christian Radio Tech [MSG 82777]
[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: Sherrod Munday <smunday@ieee.org>
Date: Thu, 26 Apr 2018 17:56:02 -0400
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ieee-org.20150623.gappssmtp.com; s=20150623; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=cyYDDGKvJMfNCW9SWIRlgY78gslg2kQLueHvHm0SLVI=; b=wU49Wf4zMG/bYi0jd0gKBhHZDi3cJ+F38ho8Mk+tD5vLLHPFbZchgh3Pf0Bq7/YeDS 0Sz+feV6feUWsEcIoQ0i6HyBrfAfCPWDUrotwCB2AMDqeN3hMebNjm3ntL+eNZYQ/51E 206n3hnf4atjAuRXvaWI520Zeg/fLg+8oTWyUVmQt7TOiNfl2WEdDOdXgk1Qo2j9Trnf F475KNQU8S+AlPGJiiyD/S8IYuBV3x3ZwDYvU7bIVVJawQQMX8YPNvTMVjt0hZ+CRdcP wzFRmKNuqhvi/tiYnfb3qth+U+wLWatIoTbdjBtuH18p6MOKfFPzRAa3ay+JK9CucKD5 ckSg==
In-reply-to: <0ABEFD45-74CE-44F0-A8A6-1CAFAF91083C@paravelsystems.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> <005101d3dcab$6fb668a0$4f2339e0$@icloud.com> <EEBEE694-91EC-40D3-9988-821E4F997AEF@ieee.org> <CAA8ua=wmQLZhaTrBpHn9Pj0o8mwMjw9MnPS=H7GXBevmvHu-wQ@mail.gmail.com> <96E5AAA5-0785-4F7F-A0B4-9E7FAD4E2756@ieee.org> <008c01d3dcc1$7cfc1350$76f439f0$@icloud.com> <dc3ddb89-2d0e-f894-2583-7107271ea680@whwl.net> <0ABEFD45-74CE-44F0-A8A6-1CAFAF91083C@paravelsystems.com>
On Apr 26, 2018, at 14:10, Fred Gleason <fredg@paravelsystems.com> wrote:
...Make no mistake: this is an existential threat so far as the C-band satellite operators are concerned. Such service will no longer be practically feasible in that band in any long-term sense if the proposals as they currently stand are adopted.

This is *precisely* the reason that everyone should “speak up” now and -- at the very least -- register the existence of C-band satellite downlinks.  

If enough sites in or near urban areas are additionally registered to protect against interference, [we can hope that] there will be enough interference protection afforded by the overlapping coverage as to make it impractical for any WISP to attempt to set up a network in that frequency range.

I’ve attached a snapshot from our recent application.  Note that the final contour is rather large.  Put a bunch of these in any one area, and it would make new sites that would conflict with existing downlink usage pretty tough to justify for a new entrant.  

One additional note: 
For anyone who’s not been registered before and who’s planning on submit a frequency coordination study and apply for protection, it will put the registered email and/or postal address into the system to get notified any time that someone in your protection area (the great circle) wants to do something that could conflict with your registered frequency.  

Prior Coordination Notices (“PCN”) usually include some language like “…and no interference is expected to your system…” 

If you disagree with that assertion by the filing entity (and their frequency coordinator), the burden is on you (the licensee) to provide a technical basis for your objection.  If you fail to respond, they automatically assume that you have no objection.  Typical response times are around 30 days, but in expedited cases you may only have 10 days to respond.

Realize that you may need to technically defend your position that any proposed new use might cause interference, so you may want to keep a good relationship with your frequency coordinator (e.g. Comsearch, Micronet, etc.) in case the need arises.


For your reference (speaking to those of you who are not already registered and receiving such notices), I’ve attached a set of files that typically come with a PCN for a new frequency use from Comsearch.  Notice that this particular one for T-Mobile is for a set of 6 GHz and 10/11 GHz transmit frequencies.  I’ve also included a separate PCN from Micronet for a 6GHz link.



On to the docs:

PNG image



Attachment: 180130COMSRP03_Letter.pdf
Description: Adobe PDF document

Attachment: 180130COMSRP03_DataSheet.pdf
Description: Adobe PDF document

Attachment: 180130COMSRP03.kml
Description: application/vnd.google-earth.kml

Attachment: M1534401 L6 GHz datasheets.pdf
Description: Adobe PDF document


--
Sherrod Munday

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
(nathaniel.steele@icloud.com, 25 Apr 2018 15:38:30 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(Sherrod Munday <smunday@ieee.org>, 25 Apr 2018 17:19:23 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(Pat Wahl <pwahl@wwib.com>, 25 Apr 2018 17:44:04 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(Sherrod Munday <smunday@ieee.org>, 25 Apr 2018 17:58:42 -0000)
RE: SBE Regulatory Alert - Apr 23, 2018
(nathaniel.steele@icloud.com, 25 Apr 2018 18:16:18 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(Andy Larsen <andy@whwl.net>, 26 Apr 2018 17:17:17 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(Fred Gleason <fredg@paravelsystems.com>, 26 Apr 2018 18:11:06 -0000)
Prev by date: Re: Why Don't I see Turbo's Post's?
(Sherrod Munday, 26 Apr 2018 21:22:02 -0000)
Next by date: RE: Why Don't I see Turbo's Post's?
(nathaniel . steele, 26 Apr 2018 22:13:58 -0000)
Prev by thread: Re: SBE Regulatory Alert - Apr 23, 2018
(dave allen, 26 Apr 2018 18:35:03 -0000)
Next by thread: Re: SBE Regulatory Alert - Apr 23, 2018
(harlanreinders, 26 Apr 2018 20:01:52 -0000)
CRTech.org