General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave.taht@gmail.com>
Cc: "make-wifi-fast@lists.bufferbloat.net"
	<make-wifi-fast@lists.bufferbloat.net>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	fcc@lists.prplfoundation.org, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] RE : Save WiFi from the FCC - DEADLINE is in 3 days *September* 8
Date: Tue, 8 Sep 2015 11:55:58 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1509081151310.8750@uplift.swm.pp.se> (raw)
In-Reply-To: <CAA93jw4JpLyM9ZucuindWvgF+Fxw6gQu0CEbabx_=vQLj09xFw@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1583 bytes --]

On Tue, 8 Sep 2015, Dave Taht wrote:

> Well, no... we need the concept of "the public's" spectrum, also.

What does that mean? Only devices that have FOSS firmware are allowed to 
send in this spectrum?

Because I actually fail to see the fundamental difference to spectrum I 
use to communicate from my purchased devices from VENDOR1 and VENDOR2 that 
I run myself, and my purchased device I use to communicate that are from 
VENDOR1 and VENDOR2 where the device from VENDOR2 is run by a mobile 
provider. I mean, do we rule out wifi networks run by providers?

Now, I will admit that I have no idea how LTE-U looks like on RF, but 
what's so different about it compared to the different other things 
sending in there like Bluetooth and wifi (and wifi has many different 
encodings).

>>> One failed concept in america, at least, is the idea of a commons - as in
>>> a tragedy of the commons - elsewhere, for example, "public lands" are
>>> actually "the queen's" lands and people tend to treat them with more
>>> respect.
>>
>>
>> Yes, in sweden we have something called (translated) "Rights of public
>> access" to land for instance, I'm allowed to go camping in someone elses
>> forest as long as it's noncommercial and I leave it as I found it.
>
> What is the word, actually?

"Allemansrätten". Literally "everymansright".

> Well, pushing the responsibility back on the actual users of the 
> technology is fine by me. Enforcement seems only to be of a concern on 
> the DFS channels around a limited number of airports.



-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

  reply	other threads:[~2015-09-08  9:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAA93jw6y7fNtU_JuQWuue=BvxigH5gXZCSrg85umANXzvXyOuA@mail.gmail.com>
2015-09-05 14:12 ` [Bloat] " Rich Brown
2015-09-05 22:05   ` Dave Taht
2015-09-06  9:02     ` [Bloat] RE : " luca.muscariello
2015-09-08  7:55       ` Dave Taht
2015-09-08  8:22         ` Mikael Abrahamsson
2015-09-08  8:36           ` Dave Taht
2015-09-08  8:55             ` Mikael Abrahamsson
2015-09-08  9:21               ` Dave Taht
2015-09-08  9:55                 ` Mikael Abrahamsson [this message]
2015-09-08 14:45               ` Michael Richardson
2015-09-08 12:13         ` MUSCARIELLO Luca IMT/OLN
2015-09-07 23:12   ` [Bloat] [Cerowrt-devel] " Jonathan Morton
2015-09-08  6:12     ` Rich 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=alpine.DEB.2.02.1509081151310.8750@uplift.swm.pp.se \
    --to=swmike@swm.pp.se \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=fcc@lists.prplfoundation.org \
    --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