From: Dave Taht <dave.taht@gmail.com>
To: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] The Whys of the Wichita IXP Project
Date: Sat, 24 Feb 2024 07:27:09 -0500 [thread overview]
Message-ID: <CAA93jw6DKU7+PyXt-uKHT-eJFgaBLZVFJtN+_Thx6XHpyoQkxQ@mail.gmail.com> (raw)
In-Reply-To: <2FE6AC99-172D-4948-8277-AD4316054E3D@gmail.com>
Who can fund more IXPs? The internet society has a 50k set-asied.
From a friend in the NTIA:
"The NTIA middle mile program was a one-time authorization from
Congress. All allocated funds have been assigned to grantees. Some
states may, if funding allows, decide to fund middle mile projects
from their BEAD allocation, but this is a lower priority compared to
last-mile projects."
What I (presently) see out of BEAD is all this end-user fiber, missing
anchor tenants, and gpon, and cluelessness about IPvX, making
interconnectivity more difficult.
There was a pretty good AMA with utopia fiber in Utah yesterday. They
at least are using active-e fiber, and are well connected to a IXP
there.
https://www.broadband.io/c/get-broadband-grant-alerts-news/credit-kim-mckinley-with-making-open-access-and-community-broadband-cool
On Sat, Feb 24, 2024 at 7:05 AM Fearghas Mckay via Nnagain
<nnagain@lists.bufferbloat.net> wrote:
>
>
>
> On 22 Feb 2024, at 18:58, rjmcmahon via Nnagain <nnagain@lists.bufferbloat.net> wrote:
>
> Boston University spent $305M on this and it doesn't have an IXP.
>
>
> There are two well established distinct IX in the metro already - why would you need a third that is not at an interconnection site ?
>
> Boston IX
> Mass IX
>
> f
>
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
--
https://blog.cerowrt.org/post/2024_predictions/
Dave Täht CSO, LibreQos
next prev parent reply other threads:[~2024-02-24 12:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 22:54 Brent Legg
2024-02-22 8:14 ` Bill Woodcock
2024-02-22 13:39 ` Dave Taht
2024-02-22 18:58 ` rjmcmahon
2024-02-22 23:31 ` Bill Woodcock
2024-02-23 0:03 ` Dave Cohen
2024-02-23 0:04 ` Bill Woodcock
2024-02-23 0:09 ` Dave Cohen
2024-02-23 0:51 ` Bill Woodcock
2024-02-23 1:47 ` Dave Cohen
2024-02-24 12:05 ` Fearghas Mckay
2024-02-24 12:27 ` Dave Taht [this message]
2024-02-24 13:12 ` Fearghas Mckay
2024-02-24 13:24 ` Bill Woodcock
2024-02-24 14:03 ` Dave Taht
2024-02-24 21:30 ` Bill Woodcock
2024-02-24 19:30 ` Robert McMahon
2024-02-25 6:04 ` Bill Woodcock
2024-02-22 20:15 ` [NNagain] Email and The Internet? Jack Haverty
2024-02-23 0:02 ` [NNagain] The Whys of the Wichita IXP Project Bill Woodcock
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=CAA93jw6DKU7+PyXt-uKHT-eJFgaBLZVFJtN+_Thx6XHpyoQkxQ@mail.gmail.com \
--to=dave.taht@gmail.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