From: "David Fernández" <davidfdzp@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] [Rpm] [Bloat] [LibreQoS] net neutrality back in the news
Date: Fri, 29 Sep 2023 18:26:36 +0200 [thread overview]
Message-ID: <CAC=tZ0ooepBLDgBzssrQYYQQGRjW9K13z-Gpkh=JKx=jLdq_kA@mail.gmail.com> (raw)
Mobile phone operators are monetizing metadata, as the issue with the
Apple Private Relay generating their complaints made evident.
The 5G has a network function for that: NWDAF
> Date: Fri, 29 Sep 2023 08:28:00 -0400
> From: Rich Brown <richb.hanover@gmail.com>
> To: Jonathan Morton <chromatix99@gmail.com>
> Cc: David Lang <david@lang.hm>, Rpm <rpm@lists.bufferbloat.net>, dan
> <dandenson@gmail.com>, Jamal Hadi Salim <jhs@mojatatu.com>, libreqos
> <libreqos@lists.bufferbloat.net>, Dave Taht via Starlink
> <starlink@lists.bufferbloat.net>, "Livingood, Jason"
> <Jason_Livingood@comcast.com>, bloat <bloat@lists.bufferbloat.net>
> Subject: Re: [Starlink] [Rpm] [Bloat] [LibreQoS] net neutrality back
> in the news
> Message-ID: <039490DA-48A7-4AE2-B00F-AA2A260FB747@gmail.com>
> Content-Type: text/plain; charset=us-ascii
>
> Thank you Jonathan for this clear description of the issues and their
> history. I wonder if there's a fourth one - privacy.
>
> Rosenworcel's talk https://docs.fcc.gov/public/attachments/DOC-397257A1.pdf
> also points out that ISPs might want to monetize our traffic patterns and
> location data. (This is less of an issue in the EU, but the US remains a
> Wild West in this regard.)
>
> I am hopeful that the FCC will include this in their NPRM (which must be
> available by now but I haven't looked...)
>
> - Rich Brown
next reply other threads:[~2023-09-29 16:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 16:26 David Fernández [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-29 15:19 Livingood, Jason
2023-09-27 18:21 [Starlink] " Dave Taht
2023-09-28 6:25 ` [Starlink] [Rpm] " Sebastian Moeller
2023-09-28 16:38 ` Dave Taht
2023-09-28 19:31 ` Sebastian Moeller
2023-09-28 19:39 ` Dave Taht
2023-09-28 20:08 ` [Starlink] [LibreQoS] " dan
2023-09-28 20:48 ` Livingood, Jason
2023-09-28 22:19 ` [Starlink] [Bloat] " David Lang
2023-09-29 4:54 ` Jonathan Morton
2023-09-29 12:28 ` [Starlink] [Rpm] [Bloat] [LibreQoS] " Rich Brown
2023-09-29 16:15 ` dan
2023-09-30 12:00 ` Frantisek Borsik
2023-09-30 12:19 ` Sebastian Moeller
2023-09-30 12:42 ` Vint Cerf
2023-09-30 14:07 ` Sebastian Moeller
2023-09-30 14:41 ` Mike Conlow
2023-09-29 6:24 ` Sebastian Moeller
2023-09-29 6:31 ` Gert Doering
2023-09-29 7:07 ` Sebastian Moeller
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='CAC=tZ0ooepBLDgBzssrQYYQQGRjW9K13z-Gpkh=JKx=jLdq_kA@mail.gmail.com' \
--to=davidfdzp@gmail.com \
--cc=starlink@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