From: Matt Mathis <mattmathis@google.com>
To: davecb@spamcop.net
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] ESR's comment popped up on slashdot
Date: Thu, 8 Oct 2015 09:07:58 -0700 [thread overview]
Message-ID: <CAH56bmBj1y3rYfC62hfiuRxKBBgqvHc_4CO_gHanM5DZZ7gX=w@mail.gmail.com> (raw)
In-Reply-To: <56168961.2080800@rogers.com>
[-- Attachment #1: Type: text/plain, Size: 2505 bytes --]
Perhaps redundant asserts() with explicit documentation would help.
A communication channel with the FAA and wardriving airports would also
help....
Thanks,
--MM--
The best way to predict the future is to create it. - Alan Kay
Privacy matters! We know from recent events that people are using our
services to speak in defiance of unjust governments. We treat privacy and
security as matters of life and death, because for some users, they are.
On Thu, Oct 8, 2015 at 8:18 AM, David Collier-Brown <davec-b@rogers.com>
wrote:
> Solandri wrote, at
> http://tech.slashdot.org/comments.pl?sid=8141531&cid=50686089
>
> So based on a few vague comments, I managed to track down what the issue
> is since neither this nor the previous/. article nor the sites opposed to
> it (who seem to want to portray it as a Big Evil Government conspiracy to
> take away your freedom) delve into it.
>
> Several airports use Terminal Doppler Weather Radar
> <https://en.wikipedia.org/wiki/Terminal_Doppler_Weather_Radar> [
> wikipedia.org] for high-resolution maps of storms, rainfall, and most
> importantly (for airports) microbursts
> <https://en.wikipedia.org/wiki/Microburst>[wikipedia.org]. TDWR operates
> at frequencies from 5.60 - 5.64 GHz. That's smack dab in the middle of the
> 5 GHz band used by 802.11a, n, and ac
> <https://en.wikipedia.org/wiki/List_of_WLAN_channels#5.C2.A0GHz_.28802.11a.2Fh.2Fj.2Fn.2Fac.29.5B16.5D>
> [wikipedia.org]. You'll notice use of those specific frequencies
> (channels 120, 124, 128) are prohibited in the U.S. and Canada for this
> reason.
>
> Based on that, it sounds like the issue is that you can buy a 5 GHz device
> off the shelf, then hack the firmware to re-enable those frequencies. And
> the FCC is proposing this action because people have been doing exactly
> that and the FCC has received reports from the airports of such
> interference on those frequencies.
>
>
> If this is correct, it argues for various of our proposals and opens up
> some new questions...
> - is it a vendor that's scewed it up?
> - was there a bad DD-WRT athe solution is enforcement... anyone
> t any time?
>
>
> --dave
>
> --
> David Collier-Brown, | Always do right. This will gratify
> System Programmer and Author | some people and astonish the restdavecb@spamcop.net | -- Mark Twain
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
>
[-- Attachment #2: Type: text/html, Size: 8745 bytes --]
next prev parent reply other threads:[~2015-10-08 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 14:11 David Collier-Brown
2015-10-08 14:41 ` Eric S. Raymond
2015-10-08 15:18 ` David Collier-Brown
2015-10-08 16:07 ` Matt Mathis [this message]
2015-10-08 19:33 ` Michael Richardson
2015-10-08 19:36 ` Dave Taht
2015-10-08 20:09 ` David Collier-Brown
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH56bmBj1y3rYfC62hfiuRxKBBgqvHc_4CO_gHanM5DZZ7gX=w@mail.gmail.com' \
--to=mattmathis@google.com \
--cc=bloat@lists.bufferbloat.net \
--cc=davecb@spamcop.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