From: Dave Taht <dave.taht@gmail.com>
To: J Ignacio Alvarez-Hamelin <ihameli@cnet.fi.uba.ar>
Cc: Sebastian Moeller <moeller0@gmx.de>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
tsvwg IETF list <tsvwg@ietf.org>, IETF IPPM WG <ippm@ietf.org>,
Rpm <rpm@lists.bufferbloat.net>,
Glenn Fishbine <glenn@breakingpointsolutions.com>,
Measurement Analysis and Tools Working Group <mat-wg@ripe.net>,
discuss <discuss@measurementlab.net>
Subject: Re: [Starlink] [mat-wg] [ippm] [Rpm] [M-Lab-Discuss] misery metrics & consequences
Date: Wed, 26 Oct 2022 01:14:40 -0700 [thread overview]
Message-ID: <CAA93jw51DO1ABNeC0sJ=e_3V7Gxt-YjmiR2+SB_tj14fh-6ATg@mail.gmail.com> (raw)
In-Reply-To: <F290B086-FDDC-4C9E-AD46-3BAC446BD8C4@cnet.fi.uba.ar>
To add some context to this enormous cross post of mine, to try and
get folk here to think further out of the box,
the FCC is due to announce how "consumer broadband labels" are
supposed to work on Nov 15th. Nobody knows
what they are going to announce.
Their first attempt was laughable, the laughs in this attempt (which
is admittedly much better), are subtler.
https://www.benton.org/blog/consumer-driven-broadband-label-design
I liked how they leveraged waveform's categories in this one.
I (cynically) loved how the delay and loss both grew in this example,
where loss should increase with less delay in most circumstances.
Perhaps consumers can be trained to look for high loss and low delay,
but I doubt it.
--
This song goes out to all the folk that thought Stadia would work:
https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
Dave Täht CEO, TekLibre, LLC
next prev parent reply other threads:[~2022-10-26 8:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 21:04 [Starlink] " Dave Taht
2022-10-21 23:50 ` Dave Taht
2022-10-25 6:15 ` [Starlink] [Rpm] " Taraldsen Erik
2022-10-22 20:18 ` [Starlink] [M-Lab-Discuss] " rjmcmahon
2022-10-22 21:00 ` [Starlink] " Dave Collier-Brown
2022-10-22 22:18 ` Dave Taht
2022-10-23 0:17 ` [Starlink] [M-Lab-Discuss] " Glenn Fishbine
2022-10-23 11:57 ` [Starlink] [Rpm] " Sebastian Moeller
2022-10-23 12:17 ` Dave Collier-Brown
2022-10-23 12:26 ` Sebastian Moeller
2022-10-23 13:11 ` Dave Collier-Brown
2022-10-23 13:52 ` Sebastian Moeller
2022-10-23 14:00 ` Dave Collier-Brown
2022-10-23 14:08 ` Sebastian Moeller
2022-10-23 14:08 ` Dave Collier-Brown
2022-10-23 15:01 ` tom
2022-10-24 20:08 ` Christoph Paasch
2022-10-24 20:57 ` Sebastian Moeller
2022-10-24 23:44 ` Christoph Paasch
2022-10-25 0:08 ` rjmcmahon
2022-10-25 0:12 ` rjmcmahon
2022-10-25 2:28 ` [Starlink] [tsvwg] " Neal Cardwell
2022-10-25 15:17 ` [Starlink] [Rpm] [tsvwg] " rjmcmahon
2022-10-31 8:59 ` [Starlink] [ippm] [tsvwg] [Rpm] " Ruediger.Geib
2022-10-25 15:50 ` [Starlink] [ippm] " J Ignacio Alvarez-Hamelin
2022-10-26 8:14 ` Dave Taht [this message]
2022-10-25 16:07 ` J Ignacio Alvarez-Hamelin
2022-10-25 17:02 ` [Starlink] [Rpm] [ippm] " rjmcmahon
2022-10-25 20:17 ` J Ignacio Alvarez-Hamelin
2022-10-24 17:37 ` [Starlink] " Dave 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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw51DO1ABNeC0sJ=e_3V7Gxt-YjmiR2+SB_tj14fh-6ATg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=discuss@measurementlab.net \
--cc=glenn@breakingpointsolutions.com \
--cc=ihameli@cnet.fi.uba.ar \
--cc=ippm@ietf.org \
--cc=mat-wg@ripe.net \
--cc=moeller0@gmx.de \
--cc=rpm@lists.bufferbloat.net \
--cc=starlink@lists.bufferbloat.net \
--cc=tsvwg@ietf.org \
/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