From: Dave Taht <dave.taht@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: make-wifi-fast@lists.bufferbloat.net,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] [Cerowrt-devel] this was a pretty comprehensive guide to how the 5.x spectrum is actually used
Date: Sun, 13 Sep 2015 10:15:32 -0700 [thread overview]
Message-ID: <CAA93jw5gAt0-b5yTJsnNqOVOpa-6AcH0J63UGnHG3SMidH_Nsw@mail.gmail.com> (raw)
In-Reply-To: <73873DE9-F18E-4E2D-8A35-5D79610EF101@gmx.de>
On Sat, Sep 12, 2015 at 11:14 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
> Hi Dave,
>
> On Sep 12, 2015, at 15:52 , Dave Taht <dave.taht@gmail.com> wrote:
>
>> http://apps.fcc.gov/ecfs/document/view?id=7022123531
>>
>> starting at section 2.82 around page 27.
>>
>> based on this, I am inclined to drop the "just fix the weather radars"
>> idea from the fcc comment letter. But a bit more thought and analysis
>> is needed, as to what infringes on th existing bands or not....
>>
>> This one talked about DFS compliance.
>>
>> http://www.erodocdb.dk/Docs/doc98/official/pdf/ECCREP192.PDF
>
> This is pretty rotten, instead of simply harmonizing the regulations world wide, they obviously went for requiring DRM and country codes. As if DVD Blue Ray had not amply proven that that does not work. It would be arguably a better solution to exempt devices from these draconian regulations that simply left the disputed frequencies alone (say by a hardware filter so can only be overridden by soldering). The whole thing is pretty funny when it pretends the solution would be to either impose country regulatory requirements by IP-geolocation or GPS (*). As if both methods were anything close to tamper proof. Not that it matters much I would simply go with heavy fines for people (purposefully) using devices outside of the regulation permitted parameters. In the end the proposed schemes also need a enforcement department and fines to back it up, so why do all the pseudo-technical DRM-done-wrong stuff beforehand… (Especially puzzling why DRM since the radar interference sources seem to allow “triangulating” the source close enough to send in the RF-compliance monitoring vans)
As deeply as I/we care about this stuff... I'd intended the last week
and this one to be a vacation before
starting work in berlin on make-wifi-fast. Since the deadline is still
a ways off, can I encourage y'all to work on the document directly,
adding content such as this?
I'd booked a studio this week to lay down some tracks and resuscitate
my right brain. This track had a few good ideas from the cellist in
it, but fell apart, and needs to get completely reworked starting with
a drum track, and most of the middle lyrics are going to get deleted
in favor of improvisation.
http://snapon.lab.bufferbloat.net/~d/rhysling_new.mp3
And - unless I want to fuel the anger - reading email right now isn't helping.
>
> (*) on the other hand a mandatory GPS receiver in each wlan router should finally settle the getting the correct time in devices without a RTC ;)
>
>>
>> --
>> Dave Täht
>> endo is a terrible disease: http://www.gofundme.com/SummerVsEndo
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
--
Dave Täht
endo is a terrible disease: http://www.gofundme.com/SummerVsEndo
prev parent reply other threads:[~2015-09-13 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-12 13:52 [Make-wifi-fast] " Dave Taht
2015-09-12 18:14 ` [Make-wifi-fast] [Cerowrt-devel] " Sebastian Moeller
2015-09-12 21:37 ` Mikael Abrahamsson
2015-09-13 17:15 ` Dave Taht [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
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=CAA93jw5gAt0-b5yTJsnNqOVOpa-6AcH0J63UGnHG3SMidH_Nsw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
/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