From: Frantisek Borsik <frantisek.borsik@gmail.com>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: "Juliusz Chroboczek" <jch@irif.fr>,
"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>,
"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: [Bloat] Re: [Cake] [NNagain] The French have decided to destroy the Internet within their own country by taxing Gigabits (Dr. Peering)
Date: Tue, 17 Nov 2026 23:53:14 -0800 [thread overview]
Message-ID: <CAJUtOOitKj-D+G72-v=NRhbg+nAaEmL_j8a82v_VQXKrHDX3_g@mail.gmail.com> (raw)
In-Reply-To: <1794879825.311917832@apps.rackspace.com>
🙏
Frantisek Borsik reacted via Gmail
<https://www.google.com/gmail/about/?utm_source=gmail-in-product&utm_medium=et&utm_campaign=emojireactionemail#app>
On Mon, Nov 16, 2026 at 5:43 PM David P. Reed <dpreed@deepplum.com> wrote:
> 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
> >
>
next prev parent reply other threads:[~2026-11-18 7:53 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 12:56 [Bloat] The French have decided to destroy the Internet within their own country by taxing Gigabits (Dr. Peering) Frantisek Borsik
2026-10-31 14:51 ` [Bloat] " Sophie
2026-11-02 7:44 ` Michael Welzl
2026-11-02 11:23 ` Sebastian Moeller
2026-11-02 14:30 ` [Bloat] Re: [NNagain] " Sascha Meinrath
2026-11-04 15:40 ` [Bloat] Re: [NNagain] " Sebastian Moeller
2026-11-04 16:20 ` Sascha Meinrath
2026-11-04 17:03 ` Sebastian Moeller
2026-11-04 17:57 ` [Bloat] Re: [Cake] " David P. Reed
2026-11-05 9:05 ` [Bloat] Re: [Cake] " Sebastian Moeller
2026-11-16 23:04 ` Juliusz Chroboczek
2026-11-17 1:43 ` David P. Reed
2026-11-17 12:33 ` Juliusz Chroboczek
2026-11-18 7:53 ` Frantisek Borsik [this message]
2026-11-18 9:25 ` David Lang
2026-11-18 7:48 ` [Bloat] Re: [Cake] " Frantisek Borsik
2026-11-18 12:12 ` Sascha Meinrath
2026-11-04 18:33 ` [Bloat] " Sascha Meinrath
2026-11-04 19:09 ` Sebastian Moeller
2026-11-04 19:14 ` David Lang
2026-11-04 19:20 ` Sebastian Moeller
2026-11-04 19:26 ` [Bloat] Re: [NNagain] " Olivier MJ Crépin-Leblond
2026-11-18 7:49 ` [Bloat] Re: [NNagain] " Frantisek Borsik
2026-11-18 1:48 ` [Bloat] Re: [Starlink] Re: [NNagain] " Raquel Renno Nunes
2026-11-18 7:46 ` [Bloat] " Frantisek Borsik
[not found] ` <bf2f7d692a5e42738403850d419c4a94@OS5P279MB0502.NORP279.PROD.OUTLOOK.COM>
2026-11-02 11:33 ` [Bloat] " Michael Welzl
2026-11-16 16:11 ` Juliusz Chroboczek
2026-11-16 16:31 ` [Bloat] Re: [LibreQoS] " Frantisek (Frank) Borsik
2026-11-16 20:41 ` 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 ` [Bloat] Re: [NNagain] " Richard Roy
2026-11-18 1:16 ` [Bloat] " Michael Richardson
2026-11-18 9:17 ` David Lang
2026-11-18 10:03 ` Sebastian Moeller
2026-11-18 13:37 ` Juliusz Chroboczek
2026-11-18 23:22 ` David Lang
2026-11-17 6:36 ` [Bloat] Re: [Starlink] " 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/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='CAJUtOOitKj-D+G72-v=NRhbg+nAaEmL_j8a82v_VQXKrHDX3_g@mail.gmail.com' \
--to=frantisek.borsik@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=dpreed@deepplum.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