public inbox for wireless-regdb@lists.infradead.org
 help / color / mirror / Atom feed
From: Nathaniel Chin <thegamingorangutans@gmail.com>
To: wens@kernel.org
Cc: linux-wireless@vger.kernel.org, wireless-regdb@lists.infradead.org
Subject: Re: wireless-regdb: Inaccurate regulatory rules for Brunei (BN)
Date: Mon, 12 Aug 2024 17:22:15 +0800	[thread overview]
Message-ID: <53f4f012-a454-443b-a2de-6151752fa5db@gmail.com> (raw)
In-Reply-To: <CAGb2v64OsGpERdrojMgfbQspk_vwsm-X16Nj4ntvN+1azaEM9w@mail.gmail.com>

Hi,

> Thank you for reporting this. I currently cannot open the 2014-2015
> document, nor the underlying website. It seems I am blocked.
I also seem to be unable to access the entire aiti.gov.bn domain as a 
whole as well but this specific document hasbeen archived in archive.org 
<https://web.archive.org/web/20240724130146/https://www.aiti.gov.bn/media/voqau1jw/brunei-darussalam-radio-spectrum-plan-2014-2015.pdf>

> the 2018 document reports two
> limits: 100 mW and 1000 mW. Do you know what that is about?
Unfortunately, no

I've found another document 
<https://web.archive.org/web/20240724125731/https://www.aiti.gov.bn/media/qjchjoni/code-of-practice-for-srd.pdf> 
(appears to be un-dated) which makes specific mention of DFS and TPC.

Best regards,
Nathaniel

On 12/8/2024 4:19 pm, Chen-Yu Tsai wrote:
> Hi,
>
> On Tue, Aug 6, 2024 at 12:51 PM Nathaniel Chin
> <thegamingorangutans@gmail.com> wrote:
>> Hi,
>>
>> I've noticed that the current values in the regdb for Brunei do not
>> match with the Brunei Darussalam Radio Spectrum Plan (2014-2015 version)
>> <https://www.aiti.gov.bn/media/voqau1jw/brunei-darussalam-radio-spectrum-plan-2014-2015.pdf>
>> and the Telecommunications (Exemption from Sections 33,34(1)(b) and 35)
>> Notification, 2018
>> <https://www.agc.gov.bn/AGC%20Images/LAWS/Gazette_PDF/2018/S039.pdf>.
>>
>> Which both state that the authorised bands are: 2.4000 - 2.4835 GHz at a
>> max of 200 mW; 5.150-5.350 GHz at a max of 1000 mW (2018 document); and
>> 5.725 - 5.850 GHz at a max of 1000/4000 mW (with the latter requiring a
>> license).
> Thank you for reporting this. I currently cannot open the 2014-2015
> document, nor the underlying website. It seems I am blocked.
>
> Regardless, the values you report align with the 2018 document. One
> oddity is that for 5.150-5.350 GHz, the 2018 document reports two
> limits: 100 mW and 1000 mW. Do you know what that is about?
>
>> Additionally the 2015 document refers to FCC and ETSI regulations and I
>> don't see any mention of Japanese regulations?
> This is from an old change that added DFS-JP and associated a bunch of
> regions with it. There was no reference given.
>
> Without access to the 2015 document I have no idea what the DFS requirements
> are. They could also be under some technical specification that describes
> the test methods for compliance.
>
>
> Thanks
> ChenYu
>
>> Best regards,
>> Nathaniel Chin
>>
>> P.S I've had to resend this email because initially it was sent as HTML
>> instead of plain text so if you've received two copies: sorry.
>>



      reply	other threads:[~2024-08-12 11:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-05 18:17 wireless-regdb: Inaccurate regulatory rules for Brunei (BN) Nathaniel Chin
2024-08-12  8:19 ` Chen-Yu Tsai
2024-08-12  9:22   ` Nathaniel Chin [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=53f4f012-a454-443b-a2de-6151752fa5db@gmail.com \
    --to=thegamingorangutans@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wens@kernel.org \
    --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