Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: "David P. Reed" <dpreed@deepplum.com>
To: "Juliusz Chroboczek" <jch@irif.fr>
Cc: "Sebastian Moeller" <moeller0@gmx.de>,
	sascha@thexlab.org,
	"Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>,
	"Michael Welzl" <michawe@ifi.uio.no>,
	"Frantisek Borsik" <frantisek.borsik@gmail.com>,
	"Dave Taht via Starlink" <starlink@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>,
	"Cake List" <cake@lists.bufferbloat.net>,
	libreqos <libreqos@lists.bufferbloat.net>,
	"Jeremy Austin via Rpm" <rpm@lists.bufferbloat.net>
Subject: [Starlink] Re: [Bloat] Re: [Cake] [NNagain] The French have decided to destroy the Internet within their own country by taxing Gigabits (Dr. Peering)
Date: Mon, 16 Nov 2026 20:43:45 -0500 (EST)	[thread overview]
Message-ID: <1794879825.311917832@apps.rackspace.com> (raw)
In-Reply-To: <87ecckgyyq.wl-jch@irif.fr>


There is a presumption that "providers" will just pay based on byte counts on their wires or wireless.
 
But I don't get it. Why not just tax the physical assets, and not bother with byte counting at all?
 
Do they tax theaters based on the number of words spoken by actors in the theater? 
 
My colleague at the Media Lab, Andy Lippman once talked about how Xerox might charge the users of its leased copiers based on end-user value - a copy of your kids homework might cost a nickel per page, but copying a corporate merger agreement for a billion dollar acquistion might be charged a few million dollars just for that one copy made.
 
This attempts to tax the "value" of the bits copied or transmitted, as companies like airlines try to do with First Class vs. Coach prices, or other "value" pricing.  In the case of bits on a wire, the actual cost of operations is not due to the bits, but the cost of installing and maintaining the wire.
 
And of course, most of the value of a "network" isn't due to usage, but due to the optionality introduced by the ability to (at any time) reach any of the endpoints.  That's been explained in Metcalfe's Law and Reed's Law - both of which try to value the option to send a message, which is usually worth more than the actual messages sent.
 
Really, the EU technocracy should learn something about the communications business and communications economics.
 
Otherwise their whole concept is just whacko.
 
On Monday, November 16, 2026 18:04, "Juliusz Chroboczek" <jch@irif.fr> said:



> > That is not ment to mean all is fine with the amendment (and we all seem
> > to agree it is going nowhere and deservedly so), just that privacy or
> > censorship in my opinion are not really affected.
> 
> Fully agreed, on all counts.
> 
> What is interesting, the rationale (``Exposé Sommaire'') explicitly
> explains how user privacy is being protected:
> 
> « This model does not raise issues related to privacy: the data are never
> consulted. The tax does not involve any deep inspection of data
> packets, no subscriber's personal data is audited, and it respects the
> confidentiality of correspondence just like the GDPR: one counts bytes
> by operator, not individual uses. Transit providers and CDNs are not
> required to name their customers. They pass on the tax to them or not,
> depending on their terms of service, while respecting trade secrets. »
> 
> I'm not claiming the envisioned scenario is realistic, merely that the
> authors did take user privacy into account.
> 
> -- Juliusz
> 

  reply	other threads:[~2026-11-17  1:43 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-31 12:56 [Starlink] The French have decided to destroy the Internet within their own country by taxing Gigabits (Dr. Peering) Frantisek Borsik
2026-10-31 14:51 ` [Starlink] Re: [Bloat] " Sophie
2026-10-31 14:58 ` [Starlink] " Inemesit Affia
2026-10-31 18:05 ` [Starlink] " Daniel AJ Sokolov
2026-11-02  7:44 ` [Starlink] [Bloat] " Michael Welzl
2026-11-02 11:23   ` [Starlink] Re: [Bloat] " Sebastian Moeller
2026-11-02 14:30     ` [Starlink] Re: [NNagain] " Sascha Meinrath
2026-11-04 15:40       ` [Starlink] Re: [NNagain] " Sebastian Moeller
2026-11-04 16:20         ` Sascha Meinrath
2026-11-04 17:03           ` Sebastian Moeller
2026-11-04 17:57             ` [Starlink] Re: [Cake] " David P. Reed
2026-11-05  9:05               ` [Starlink] Re: [Cake] " Sebastian Moeller
2026-11-16 23:04                 ` [Starlink] Re: [Bloat] Re: [Cake] [NNagain] " Juliusz Chroboczek
2026-11-17  1:43                   ` David P. Reed [this message]
2026-11-17 12:33                     ` Juliusz Chroboczek
2026-11-18  7:53                     ` Frantisek Borsik
2026-11-18  9:25                     ` David Lang
2026-11-18  7:48               ` [Starlink] Re: [Cake] Re: [NNagain] [Bloat] " Frantisek Borsik
2026-11-18 12:12                 ` Sascha Meinrath
2026-11-04 18:33             ` [Starlink] " Sascha Meinrath
2026-11-04 19:09               ` Sebastian Moeller
2026-11-04 19:14                 ` [Starlink] Re: [Bloat] Re: [NNagain] " David Lang
2026-11-04 19:20                   ` [Starlink] Re: [Bloat] " Sebastian Moeller
2026-11-04 19:26                 ` [Starlink] Re: [NNagain] Re: [Bloat] " Olivier MJ Crépin-Leblond
2026-11-18  7:49               ` [Starlink] Re: [NNagain] " Frantisek Borsik
2026-11-18  1:48       ` [Starlink] Re: [NNagain] " Raquel Renno Nunes
2026-11-18  7:46       ` Frantisek Borsik
     [not found]   ` <bf2f7d692a5e42738403850d419c4a94@OS5P279MB0502.NORP279.PROD.OUTLOOK.COM>
2026-11-02 11:33     ` [Starlink] " Michael Welzl
2026-11-16 16:11 ` Juliusz Chroboczek
2026-11-16 16:31   ` [Starlink] Re: [LibreQoS] " Frantisek (Frank) Borsik
2026-11-16 20:41     ` [Starlink] Re: [Bloat] Re: [LibreQoS] " Linus Lüssing
2026-11-16 22:53       ` Juliusz Chroboczek
2026-11-17 15:59         ` Michael Richardson
2026-11-18  0:13           ` David Lang
2026-11-18  0:36             ` [Starlink] Re: [NNagain] " Richard Roy
2026-11-18  1:16             ` [Starlink] " Michael Richardson
2026-11-18  9:17               ` David Lang
2026-11-18 13:37                 ` Juliusz Chroboczek
2026-11-18 23:22                   ` David Lang
2026-11-17  6:36     ` [Starlink] Re: [LibreQoS] Re: [Bloat] " 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=1794879825.311917832@apps.rackspace.com \
    --to=dpreed@deepplum.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=frantisek.borsik@gmail.com \
    --cc=jch@irif.fr \
    --cc=libreqos@lists.bufferbloat.net \
    --cc=michawe@ifi.uio.no \
    --cc=moeller0@gmx.de \
    --cc=nnagain@lists.bufferbloat.net \
    --cc=rpm@lists.bufferbloat.net \
    --cc=sascha@thexlab.org \
    --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