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: Bill Woodcock <woody@pch.net>
Cc: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] ISOC's IXP program
Date: Tue, 16 Jan 2024 11:18:05 -0500	[thread overview]
Message-ID: <CAA93jw4815-dakoeGN98vXAo3Ui7DbhN80KSysW2NP=cu90uXQ@mail.gmail.com> (raw)
In-Reply-To: <1E7D331C-CA41-4FC5-BE8F-E98409154321@pch.net>

You're tough, Bill! I do not know any more about this program than
from the link, but it appeals to me at various levels. Notably: "Funds
are available for training, community/regional development, and
equipment purchases such as switches, optic modules, servers, and
routers." Not enough people really understand BGP, nor the need for an
internet to be an internet, and sometimes the capex needed to put in a
better switch or router, just isn't there.

So in particular, I would love to see efforts to make the need for
IXPs more understandable.

A couple weeks ago isoc also came out with a $12M program to support
internet resilience. I have been watching several WISPs boast today
how their networks stayed up (with adequate backup power and meshy
links) when their fiber competitors didn't, in the current cold/snow
snap...

I have been looking also, into cheaper gear that can do this job,
built around DANOS and SONIC. There's one switch for $1400 base cost
that looked really good, built around that.

Flaws:

This is support for the traditional IXP model, which does not include
middle mile/backhaul to another IXP hub.
It does, however, have a carveout for IP transit to attract CDNs, but
it's really not the same thing.

Doesn't have a carve-out for software development. I think it really
sad that so many seem to think that happens magically, and for free,
nowadays.

On Tue, Jan 16, 2024 at 10:46 AM Bill Woodcock <woody@pch.net> wrote:
>
>
>
> > On Jan 16, 2024, at 16:09, Dave Taht via Nnagain <nnagain@lists.bufferbloat.net> wrote:
> > this is the kind of initiative I can get behind.
>
> What, specifically, do you find admirable about it?
>
>                                 -Bill
>


-- 
40 years of net history, a couple songs:
https://www.youtube.com/watch?v=D9RGX6QFm5E
Dave Täht CSO, LibreQos

  reply	other threads:[~2024-01-16 16:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16 15:09 Dave Taht
2024-01-16 15:46 ` Bill Woodcock
2024-01-16 16:18   ` Dave Taht [this message]
2024-01-16 16:25     ` Bill Woodcock
2024-01-17 15:32 ` michael brooks - ESC

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='CAA93jw4815-dakoeGN98vXAo3Ui7DbhN80KSysW2NP=cu90uXQ@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=nnagain@lists.bufferbloat.net \
    --cc=woody@pch.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