public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Seth Forshee <sforshee@kernel.org>
To: Victor Bayas <victorsbayas@gmail.com>
Cc: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] Update regulatory rules for Ecuador (EC)
Date: Thu, 26 Aug 2021 13:26:53 -0500	[thread overview]
Message-ID: <YSfc7T61r/H9Tz7m@ubuntu-x1> (raw)
In-Reply-To: <CAD+f07-egB+kgjbbY2mN=0KaV+HddQfxRB019o65um3QR4ceaw@mail.gmail.com>

On Thu, Aug 26, 2021 at 11:22:49AM -0500, Victor Bayas wrote:
> My apologies, I forgot to CC the mailing list in my previous reply.
> 
> El jue, 26 de ago. de 2021 a la(s) 09:32, Seth Forshee
> (sforshee@kernel.org) escribió:
> >
> > On Tue, Aug 24, 2021 at 10:14:09PM -0500, Victor Bayas wrote:
> > > Update the frequency ranges and power limits according to the current Ecuadorian norm [1],
> > > corrected 5GHz maximum bandwidth since there are no legal restrictions in this subject.
> > >
> > > Note: 60GHz channels 1 to 3 are allowed without license for Point-to-Point links but
> > > they aren't for Point-to-Multipoint links so they were omitted in this patch.
> > >
> > > [1] https://www.arcotel.gob.ec/wp-content/uploads/2018/04/NORMA-ESPECTRO-DE-USO-LIBRE-Y-ESPECTRO-PARA-USO-DETERMINADO-EN-BANDAS-LIBRES.pdf
> > >
> > > Signed-off-by: Victor Bayas <victorsbayas@gmail.com>
> >
> > Thanks for the patch! A few comments below.
> >
> 
> Thank you for your feedback.
> 
> > > ---
> > >  db.txt | 12 +++++++-----
> > >  1 file changed, 7 insertions(+), 5 deletions(-)
> > >
> > > diff --git a/db.txt b/db.txt
> > > index e7b11cf..4630854 100644
> > > --- a/db.txt
> > > +++ b/db.txt
> > > @@ -504,12 +504,14 @@ country DZ: DFS-JP
> > >       (5250.000 - 5330.000 @ 80.000), (23.00), DFS, AUTO-BW
> > >       (5490.000 - 5670.000 @ 160.000), (23.00), DFS
> > >
> > > +# Source:
> > > +# https://www.arcotel.gob.ec/wp-content/uploads/2018/04/NORMA-ESPECTRO-DE-USO-LIBRE-Y-ESPECTRO-PARA-USO-DETERMINADO-EN-BANDAS-LIBRES.pdf
> > >  country EC: DFS-FCC
> > > -     (2402 - 2482 @ 40), (20)
> > > -     (5170 - 5250 @ 20), (17)
> > > -     (5250 - 5330 @ 20), (24), DFS
> > > -     (5490 - 5730 @ 20), (24), DFS
> > > -     (5735 - 5835 @ 20), (30)
> > > +     (2400 - 2483.5 @ 40), (1000 mW)
> > > +     (5150 - 5250 @ 80), (50 mW), AUTO-BW
> >
> > It looks like 5150-5250 MHz also requires DFS.
> 
> Yes, I tried contacting ARCOTEL without success to get a clarification
> from them because other countries don't require DFS for 5150-5250 MHz.

In the absence of any clarification we should stick with the rules as
documented. The database can always be updated later if it turns out DFS
is not a requirement.

> 
> >
> > > +     (5250 - 5350 @ 80), (250 mW), AUTO-BW, DFS
> > > +     (5470 - 5725 @ 160), (250 mW), DFS
> >
> > 5250-5350 and 5470-5725 MHz require TPC. Since Linux does not support
> > TPC the power limits need to be reduced by 3 dBm, which puts them at 125
> > mW.
> 
> Thanks for the heads up, I forgot there was a TPC requirement.
> 
> >
> > I also don't see any DFS requirement for 5470-5725 MHz.
> 
> Section 2.1.6 says that users of 5250 - 5350 MHz and 5470 - 5725 MHz
> should apply the interference mitigation measures mitigation measures in
> Recommendation ITU-R M.1652 to ensure compatible behavior with
> radiodetermination systems.
> 
> ITU-R M.1652 norm section 1.1 recommends the usage of DFS for
> 5250 - 5350 MHz and 5470 - 5725 MHz, so I inferred the DFS
> requirement for 5470 - 5725 MHz as well.
> 
> https://www.itu.int/dms_pubrec/itu-r/rec/m/R-REC-M.1652-1-201105-I!!PDF-E.pdf

Ah, yes, I missed that.

Thanks,
Seth

      reply	other threads:[~2021-08-26 18:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-25  3:14 [PATCH] Update regulatory rules for Ecuador (EC) Victor Bayas
2021-08-26 14:32 ` Seth Forshee
2021-08-26 16:22   ` Victor Bayas
2021-08-26 18:26     ` Seth Forshee [this message]

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=YSfc7T61r/H9Tz7m@ubuntu-x1 \
    --to=sforshee@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=victorsbayas@gmail.com \
    --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