From: Bill Woodcock <woody@pch.net>
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: Sun, 25 Feb 2024 07:04:26 +0100 [thread overview]
Message-ID: <DC4C70A3-B692-4023-BCDE-8BCE7E30720F@pch.net> (raw)
In-Reply-To: <730e404c-f7ef-4845-a634-71fb0505e3c8@rjmcmahon.com>
[-- Attachment #1: Type: text/plain, Size: 1507 bytes --]
> On Feb 24, 2024, at 20:30, Robert McMahon via Nnagain <nnagain@lists.bufferbloat.net> wrote:
>> On Feb 24, 2024, at 4:05 AM, Fearghas Mckay <fearghas@gmail.com> 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 ?
> For education and modeling. Students used to run on campus radio stations as an example. A modern world requires understanding things like IXPs.
That’s a good point. When we do IXP formation workshops, if there are very many ASes which haven’t peered before, we do get the whole thing up and running on a meeting-room table in a classroom sort of situation, before trying to do it in production. And we’ve done joint projects between IXPs and departments of education. So this is a very good reason for a university to host a small-scale or lab IXP. But it’s also a good reason to forge a relationship with nearby production IXPs, such that student projects can get access to no-cost local bandwidth, etc.
Students getting access to distance-insensitive bandwidth at universities causes a lot of startups to crash-and-burn when they start to scale up and find out that the Internet isn’t flat, it just looks that way when you’re buying small amounts at retail.
-Bill
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-02-25 6:04 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
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 [this message]
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=DC4C70A3-B692-4023-BCDE-8BCE7E30720F@pch.net \
--to=woody@pch.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