Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: "Livingood, Jason" <jason_livingood@comcast.com>
To: "karl@cavebear.com" <karl@cavebear.com>,
	"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: Thu, 16 May 2024 13:07:07 +0000	[thread overview]
Message-ID: <16345818-E1C2-4252-A3E8-F9347ED0376F@comcast.com> (raw)
In-Reply-To: <e6242c87-9bf3-442d-8ee7-4745064a4cf9@cavebear.com>

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

> First is the natural inclination of some large organizations to use regulatory language as a weapon, often twisting inadequately detailed expressions of intent around a Procrustean iron bed of regulatory definitions.

Many people expect to see the same. ;-)

JL


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

  reply	other threads:[~2024-05-16 13:07 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
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 [this message]
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=16345818-E1C2-4252-A3E8-F9347ED0376F@comcast.com \
    --to=jason_livingood@comcast.com \
    --cc=karl@cavebear.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