Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: Bill Woodcock <woody@pch.net>
To: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Cc: rjmcmahon <rjmcmahon@rjmcmahon.com>,
	Brent Legg <blegg@connectednation.org>
Subject: Re: [NNagain] The Whys of the Wichita IXP Project
Date: Fri, 23 Feb 2024 00:31:18 +0100	[thread overview]
Message-ID: <71924C54-A1AA-421F-B9A3-738DC04E8412@pch.net> (raw)
In-Reply-To: <f9f784f0bfe7093246ed5d9f34fd3a3b@rjmcmahon.com>

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



> On Feb 22, 2024, at 19:58, rjmcmahon via Nnagain <nnagain@lists.bufferbloat.net> wrote:
> Boston University spent $305M on this and it doesn't have an IXP.
> https://www.bu.edu/articles/2022/center-for-computing-and-data-sciences-photo-essay/
> It's like building a magnificent train station w/o any tracks to/fro the station.

Most datacenters don’t contain IXPs, and most IXPs aren’t located in datacenters.  It’s very financially advantageous for a neutral multi-tenant datacenter to contain an IXP, but generally much less advantageous for an IXP to be located in a datacenter.  Datacenters tend to concentrate content, but that content can be transported to an IXP over just a few strands of fiber.  Whereas eyeballs have to be physically aggregated, and that’s over thousands of strands, so the average distance to eyeballs matters, whereas the average distance to content just doesn’t have a significant multiplier on it, and the content is portable anyway.  The optimum location for an IXP is in a city center, whereas the optimum location for a datacenter (all political, zoning, and real-estate factors considered) is typically in an industrial park well outside the city core.

Lots of organizations need a datacenter for their own use, and universities are typical in that.  It doesn’t mean that they’d make sense as locations for an IXP, unless they’re also aggregating a lot of eyeball fiber for some reason.

                                -Bill


[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-02-22 23:31 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 [this message]
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
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=71924C54-A1AA-421F-B9A3-738DC04E8412@pch.net \
    --to=woody@pch.net \
    --cc=blegg@connectednation.org \
    --cc=nnagain@lists.bufferbloat.net \
    --cc=rjmcmahon@rjmcmahon.com \
    /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