General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Replikon Research, D-U-N-S/FCN 77-387-4974" <Admin@replikon.net>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] FCC request for standardized testing
Date: Thu, 19 Dec 2024 12:56:22 -0500	[thread overview]
Message-ID: <CAOnAEVaezuOSoG6pDLDz66xQcWqDqn0SALt_kWrtchMNRTbOMw@mail.gmail.com> (raw)
In-Reply-To: <mailman.384.1734627227.1142.bloat@lists.bufferbloat.net>

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

This is my kind of discussion whoopee usually I just read

Let me say that I am currently advocating for more electric car chargers in
apartment developments and more of those electric car chargers to be
connected internally to specified apartments in larger buildings or in
smaller developments where they have bi-directional charging that is
provide community resource in an emergency not all of them just some of
them and that I learned in November that national electrical code is
specifying the manner in which that is done so let me start there

I'm a tactical strategic thinker both

A diplomat also but let's not brag I don't go overseas it's just a style of
communication

So along the spectrum between tactical and strategic let's start with
national electrical code the manner in which it is done that is a tactical
specification think about it tactics how to

That's at the federal level national electric Code is

And likewise FCC would be at the federal level

So big space here


Expect tactical interaction from fcc's input to the process


Now here are the refinements about which I'm not completely sure the first
I'm pretty sure

You can expect strategic interactions or interactions on the question of
strategy from the more local authorities which define who gets access to
what when what everything means how often things get done what resources
are diverted in money money where the federal level does not generally
specify that although it can for the really large projects programs and
initiatives

So on the question of the speed test and it's relevant to networking I'm
sorry I don't have a plus I'll drop out of that point

I hope that what I've contributed here contributes to the discussion
between you all a plus kind of guys and gals and the rest of the world on
how to manage buffer bloat and the overall vulnerability of the internet

I will say that I do have fingers in a couple of pots

Here to save the day? That is the slogan in Latin actually of the planetary
defense group headquartered at nasa and participating internationally. It
is absolutely certain that one day a really whopping asteroid will just
Wang us really hard

Is absolutely certain that one day the internet will utterly crash

The question of when I leave to see you all

and so Merry Christmas you are definitely here to save the day
congratulations bye

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

           reply	other threads:[~2024-12-19 17:56 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <mailman.384.1734627227.1142.bloat@lists.bufferbloat.net>]

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/bloat.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=CAOnAEVaezuOSoG6pDLDz66xQcWqDqn0SALt_kWrtchMNRTbOMw@mail.gmail.com \
    --to=admin@replikon.net \
    --cc=D.Goncz-FAX-571-395-3575@replikon.net \
    --cc=bloat@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