From: Harshal Chhaya <harshal@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] fcc vote on 6ghz thursday
Date: Thu, 23 Apr 2020 09:32:25 -0500 [thread overview]
Message-ID: <CAJ8GFOiJVkxToUBcFjvAeRfQHk7EBmBjorFrAfkUZs+qqrXryA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6myLKvyd-dxVVmd3-=EOOQ+dVmmGqsJp0Unb-sex_euA@mail.gmail.com>
FYI - you can listen to today's FCC meeting at https://www.fcc.gov/general/live
On Wed, Apr 22, 2020 at 12:33 PM Dave Taht <dave.taht@gmail.com> wrote:
>
> H/T to james. First reading - ALL wifi 6ghz access points need to
> report their location to a centralized FCC database
> via a yet to be written "AFC" system. Hmmm...
>
> more:
>
> https://docs.fcc.gov/public/attachments/DOC-363490A1.pdf (linked from
> here: https://www.fcc.gov/document/promoting-unlicensed-use-6-ghz-band-0)
>
> Draft rules are in appendix A. They could have changed slightly
> between the agenda release on Apr 2, and the meeting/vote tomorrow.
> Final version will be published after the meeting tomorrow. Don't ask
> me how long that takes.
>
> For the very high level summary of the four operating modes, see III
> A, III B, IV A and IV B in the Table of Contents.
>
> III. Report and Order:
> A. Standard-Power Operations in U-NII-5 and U-NII-7 Bands
> B. Low-Power Indoor Operations Across the Entire 6 GHz Band
> IV. Further Proposed:
> A. Very Low Power Operation
> B. Higher Power Spectral Density for Low Power Indoor Operations
>
>
> https://docs.fcc.gov/public/attachments/DOC-363490A1.pdf
>
> On Wed, Apr 22, 2020 at 8:17 AM Dave Taht <dave.taht@gmail.com> wrote:
> >
> > I just wish I knew what was required for an open source maker of
> > outdoor capable APs had to do. So far I haven't found the draft
> > rules...
> >
> > It sounded to me that outdoor use required use of a gps and active
> > ongoing registration into some FCC database.
> >
> > https://www.fiercewireless.com/regulatory/fcc-sets-all-1-200-mhz-motion-for-6-ghz-unlicensed
> >
> > “We’re stoked about what the 6 GHz band can do,” he told Fierce.
> > “Imagine getting 2 Gbps on your phone, that’s something Wi-Fi 6E and 6
> > GHz can accomplish,” as well as produce latency on the order of 2
> > milliseconds or less, which is why it’s so attractive for things like
> > AR/VR."
> >
> >
> >
> > --
> > Make Music, Not War
> >
> > Dave Täht
> > CTO, TekLibre, LLC
> > http://www.teklibre.com
> > Tel: 1-831-435-0729
>
>
>
> --
> Make Music, Not War
>
> Dave Täht
> CTO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-831-435-0729
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
next prev parent reply other threads:[~2020-04-23 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 15:17 Dave Taht
2020-04-22 17:32 ` Dave Taht
2020-04-23 14:32 ` Harshal Chhaya [this message]
2020-04-23 15:05 ` Dave Taht
2020-04-23 15:35 ` Isaac Konikoff
2020-04-23 15:35 ` Dave Taht
2020-04-27 17:28 ` James Lepp
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
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ8GFOiJVkxToUBcFjvAeRfQHk7EBmBjorFrAfkUZs+qqrXryA@mail.gmail.com \
--to=harshal@gmail.com \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
/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