From: Bill Woodcock <woody@pch.net>
To: Dave Taht <dave.taht@gmail.com>
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 17:25:41 +0100 [thread overview]
Message-ID: <CE4C94C9-431C-47F8-A365-01A547331415@pch.net> (raw)
In-Reply-To: <CAA93jw4815-dakoeGN98vXAo3Ui7DbhN80KSysW2NP=cu90uXQ@mail.gmail.com>
> On Jan 16, 2024, at 17:18, Dave Taht <dave.taht@gmail.com> wrote:
> I do not know any more about this program than from the link
Well, paying PR firms to write web content is one way to spend $100M/year.
> “Funds are available for training, community/regional development, and
> equipment purchases such as switches, optic modules, servers, and
> routers.”
Having been doing this for thirty years, I can assure you that nobody who’s trying to build an IXP needs 0.005% of ISOC’s budget. They need information and experience.
> I would love to see efforts to make the need for IXPs more understandable.
Yep, definitely. But that’s not what’s being floated here.
> This is support for the traditional IXP model, which does not include
> middle mile/backhaul to another IXP hub.
What would that accomplish?
> It does, however, have a carveout for IP transit to attract CDNs
Yep, Google will always take your money. Not sure what that would accomplish, though, other than to encourage Google to be more evil more of the time. Doesn’t have anything to do with IXPs.
> 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.
Yep.
-Bill
next prev parent reply other threads:[~2024-01-16 16:25 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
2024-01-16 16:25 ` Bill Woodcock [this message]
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=CE4C94C9-431C-47F8-A365-01A547331415@pch.net \
--to=woody@pch.net \
--cc=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