From: suchan <abnoeh@mail.com>
To: wireless-regdb@lists.infradead.org
Subject: Re: [wireless-regdb] [PATCH] wireless-regdb: Update regulatory rules for South Korea
Date: Fri, 26 Apr 2019 07:20:41 +0900 [thread overview]
Message-ID: <aed0df90-66cb-c0e9-a3de-95fb19d70960@mail.com> (raw)
In-Reply-To: <6438cda3-169c-be2a-26f7-2ab0780040ea@bowerswilkins.com>
http://www.law.go.kr/%ED%96%89%EC%A0%95%EA%B7%9C%EC%B9%99/%EC%8B%A0%EA%B3%A0%ED%95%98%EC%A7%80%EC%95%84%EB%8B%88%ED%95%98%EA%B3%A0%EA%B0%9C%EC%84%A4%ED%95%A0%EC%88%98%EC%9E%88%EB%8A%94%EB%AC%B4%EC%84%A0%EA%B5%AD%EC%9A%A9%EB%AC%B4%EC%84%A0%EA%B8%B0%EA%B8%B0/(2018-89,20181227)
there is newer version(2018-89) available, and it's copyable by web.
disket button on right top prints the page in one of (hwp,pdf,doc) format
> On 04/25/2019 01:37 PM, b.K.il.h.u+tigbuh@gmail.com wrote:
>> Note that a link to the 2016-124 document is specified as reference in
>> the above code (conversion also attached), not to 2016-125. Should we
>> update the link? Although some of the numbers seem to match, the
>> documents differ in structure and -125 seems to handle more bands.
> I don't know where you downloaded 2016-124, but there is no link to
> 2016-124 one RAA website.
> https://www.rra.go.kr/ko/reference/lawList_view.do?lw_seq=55&lw_type=3&searchCon=&lw_select=ALL&lw_model=&searchTxt=
> Even though 2016-124 exist, we should refer 2016-125 since it's later
> version than -124.
>
> Thanks,
> Peter
> _______________________________________________
> wireless-regdb mailing list
> wireless-regdb@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/wireless-regdb
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
next prev parent reply other threads:[~2019-04-25 22:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 18:34 [wireless-regdb] [PATCH] wireless-regdb: Update regulatory rules for South Korea Peter Oh
2019-04-08 12:41 ` Seth Forshee
2019-04-22 18:04 ` Peter Oh
2019-04-23 20:54 ` b.K.il.h.u+tigbuh
2019-04-24 17:33 ` Peter Oh
2019-04-25 20:37 ` b.K.il.h.u+tigbuh
2019-04-25 22:14 ` Peter Oh
2019-04-25 22:20 ` suchan [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-18 12:15 suchan
[not found] <mailman.11.1556305202.6907.wireless-regdb@lists.infradead.org>
2019-04-26 21:19 ` Peter Oh
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=aed0df90-66cb-c0e9-a3de-95fb19d70960@mail.com \
--to=abnoeh@mail.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