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: Dave Cohen <craetdave@gmail.com>
Cc: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>,
	"Brent Legg" <blegg@connectednation.org>
Subject: Re: [NNagain] The Whys of the Wichita IXP Project
Date: Fri, 23 Feb 2024 01:51:47 +0100	[thread overview]
Message-ID: <673B3FF2-1FD8-4CB8-9726-70785B1CBFC0@pch.net> (raw)
In-Reply-To: <CA34BCCB-E2F5-42D0-8D89-1B3A1E65F7AB@gmail.com>

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

> On Feb 23, 2024, at 01:09, Dave Cohen <craetdave@gmail.com> wrote:
> Prior to roughly 2016-17, most IXs in the US that we worked with were in a single site

The vast majority of IXPs are still in a single site, but all the ones with normal switch-fabric extension policies are on a growth path to multiple sites, provided the markets they’re in are of sufficient size to support it.  Both of those things have been the case for more than thirty years.

> …that site was often not a third-party facility, often a private R&E oriented datacenter.

Can you explain in more words what you’re saying here?  IXPs spring up in all kinds of sites…  Many of them are in closets of buildings which happen to have multiple ISPs already present because all of the ISPs already have customers in the building.  Some of them are in datacenters, and some of those are “neutral” datacenters, while others are owned or operated by one of the participating networks, and others are governmental or academic.  There’s a very wide diversity of IXP siting arrangements, and often individual IXPs are spread across several different kinds of sites; that’s always been the case.

Over time, existing IXPs, as they grow, tend to spread across more sites; but also, new IXPs form, which almost always form in a single location before growing to multiple sites.  IXPs that _start_ organically in multiple sites simultaneously certainly aren’t common.

                                -Bill


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

  reply	other threads:[~2024-02-23  0:51 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 [this message]
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=673B3FF2-1FD8-4CB8-9726-70785B1CBFC0@pch.net \
    --to=woody@pch.net \
    --cc=blegg@connectednation.org \
    --cc=craetdave@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