From: Jan Ceuleers <jan.ceuleers@gmail.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] [Rpm] [Starlink] [LibreQoS] net neutrality back in the news
Date: Sat, 30 Sep 2023 16:28:25 +0200 [thread overview]
Message-ID: <d9e850e7-daed-8022-5b25-f931c8aa2e59@gmail.com> (raw)
In-Reply-To: <3F6D16C8-530E-4066-8B6A-C0644B3C2D2C@gmx.de>
On 30/09/2023 14:19, Sebastian Moeller via Bloat wrote:
>
> P.S.: Of course if we look close enough we surely can find corner-cases where either the EU regulations or the translation into national law result in less desirable outcomes, but "nothing is perfect" and all in all the regulations seem to be "good enough". With the caveat that explicitly excluding ISP interconnect from the regulations BEREC essentially pointed the way for ISPs wanting to monetize their eye-balls twice to do so via interconnects, but that only works for the 800 pound gorillas and generally is not a game smaller ISPs can play. I do understand why BEREC wants to stay out of the interconnection issue, as this is rather complicated and the market seems to generally work okay-ish (that is not badly enough to make intervention a hot-button issue for voters and hence politicians).
EU Regulations have force of law in and of themselves; they need not be
transposed into national law. That sets Regulations apart from
Directives: those do need to be transposed into national law. Having
said that many member states may adopt laws that implement Regulations,
but in case of any differences between those national laws and the
Regulations in question the Regulations will prevail in the courts.
next prev parent reply other threads:[~2023-09-30 14:28 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 18:21 [Bloat] " Dave Taht
2023-09-28 3:33 ` [Bloat] [Rpm] " rjmcmahon
2023-09-28 6:06 ` Dave Taht
2023-10-01 17:08 ` [Bloat] [Starlink] " Sebastian Moeller
2023-10-05 19:22 ` Dave Taht
2023-09-28 6:25 ` [Bloat] " Sebastian Moeller
[not found] ` <ZRUe_5uiRJyDxb9Z@Space.Net>
2023-09-28 7:14 ` [Bloat] [Starlink] " Sebastian Moeller
[not found] ` <ZRUsLalRicJpQoXH@Space.Net>
2023-09-28 7:38 ` Sebastian Moeller
2023-09-28 16:38 ` [Bloat] " Dave Taht
2023-09-28 16:52 ` [Bloat] [Starlink] " Livingood, Jason
2023-09-28 17:04 ` [Bloat] [Rpm] [Starlink] " rjmcmahon
2023-09-28 19:31 ` [Bloat] [Rpm] " Sebastian Moeller
2023-09-28 19:39 ` Dave Taht
2023-09-28 20:08 ` [Bloat] [LibreQoS] " dan
2023-09-28 20:18 ` Dave Taht
2023-09-29 19:00 ` [Bloat] Getting Google to index. was:Re: [Starlink] " Rodney W. Grimes
2023-09-28 20:36 ` [Bloat] " Jeremy Austin
2023-09-28 20:54 ` Livingood, Jason
2023-09-28 20:48 ` [Bloat] [Starlink] " Livingood, Jason
2023-09-28 22:19 ` David Lang
2023-09-29 4:54 ` Jonathan Morton
2023-09-29 12:28 ` [Bloat] [Rpm] [Starlink] [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 ` [Bloat] [Starlink] [Rpm] " Vint Cerf
2023-09-30 14:07 ` Sebastian Moeller
2023-09-30 14:28 ` Jan Ceuleers [this message]
2023-09-30 14:35 ` [Bloat] [Rpm] [Starlink] " Sebastian Moeller
2023-09-30 14:41 ` Mike Conlow
2023-09-30 15:20 ` Sebastian Moeller
2023-09-30 15:23 ` [Bloat] [LibreQoS] [Rpm] [Starlink] " Dave Taht
2023-09-30 17:35 ` Dave Taht
2023-09-30 21:57 ` [Bloat] New email list: NNagain for network neutrality Dave Taht
2023-10-04 22:19 ` [Bloat] [Rpm] [Starlink] [LibreQoS] net neutrality back in the news Michael Richardson
2023-09-29 6:24 ` Sebastian Moeller
[not found] ` <ZRZvMLtKhkd6-16m@Space.Net>
2023-09-29 7:07 ` [Bloat] [Starlink] [Rpm] " Sebastian Moeller
2023-09-28 22:25 ` [Bloat] [LibreQoS] [Rpm] " David Lang
2023-09-28 17:10 ` [Bloat] " Livingood, Jason
2023-09-28 19:30 ` Dave Taht
2023-09-28 20:05 ` Sebastian Moeller
2023-09-28 21:07 ` [Bloat] [EXTERNAL] " Livingood, Jason
2023-09-28 21:08 ` Livingood, Jason
2023-09-29 8:56 ` Erik Auerswald
2023-09-29 15:19 [Bloat] [Rpm] [Starlink] [LibreQoS] " Livingood, Jason
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=d9e850e7-daed-8022-5b25-f931c8aa2e59@gmail.com \
--to=jan.ceuleers@gmail.com \
--cc=bloat@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