Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: Dave Cohen <craetdave@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] Flash Priority
Date: Sat, 9 Mar 2024 13:08:59 -0500	[thread overview]
Message-ID: <CAAsXY1RBGbnxi0t0+7SvnsX5_xgrUeny5oOJSs7bvRFo0wwm4A@mail.gmail.com> (raw)
In-Reply-To: <CAOnAEVY_2LiR1cTdp1dzXNHqbzGDT4X7a5+aXi709BosWpN2YA@mail.gmail.com>

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

Bear in mind that FirstNet is its own thing, to an extent. Internet
providers will (almost?) always discard priority bits for *general public
Internet service*. FirstNet doesn't qualify as a service for general use,
so it is possible that some markings may be reacted to, or at least not
discarded outright. That is a question for someone more knowledgeable on
the FirstNet service directly.

What I can add is that in a previous life at a Tier 1, any traffic on a
port that touched the public Internet in some manner had priority markings
squashed, and that traffic was placed into the same priority queue on our
backbone links (I recognize that the latter part of this statement opens up
some other neutrality-adjacent worms) - this includes traffic accepted via
peering, not just transit. Customers with private L2/3 services would
either have their markings preserved or acted upon, depending on whether or
not that service was "QoS enabled". The conclusions to reach here are, IMO:

1) Even if FirstNet itself responds to or accepts prioritization markings,
destination networks beyond, where applicable, may not, so the relevance
may be limited regardless.
2) This is deliberate choice at the provider level, even if that choice is
effectively a consensus

On Sat, Mar 9, 2024 at 12:56 PM Douglas Goncz A.A.S. M.E.T. 1990 via
Nnagain <nnagain@lists.bufferbloat.net> wrote:

> I think some of the cogent points made were
>
> Just because something is in an RFC and recognized or accepted RFC does
> not mean it's been established
>
> Ancient rfcs can age out into abandoned protocols
>
> I got the distinct impression now and I think it's reasonable flash
> priority is an abandoned protocol
>
> I will stay with firstnet and the engineers there to make sure I have
> reliable communication in the event of an Internet emergency so that I can
> do what I do best which is help other people and I thank you all for
> helping me with this issue.
>
>
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
>


-- 
- Dave Cohen
craetdave@gmail.com
@dCoSays
www.venicesunlight.com

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

  reply	other threads:[~2024-03-09 18:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.5.1710003601.27690.nnagain@lists.bufferbloat.net>
2024-03-09 17:56 ` Douglas Goncz  A.A.S. M.E.T. 1990
2024-03-09 18:08   ` Dave Cohen [this message]
     [not found] <mailman.2416.1709929573.1074.nnagain@lists.bufferbloat.net>
2024-03-09  2:31 ` [NNagain] Flash priority Douglas Goncz  A.A.S. M.E.T. 1990
2024-03-09  3:01   ` David Lang
2024-03-09 14:38     ` Livingood, Jason
2024-03-09 15:04       ` Sebastian Moeller
2024-03-09 18:38       ` rjmcmahon
2024-03-09 18:43         ` rjmcmahon
2024-03-09 21:01           ` Sebastian Moeller
2024-03-09 22:36             ` rjmcmahon
2024-03-10  2:52         ` Lee
2024-03-10  3:49           ` rjmcmahon
2024-03-09  3:22   ` Dick Roy
2024-03-09  9:41   ` Vint Cerf
2024-03-10 15:39     ` Joe Hamelin

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=CAAsXY1RBGbnxi0t0+7SvnsX5_xgrUeny5oOJSs7bvRFo0wwm4A@mail.gmail.com \
    --to=craetdave@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