Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: Mike Conlow <mconlow@cloudflare.com>
To: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] "FCC explicitly prohibits fast lanes, closing possible net neutrality loophole"
Date: Fri, 10 May 2024 11:08:39 -0400	[thread overview]
Message-ID: <CAMo6_muxzhfqfxsHL6N9+RsWg_R1F8Thvg1wObps9R_Dx9BTnA@mail.gmail.com> (raw)
In-Reply-To: <CAJUtOOiBCOrVwi9=g4F27sZ7bCw32A=yRCrqiy56CBghq1kAvw@mail.gmail.com>

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

I'm sure this was a difficult thing to write a regulation on. I'm glad the
FCC took a swing. Here's why:

If the Internet community wants to [continue] to develop technologies where
applications (or users) can signal a need for low latency treatment and
other networks in the path can honor that need -- great.

But one of the networks in the chain -- the access network -- making the
determination of what types of traffic get the low latency treatment, in my
personal opinion is reasonably interpreted as throttling.

I think it's also worth noting that these rules only apply to last-mile
mass-market ISP plans. And any network is still free to offer "network
slicing" as an enterprise offering, which I'm sure they will.

On Fri, May 10, 2024 at 10:32 AM Frantisek Borsik via Nnagain <
nnagain@lists.bufferbloat.net> wrote:

> "Net neutrality proponents argued that these separate lanes for different
> kinds of traffic would degrade performance of traffic that isn't favored.
> The final FCC order released yesterday addresses that complaint.
>
> "We clarify that a BIAS [Broadband Internet Access Service] provider's
> decision to speed up 'on the basis of Internet content, applications, or
> services' would 'impair or degrade' other content, applications, or
> services which are not given the same treatment," the FCC's final order
> said.
>
> The "impair or degrade" clarification means that speeding up is banned
> because the no-throttling rule says that ISPs "shall not impair or degrade
> lawful Internet traffic on the basis of Internet content, application, or
> service."
>
>
> https://arstechnica.com/tech-policy/2024/05/fcc-explicitly-prohibits-fast-lanes-closing-possible-net-neutrality-loophole/
>
>
> 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
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
>

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

  reply	other threads:[~2024-05-10 15:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-10 14:31 Frantisek Borsik
2024-05-10 15:08 ` Mike Conlow [this message]
2024-05-10 15:48   ` Dave Taht
2024-05-15 21:43 ` Karl Auerbach
2024-05-15 22:28   ` Robert McMahon
2024-05-16  0:55   ` Vint Cerf
2024-05-16  1:14     ` Jack Haverty
2024-05-16  1:45       ` Mike Conlow
2024-05-16  1:53     ` Karl Auerbach
2024-05-16 13:07       ` Livingood, Jason
2024-05-16  6:23   ` Sebastian Moeller
2024-05-16 13:03   ` 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=CAMo6_muxzhfqfxsHL6N9+RsWg_R1F8Thvg1wObps9R_Dx9BTnA@mail.gmail.com \
    --to=mconlow@cloudflare.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