From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: "Dave Taht" <dave.taht@gmail.com>,
m.seliuchenko@gmail.com, mykola.i.beshlei@lpnu.ua,
elhadi.shakshuki@acadiau.ca, halink@ukr.net,
natalia.kryvinska@univie.ac.at,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
ansar.yasar@uhasselt.be
Subject: Re: [Cerowrt-devel] smart queue management conflict
Date: Mon, 22 Mar 2021 21:41:46 -0400 [thread overview]
Message-ID: <324730.1616463706@turing-police> (raw)
In-Reply-To: <1616460650.275121342@apps.rackspace.com>
[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]
On Mon, 22 Mar 2021 20:50:50 -0400, "David P. Reed" said:
> Let's say I have a sensor on my dog's collar, or on a fork lift in a
> warehouse? Do these researchers honestly think that each sensor will make a
> *phone call* over the LTE fabric and continue that phone call for all the time
> the device is powered on? Is the cost going to be proportional to the delivered
> bit-rate? In "message units" for each 3 minutes of call time?
You turn on almost any media, and get to see ads for Ring doorbells and other
IoT things that don't report to a smart-home-hub on the local home network, but
to someplace where corporate interests can monetize the data. So yes, the
researchers honestly think that's a sustainable model.
I'm still trying to figure out how the <expletive> you monetize data from a
Roomba, unless they're looking at the coverage patterns and using them to
figure out how big your residence is and how much furniture you have, and using
that to estimate income and/or need for new/more furniture...
[-- Attachment #2: Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2021-03-23 1:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 5:28 Dave Taht
2021-03-23 0:50 ` David P. Reed
2021-03-23 1:41 ` Valdis Klētnieks [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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=324730.1616463706@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=ansar.yasar@uhasselt.be \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=dpreed@deepplum.com \
--cc=elhadi.shakshuki@acadiau.ca \
--cc=halink@ukr.net \
--cc=m.seliuchenko@gmail.com \
--cc=mykola.i.beshlei@lpnu.ua \
--cc=natalia.kryvinska@univie.ac.at \
/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