Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: David Lang <david@lang.hm>
Cc: 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] [NNagain] The French have decided to destroy the Internet within their own country by taxing Gigabits (Dr. Peering)
Date: Wed, 4 Nov 2026 20:20:54 +0100	[thread overview]
Message-ID: <F84D6A29-094E-4C44-AC3D-E1C57B78770D@gmx.de> (raw)
In-Reply-To: <97sos3pq-n209-nr88-ops7-24qn6n06n5q0@ynat.uz>

Hi David,


> On Nov 4, 2026, at 20:14, David Lang <david@lang.hm> wrote:
> 
> Sebastian Moeller via Bloat wrote:
> 
>>> In essence, someone in France could VPN to a different country; neither the ISP or the VPN provider would know the specific content being accessed
>> 
>> Indeed, and the law explicitly states that just received bytes for the ISPs customers are to be counted, per ASN and the bill is supposed to be sent to that ASN, independent of whether that ASN is the true source or what kind of data we are talking about...  actually the law states that neither destination (the specific enduser) nor content are to be looked at/reported/aggregated.
> 
> so if a packet transitions multiple ISPs, each one would generate a bill for the traffic? what a way to entrench large ISPs

As far as I understand only the final ISP that serves the destination IP address... so if e.g. free would use orange as transit provider orange would not count that data as it does not terminate at end-users. BUT I have only read translations as my french is to bad and I have zero understanding of french legalese, so you might be correct that such a situation is not currently handled* 

> 
> (I may be misunderstanding something)

I am in the same boat ;)

> 
> David Lang


*) Ans anyway, I thing we all agree this thing is half-baked at best and will not pass (at least not in that form).

  reply	other threads:[~2026-11-04 19:21 UTC|newest]

Thread overview: 18+ 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-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                   ` Sebastian Moeller [this message]
2026-11-04 19:26                 ` [Starlink] Re: [NNagain] Re: [Bloat] " Olivier MJ Crépin-Leblond
     [not found]   ` <bf2f7d692a5e42738403850d419c4a94@OS5P279MB0502.NORP279.PROD.OUTLOOK.COM>
2026-11-02 11:33     ` [Starlink] " Michael Welzl

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=F84D6A29-094E-4C44-AC3D-E1C57B78770D@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=david@lang.hm \
    --cc=frantisek.borsik@gmail.com \
    --cc=libreqos@lists.bufferbloat.net \
    --cc=michawe@ifi.uio.no \
    --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