From: "seth.forshee" <seth.forshee@canonical.com>
To: b.K.il.h.u+tigbuh@gmail.com
Cc: "junping.xu@jaguarwave.com" <junping.xu@jaguarwave.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
wireless-regdb <wireless-regdb@lists.infradead.org>
Subject: Re: [wireless-regdb] wireless-regdb: Please update regulatory rules for Japan (JP) on 60GHz
Date: Wed, 15 May 2019 08:15:33 -0500 [thread overview]
Message-ID: <20190515131533.GZ4357@ubuntu-xps13> (raw)
In-Reply-To: <CAPuHQ=EvWzXtxk0fLOT6PyeYkcNOOXmw0ck-yT-JsqhhDmu2gA@mail.gmail.com>
On Fri, Apr 26, 2019 at 12:00:22AM +0200, b.K.il.h.u+tigbuh@gmail.com wrote:
> This seems to be the page for the previous standard:
> https://www.arib.or.jp/english/std_tr/telecommunications/std-t74.html
>
> And the following should be the new standard, but I don't know where
> to obtain it:
> https://www.arib.or.jp/english/std_tr/telecommunications/std-t117.html
>
> The description fields here do note the range of 57-66GHz, though:
> https://www.arib.or.jp/kikaku/kikaku_tushin/desc/std-t117.html
> https://webstore.arib.or.jp/en/products/detail.php?product_id=288
>
> Similar mentions in the news (search for T117):
> https://www.arib.or.jp/image/osirase/news/1044.pdf
> https://www.arib.or.jp/image/iinkai/kikaku-kaigi/rireki/101.pdf
>
> Testing procedure is described here, not sure if it's considered useful:
> file:///home/bkil/chrome.root/Downloads/60ghz2_1_19_4_2_1.pdf
Thanks. Judging by these and numerous other third-party resources I've
found, I think it's safe to say that the range was expanded back to 57
GHz quite some time ago. I'll send a patch to update this range.
Seth
prev parent reply other threads:[~2019-05-15 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2019040118074276659215@jaguarwave.com>
2019-04-08 12:48 ` wireless-regdb: Please update regulatory rules for Japan (JP) on 60GHz seth.forshee
2019-04-25 22:00 ` [wireless-regdb] " b.K.il.h.u+tigbuh
2019-04-25 22:01 ` b.K.il.h.u+tigbuh
2019-05-15 13:15 ` 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=20190515131533.GZ4357@ubuntu-xps13 \
--to=seth.forshee@canonical.com \
--cc=b.K.il.h.u+tigbuh@gmail.com \
--cc=junping.xu@jaguarwave.com \
--cc=linux-wireless@vger.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