From: Mike Hammett <nanog@ics-il.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>,
libreqos <libreqos@lists.bufferbloat.net>,
NANOG <nanog@nanog.org>
Subject: Re: [LibreQoS] transit and peering costs projections
Date: Sun, 15 Oct 2023 08:38:21 -0500 (CDT) [thread overview]
Message-ID: <1241680682.954.1697377096485.JavaMail.mhammett@Thunderfuck2> (raw)
In-Reply-To: <CAA93jw5CqXvn0-CwbDpBxQ2WRcEMQmCSU2+LK6aqxVzZwKt2xA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1801 bytes --]
I've seen some attempts to put an IX at every corner, but I don't think those efforts will be overly successful.
It's still difficult to gain sufficient scale in NFL-sized cities. Big content won't join without big eyeballs (well, not the national-level guys because they almost never will). Big eyeballs just can't be bothered. Small guys don't move the needle enough.
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest-IX
http://www.midwest-ix.com
----- Original Message -----
From: "Dave Taht" <dave.taht@gmail.com>
To: "Network Neutrality is back! Let´s make the technical aspects heard this time!" <nnagain@lists.bufferbloat.net>, "libreqos" <libreqos@lists.bufferbloat.net>, "NANOG" <nanog@nanog.org>
Sent: Saturday, October 14, 2023 6:01:54 PM
Subject: transit and peering costs projections
This set of trendlines was very interesting. Unfortunately the data
stops in 2015. Does anyone have more recent data?
https://drpeering.net/white-papers/Internet-Transit-Pricing-Historical-And-Projected.php
I believe a gbit circuit that an ISP can resell still runs at about
$900 - $1.4k (?) in the usa? How about elsewhere?
...
I am under the impression that many IXPs remain very successful,
states without them suffer, and I also find the concept of doing micro
IXPs at the city level, appealing, and now achievable with cheap gear.
Finer grained cross connects between telco and ISP and IXP would lower
latencies across town quite hugely...
PS I hear ARIN is planning on dropping the price for, and bundling 3
BGP AS numbers at a time, as of the end of this year, also.
--
Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
Dave Täht CSO, LibreQos
[-- Attachment #2: Type: text/html, Size: 2271 bytes --]
prev parent reply other threads:[~2023-10-15 13:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-14 23:01 Dave Taht
2023-10-15 0:25 ` [LibreQoS] [NNagain] " Dave Cohen
2023-10-15 3:45 ` [LibreQoS] " Tim Burke
2023-10-15 4:03 ` Ryan Hamel
2023-10-15 4:12 ` Tim Burke
2023-10-15 4:19 ` Dave Taht
2023-10-15 4:26 ` dan
2023-10-15 7:54 ` Bill Woodcock
2023-10-15 13:41 ` Mike Hammett
2023-10-15 14:19 ` Tim Burke
2023-10-15 16:44 ` dan
2023-10-15 16:32 ` Tom Beecher
2023-10-15 19:19 ` Tim Burke
2023-10-15 7:40 ` Bill Woodcock
2023-10-15 12:40 ` Jim Troutman
2023-10-15 14:12 ` Tim Burke
2023-10-15 13:38 ` Mike Hammett [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/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1241680682.954.1697377096485.JavaMail.mhammett@Thunderfuck2 \
--to=nanog@ics-il.net \
--cc=dave.taht@gmail.com \
--cc=libreqos@lists.bufferbloat.net \
--cc=nanog@nanog.org \
--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