public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: Robert Marko <robert.marko@sartura.hr>
Cc: wireless-regdb@lists.infradead.org,
	linux-wireless@vger.kernel.org,
	Luka Perkov <luka.perkov@sartura.hr>
Subject: Re: [PATCH] wireless-regdb: Update regulatory rules for Croatia (HR)
Date: Tue, 10 Nov 2020 08:28:03 -0600	[thread overview]
Message-ID: <20201110142803.GK6125@ubuntu-x1> (raw)
In-Reply-To: <CA+HBbNHfxt7pggPDtz2gTyg74OD9KmYto7-Lck3qF_pTGvuQqQ@mail.gmail.com>

On Tue, Nov 10, 2020 at 11:35:38AM +0100, Robert Marko wrote:
> On Tue, Nov 10, 2020 at 12:16 AM Seth Forshee
> <seth.forshee@canonical.com> wrote:
> >
> > On Sun, Sep 13, 2020 at 07:21:40PM +0200, Robert Marko wrote:
> > > Croatian Regulatory Authority for Network Industries (HAKOM) has
> > > updated the general licenses OD-85 and OD-86 with the new OD-85a
> > > and OD-86a versions.
> > >
> > > These introuduce the following changes:
> > > * Outdoor usage for 5150-5250 and 5250-5350 MHz ranges is permitted
> > > * 5150-5250 MHz range TPC requirment was dropped and power output raised to 200mW
> > >
> > > OD-85a: https://www.hakom.hr/UserDocsImages/op%C4%87e%20dozvole%20prosinac%202009.g/Opca_dozvola_85a.pdf
> > > OD-86a: https://www.hakom.hr/UserDocsImages/op%C4%87e%20dozvole%20prosinac%202009.g/Opca_dozvola_86a.pdf
> > >
> > > Signed-off-by: Robert Marko <robert.marko@sartura.hr>
> > > Cc: Luka Perkov <luka.perkov@sartura.hr>
> > > ---
> > >  db.txt | 4 ++--
> > >  1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/db.txt b/db.txt
> > > index ac32483..52d0fab 100644
> > > --- a/db.txt
> > > +++ b/db.txt
> > > @@ -693,8 +693,8 @@ country HR: DFS-ETSI
> > >  # Harmonized CEPT countries (July 2019): https://www.ecodocdb.dk/download/25c41779-cd6e/Rec7003e.pdf
> > >  # HR: http://tablice.hakom.hr:8080/vis?lang=en
> > >       (2400 - 2483.5 @ 40), (100 mW)
> > > -     (5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW, wmmrule=ETSI
> > > -     (5250 - 5350 @ 80), (100 mW), NO-OUTDOOR, DFS, AUTO-BW, wmmrule=ETSI
> > > +     (5150 - 5250 @ 80), (200 mW), AUTO-BW, wmmrule=ETSI
> >
> > Based on the translation I'm reading the 200 mW applied to elevations
> > from 5 degrees to 30 degrees, and for elevations above 30 degress the
> > limit is 125 mW. I'm not expeienced with regulations that vary with the
> > elevation angle. Why should we use 200 mW instead of 125 mW, which is
> > allowed for any elevation?
> 
> You can see in the OD-86a that now 1W (30 dBm) EIRP is the maximum
> allowed power.
> Then in usage conditions, they state that if median EIRP power larger
> than 200mW (23 dBm) is used then the listed
> angle and power limits should be used.
> That is why I used 200mW as it has no limitations associated.

Right, but OD-86a applies to 5250-5350 MHz. I don't see this same
statement in OD-85a.

However, digging into it a little more, it looks like the elevation
restrictions come from WRC-19 resolution 229 [1], which has more detail.
Based on my reading of that it seems that the situation here actually is
similar to that for 5250-5350 MHz, i.e. that 200 mW is the general limit
but that operation at 1W is allowed subject to the stated elevation
angle restrictions. So it sounds like the 200 mW limit for 5150-5250 MHz
should be okay.

[1] https://www.itu.int/dms_pub/itu-r/opb/act/R-ACT-WRC.14-2019-PDF-E.pdf

> >
> > > +     (5250 - 5350 @ 80), (200 mW), DFS, AUTO-BW, wmmrule=ETSI
> >
> > The translation of OD-86a I'm reading says "use mostly indoors." Is that
> > an accurate translation? How does this compare to the language from
> > OD-86? I'm a little unsure how to interpret it.
> 
> Yes, it's accurate.
> In OD-86 this was strictly written as "exclusive use indoors", Hakom
> even stated in their press release that the
> changes to OD-86 now allow outdoor usage.
> https://www.hakom.hr/default.aspx?id=10442
> It's in English.
> 
> They are just trying to encourage the band to still be mostly used for
> indoor stuff.

Great, thanks for clarifying.

I've applied the patch. Thanks!

  reply	other threads:[~2020-11-10 14:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-13 17:21 [PATCH] wireless-regdb: Update regulatory rules for Croatia (HR) Robert Marko
2020-11-09 23:16 ` Seth Forshee
2020-11-10 10:35   ` Robert Marko
2020-11-10 14:28     ` Seth Forshee [this message]
2020-11-10 15:22       ` Robert Marko
  -- strict thread matches above, loose matches on Subject: below --
2015-10-13 18:31 Andrej Vlasic
2015-10-15 18:04 ` Seth Forshee
2015-10-18 19:44   ` Andrej Vlašić
2015-10-22 15:00     ` Seth Forshee

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201110142803.GK6125@ubuntu-x1 \
    --to=seth.forshee@canonical.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luka.perkov@sartura.hr \
    --cc=robert.marko@sartura.hr \
    --cc=wireless-regdb@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox