From: Frantisek Borsik <frantisek.borsik@gmail.com>
To: "Livingood, Jason" <jason_livingood@comcast.com>,
Jonathan Morton <chromatix99@gmail.com>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>,
Rpm <rpm@lists.bufferbloat.net>,
libreqos <libreqos@lists.bufferbloat.net>,
dan <dandenson@gmail.com>
Subject: Re: [Rpm] [LibreQoS] [Bloat] [Starlink] net neutrality back in the news
Date: Sat, 30 Sep 2023 13:41:39 +0200 [thread overview]
Message-ID: <CAJUtOOijcdYqr-+Pn=sBRetGL8jvwa_tbsfDAxLhaWx3h6D66g@mail.gmail.com> (raw)
In-Reply-To: <CAA_JP8X0dRJJm5vAxccvWjbqqL5hAdk=BHE9pf8k==0CDsAHnQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3560 bytes --]
>
> > They want something that can provide a domination service within their
> own walled gardens.
> Also not correct. And last time I checked the balance sheets of companies
> in these sectors - *video streaming services were losing money while
> provision of internet services were financially healthy. *
Indeed, Jason:
https://www.vulture.com/2023/06/streaming-industry-netflix-max-disney-hulu-apple-tv-prime-video-peacock-paramount.html
All the best,
Frank
Frantisek (Frank) Borsik
https://www.linkedin.com/in/frantisekborsik
Signal, Telegram, WhatsApp: +421919416714
iMessage, mobile: +420775230885
Skype: casioa5302ca
frantisek.borsik@gmail.com
On Fri, Sep 29, 2023 at 5:53 PM dan via Rpm <rpm@lists.bufferbloat.net>
wrote:
>
>
> On Fri, Sep 29, 2023 at 7:17 AM Livingood, Jason via LibreQoS <
> libreqos@lists.bufferbloat.net> wrote:
>
>> On 9/29/23, 00:54, "Jonathan Morton" <chromatix99@gmail.com <mailto:
>> chromatix99@gmail.com>> wrote:
>> > Some ISPs began to actively degrade Netflix traffic, in particular by
>> refusing to provision adequate peering capacity at the nodes through which
>> Netflix traffic predominated
>>
>> That is not true and really not worth re-litigating here.
>>
>> > NN regulations forced ISPs to carry Netflix traffic with reasonable
>> levels of service, even though they didn't want to for purely selfish and
>> greedy commercial reasons.
>>
>> NN regulations played no role whatsoever in the resolution of that
>> conflict - a business arrangement was reached, just as it was in the SK
>> Telecom example recently:
>> https://about.netflix.com/en/news/sk-telecom-sk-broadband-and-netflix-establish-strategic-partnership-to
>>
>> > ISPs behind L4S actively do not want a technology that works end-to-end
>> over the general Internet.
>>
>> That's simply not true. As someone running an L4S field trial right now -
>> we want the technology to get the widest possible deployment and be fully
>> end-to-end. Why else would there be so much effort to ensure that ECN and
>> DSCP marks can traverse network domain boundaries for example? Why else
>> would there be strong app developer interest? What evidence do you have to
>> show that anyone working on L4S want to create a walled garden? If
>> anything, it seems the opposite of 5G network slicing, which seems to me
>> personally to be another 3GPP run at walled garden stuff (like IMS).
>> Ultimately it is like a lot of other IETF work -- it is an interesting
>> technology and we'll have to see whether it gets good adoption - the
>> 'market' will decide.
>>
>> > They want something that can provide a domination service within their
>> own walled gardens.
>>
>> Also not correct. And last time I checked the balance sheets of companies
>> in these sectors - video streaming services were losing money while
>> provision of internet services were financially healthy.
>>
>> JL
>>
>>
>>
> I think this stuff degrades into conspiracy theory often enough. While I
> don't discount the possibility of collusion, I don't give these
> people/groups credit enough to pull of a mass scale conspiracy either....
> If netflix is jammed down to small of a pipe at an ISP, that's more likely
> (IMO...) disorganization or incompetence or disinterest over conspiracy.
> I feel the same about government in general...
> _______________________________________________
> Rpm mailing list
> Rpm@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/rpm
>
[-- Attachment #2: Type: text/html, Size: 6299 bytes --]
next prev parent reply other threads:[~2023-09-30 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 13:16 [Rpm] [Bloat] [Starlink] [LibreQoS] " Livingood, Jason
2023-09-29 15:53 ` [Rpm] [LibreQoS] [Bloat] [Starlink] " dan
2023-09-30 11:41 ` Frantisek Borsik [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-27 18:21 [Rpm] " Dave Taht
2023-09-28 6:25 ` 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 ` [Rpm] [LibreQoS] " dan
2023-09-28 20:48 ` [Rpm] [Starlink] " Livingood, Jason
2023-09-28 22:19 ` [Rpm] [Bloat] " David Lang
2023-09-29 4:54 ` Jonathan Morton
2023-09-29 12:28 ` Rich Brown
2023-09-29 16:15 ` dan
2023-09-30 12:00 ` Frantisek Borsik
2023-09-30 12:19 ` Sebastian Moeller
[not found] ` <CAMo6_mstw1tKjZfonQ=3Zc5TNqrffkEiUEXzCxLUf85o3kJs9A@mail.gmail.com>
2023-09-30 15:20 ` Sebastian Moeller
2023-09-30 15:23 ` [Rpm] [LibreQoS] [Bloat] [Starlink] " Dave Taht
2023-09-30 17:35 ` Dave Taht
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/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJUtOOijcdYqr-+Pn=sBRetGL8jvwa_tbsfDAxLhaWx3h6D66g@mail.gmail.com' \
--to=frantisek.borsik@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=dandenson@gmail.com \
--cc=jason_livingood@comcast.com \
--cc=libreqos@lists.bufferbloat.net \
--cc=rpm@lists.bufferbloat.net \
--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