Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] nn announced
Date: Thu, 19 Oct 2023 14:22:22 -0700	[thread overview]
Message-ID: <CAA93jw6Jpxx0yPPU-4Wz5XtOkGsnkYVKVd=HKfPaBM-BjR6c7A@mail.gmail.com> (raw)
In-Reply-To: <8AD15796-A785-4A88-B554-C9D507134B92@gmx.de>

Thx for the direct link. Very few, emotional responses so far, and I
liked the FTC suggestion here:

https://yro.slashdot.org/story/23/10/19/1619226/fcc-moves-ahead-with-title-ii-net-neutrality-rules-in-3-2-party-line-vote


On Thu, Oct 19, 2023 at 11:22 AM Sebastian Moeller <moeller0@gmx.de> wrote:
>
> Hi Dave,
>
> for the actual text see:
> https://docs.fcc.gov/public/attachments/DOC-397309A1.pdf
>
> Regards
>         Sebastian
>
>
> > On Oct 19, 2023, at 19:58, Dave Taht via Nnagain <nnagain@lists.bufferbloat.net> wrote:
> >
> > https://broadbandbreakfast.com/2023/10/fcc-moves-to-reinstate-net-neutrality-keeps-rules-open-for-comment/
> >
> > I would like to find the actual remarks, before everyone brings out
> > their own old knives, covered with ancient blood.
> >
> > --
> > Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
> > Dave Täht CSO, LibreQos
> > _______________________________________________
> > Nnagain mailing list
> > Nnagain@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/nnagain
>


-- 
Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
Dave Täht CSO, LibreQos

      reply	other threads:[~2023-10-19 21:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19 17:58 Dave Taht
2023-10-19 18:22 ` Sebastian Moeller
2023-10-19 21:22   ` Dave Taht [this message]

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='CAA93jw6Jpxx0yPPU-4Wz5XtOkGsnkYVKVd=HKfPaBM-BjR6c7A@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=moeller0@gmx.de \
    --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