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] Kansas to build its first IXP
Date: Thu, 22 Feb 2024 01:03:10 +0100 [thread overview]
Message-ID: <BBF9E88A-1F43-43EB-9D15-C878A6C40F6B@pch.net> (raw)
In-Reply-To: <07CC415A-D934-464E-B807-DD0972D82628@pch.net>
[-- Attachment #1: Type: text/plain, Size: 2039 bytes --]
> On Dec 3, 2023, at 10:43, Bill Woodcock via Nnagain <nnagain@lists.bufferbloat.net> wrote:
>> On Dec 2, 2023, at 21:08, Dave Taht via Nnagain <nnagain@lists.bufferbloat.net> wrote:
>> This is wonderful. It hits all the high notes (accurately). The interview also. Go Kansas!!!
> I’m curious what they’re planning to do with the $4,992,000 that isn’t needed for the IXP.
So Hunter and I talked today, and the rest of the money is going to a small modular datacenter and the supporting systems for it, which sounds reasonable given the dearth of appropriate space in Wichita.
It looks like there was a “Wichita Data” DC from 2005-2017 in an office building at 209 E. William, and they might have briefly had a space in the office building at 125 N. Market Street, but they’re long gone. What I see currently available are:
A small one in an office suite, well-located at 245 N. Waco: https://uvsinc.com/concergent-it-a-division-of-uvs/
A small purpose-specific datacenter at 3622 E. Bayley, a couple miles outside the city center, with about 12,000 sq ft gross.
There’s a managed-IT-services place in an industrial park building at 8201 E 34th Cir N, seven miles NE of the city center, with about 7,000 sq ft gross, but it’s not clear that they sell any datacenter services. https://www.isgtech.com
The location Hunter is planning to build out is on the campus of Wichita State University, about three miles NE of the city center, and it would be small (a modular building, it sounded like somewhere in the 25-50 racks range, net), but neutral and purpose-specific.
I think the confusion arises from the conflation of datacenter and IXP, which is a complicated issue, and comes up a lot. Hunter and I are going to talk more tomorrow.
In general, I’m pro-IXP, and in general, I’m pro-datacenter. But they generally need to be in different places and have very different requirements, so when they get conflated, it get confusing quickly.
-Bill
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-02-22 0:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 20:08 Dave Taht
2023-12-03 9:43 ` Bill Woodcock
2024-02-22 0:03 ` Bill Woodcock [this message]
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=BBF9E88A-1F43-43EB-9D15-C878A6C40F6B@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