From: dan <dandenson@gmail.com>
To: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Cc: "Douglas Goncz A.A.S. M.E.T. 1990" <DGoncz@replikon.net>
Subject: Re: [NNagain] Throttling
Date: Tue, 3 Oct 2023 12:19:15 -0600 [thread overview]
Message-ID: <CAA_JP8WgKJ1b7bCmNEdD+oz_NH70_M8rGrJSWUQqux4ywx-eJQ@mail.gmail.com> (raw)
In-Reply-To: <CAOnAEVaCqUTT-iuK0eKaG1fS_UY6ZFuSYTjxx1R6-toX98hS2A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
On Tue, Oct 3, 2023 at 12:16 PM Douglas Goncz A.A.S. M.E.T. 1990 via
Nnagain <nnagain@lists.bufferbloat.net> wrote:
> Internet protocol includes a flash traffic binary bit acceptable to
> indicate the priority traffic such during tomorrow's test of the emergency
> communication system and mobile emergency airtime warning or whatever m e a
> w stands for.
>
> Please let us include in our discussions here at nnagain the importance of
> dropping all other traffic when flash traffic is in the Network
>
>
Like I said, not all packets are equal. No one wants to trade a shorter
buffer fill in their streaming for not getting emergency broadcasts, but
they also don't want their zoom call or VoIP call glitching for their
netflex stream or any other realtime data flow. different degrees of the
some thing.
[-- Attachment #2: Type: text/html, Size: 1218 bytes --]
prev parent reply other threads:[~2023-10-03 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.825.1696356617.1074.nnagain@lists.bufferbloat.net>
2023-10-03 18:15 ` Douglas Goncz A.A.S. M.E.T. 1990
2023-10-03 18:19 ` dan [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=CAA_JP8WgKJ1b7bCmNEdD+oz_NH70_M8rGrJSWUQqux4ywx-eJQ@mail.gmail.com \
--to=dandenson@gmail.com \
--cc=DGoncz@replikon.net \
--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