Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: Frantisek Borsik <frantisek.borsik@gmail.com>
To: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] The Verge: The quiet plan to make the internet feel faster
Date: Sun, 10 Dec 2023 07:54:07 +0100	[thread overview]
Message-ID: <CAJUtOOidWrXn0aOJtZXGP4FdRt_hjmaT1y1RxA9uFix1cN1FZQ@mail.gmail.com> (raw)
In-Reply-To: <CA+s1KQFSuid=BRT-_==fmLB4GBo03S6k5viNOV_0fP7A89ssmQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]

Well, to be completely honest, I would say its about general public, really
- it’s an article in The Verge :-)

But yeah. Here’s something they should address:

https://github.com/heistp/l4s-tests#key-findings

In general - a potential harm to innocent bystanders is a biggest L4S
problem:
https://www.linkedin.com/posts/frantisekborsik_jonathanmorton-l4s-ietf118-activity-7128317873571176448-GWAX




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 Sun, 10 Dec 2023 at 5:48 AM, Matt Mathis via Nnagain <
nnagain@lists.bufferbloat.net> wrote:

> About L4S
>
> https://www.theverge.com/23655762/l4s-internet-apple-comcast-latency-speed-bandwidth
>
> It says something about their target audience that they feel they need to
> explain bytes vs bits.
>
> Thanks,
> --MM--
> Evil is defined by mortals who think they know "The Truth" and use force
> to apply it to others.
> -------------------------------------------
> Matt Mathis  (Email is best)
> Home & mobile: 412-654-7529 please leave a message if you must call.
>
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
>

[-- Attachment #2: Type: text/html, Size: 3117 bytes --]

  reply	other threads:[~2023-12-10  6:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-10  4:48 Matt Mathis
2023-12-10  6:54 ` Frantisek Borsik [this message]
2023-12-10 11:12   ` Sauli Kiviranta
2023-12-10 18:21     ` Robert McMahon
2023-12-11  9:50       ` Frantisek Borsik
     [not found]         ` <4C2CA220-A7EF-4198-BE6C-A2FC979A1F8D@gmx.de>
2023-12-11 10:18           ` Frantisek Borsik
     [not found]             ` <E96CB707-1BDE-48F6-A09F-2229FDBA372A@gmx.de>
2023-12-11 19:33               ` Frantisek Borsik
2023-12-11 14:54         ` Livingood, Jason
2023-12-11 18:51           ` rjmcmahon
2023-12-11 19:25             ` Frantisek Borsik
2023-12-11 15:13       ` Livingood, Jason
2023-12-11 14:56 ` 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/nnagain.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJUtOOidWrXn0aOJtZXGP4FdRt_hjmaT1y1RxA9uFix1cN1FZQ@mail.gmail.com \
    --to=frantisek.borsik@gmail.com \
    --cc=nnagain@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