From: rjmcmahon <rjmcmahon@rjmcmahon.com>
To: dan <dandenson@gmail.com>
Cc: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>,
"Sebastian Moeller" <moeller0@gmx.de>
Subject: Re: [NNagain] On "Throttling" behaviors
Date: Tue, 03 Oct 2023 12:23:11 -0700 [thread overview]
Message-ID: <6cbc586778ec5a4ae123b6783d2cd72b@rjmcmahon.com> (raw)
In-Reply-To: <CAA_JP8VryiTvavzQyS2HrxKAdfHM-7Or5j0NvCoJ0On+v1_HcQ@mail.gmail.com>
It doesn't matter who is to blame. What matters is that it didn't work
at scale despite the political, regulatory and legal attempts per the
federal 1996 Telco Act which proved to be a naive Act even with all the
experts, including tech leaders, trying their best.
There aren't fiber cables over the last 100 meters (or more) in the OSP
and none inside buildings (other than data centers.)
Cat copper cable tops out at 10Gb/s and 100m, and 4M for 100Gb/s. We're
already releasing 200Gb/s SERDES today. And optics NRE are driving power
down to increase MTBF. The last NRE spent on 10G was done over a decade
ago. Years in technology are like dog years.
Today, for 1Gb/s it's 300 times the energy per meter using copper CAT vs
fiber. No comparison at 100G because 4M is too short for most things
except for a data center rack.
China has basically banned copper and is going fiber to and through all
buildings.
Bob
> On Tue, Oct 3, 2023 at 11:55 AM Sebastian Moeller via Nnagain
> <nnagain@lists.bufferbloat.net> wrote:
>
>> ...
>>>
>>> The idea of municipal ownership of access networks in the U.S. was
>> pushed in 2000 after the 1996 Telco act. It didn't work out.
>
> My state specifically bans municipalities from building or owning
> networks involved in internet delivery. I think about a dozen states
> do this. In my state, I think this was a specific charity by the
> governor to his buddies at spectrum so cities didn't compete against
> spectrum....
>
>>>
>>> The U.S. railroads were natural monopolies. They were given
>> massive land grants to build out. They ran as private companies for
>> about one century. They lost their monopoly position after third
>> generations who inherited them used these monopolies to price guoge
>> government during WWI and WWII. That's part of the reason most DoT
>> type govt agencies today are "roads & airports" vs "roads, rail &
>> airports." Rail has been re privatized and under invested - perfect
>> for Warren Buffett but no so good for everyone else nor for the
>> climate.
>
> I don't know that this is an appropriate conclusion. I don't think
> that any railroads were monopolies until the government gave out land
> grants and monies to build those monopolies and now they are
> absolutely government backed monopolies. Yes, railroads gouged for
> use of their lines, but that was more price collusion than monopoly.
>
>>>
>>> Governments will respond to monopoly abuse after it occurs, not
>> before.
>>
>> [SM] Indeed, that is often the case...
>
> and often WAY after and only when the government itself feels the pain
> of it.
>
>>> First, the infrastructure needs massive funding to be installed
>
>> , however that can get done. Municipal revenue bonds & networks
>> sound nice in theory but haven't worked over the last two decades.
>> Time to try something different.
>
> There is existing dark fiber through or within a few miles of
> something like 95% of US towns, down to tiny villages. The government
> has already paid lots of money out to get fiber everywhere, but then
> that fiber is not readily available to purchase. This goes back to
> the microIX model discussed on the bufferbloat list and matrix chat.
> We only need to find a way to require this fiber be sold and at
> reasonable rates to allow for competition. This really isn't a big
> infrastructure spend because that was spent 2 decades ago.
next prev parent reply other threads:[~2023-10-03 19:23 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 17:15 [NNagain] Some backstory on the nn-again mailing list Dave Taht
2023-10-01 18:56 ` Frantisek Borsik
2023-10-01 19:51 ` [NNagain] On "Throttling" behaviors Dave Taht
2023-10-01 20:50 ` Dave Cohen
2023-10-01 22:01 ` Patrick Maupin
2023-10-02 1:34 ` dan
2023-10-02 7:28 ` Sebastian Moeller
2023-10-02 16:29 ` dan
2023-10-04 7:30 ` Sebastian Moeller
2023-10-02 15:30 ` Andy Ringsmuth
2023-10-02 18:28 ` Nathan Loofbourrow
2023-10-02 20:34 ` Colin_Higbie
2023-10-02 21:04 ` Dave Cohen
2023-10-02 21:07 ` rjmcmahon
2023-10-02 21:43 ` Colin_Higbie
2023-10-02 21:55 ` rjmcmahon
2023-10-03 19:29 ` Colin_Higbie
2023-10-03 19:45 ` rjmcmahon
2023-10-04 0:57 ` David Lang
2023-10-03 7:50 ` Sebastian Moeller
2023-10-03 8:10 ` Karl Auerbach
2023-10-03 14:41 ` Sebastian Moeller
2023-10-03 15:34 ` dan
2023-10-03 16:54 ` rjmcmahon
2023-10-03 17:55 ` Sebastian Moeller
2023-10-03 18:09 ` Frantisek Borsik
2023-10-03 18:14 ` dan
2023-10-03 19:44 ` Dick Roy
2023-10-03 18:10 ` dan
2023-10-03 19:23 ` rjmcmahon [this message]
2023-10-04 1:05 ` David Lang
2023-10-04 0:39 ` David Lang
2023-10-03 20:26 ` Colin_Higbie
2023-10-03 21:40 ` dan
2023-10-04 15:56 ` Colin_Higbie
2023-10-04 17:45 ` David Lang
2023-10-05 20:24 ` Livingood, Jason
2023-10-05 22:17 ` Dick Roy
2023-10-05 22:47 ` Jeremy Austin
2023-10-05 22:53 ` Dave Cohen
2023-10-06 15:56 ` Dick Roy
2023-10-06 15:58 ` rjmcmahon
2023-10-04 17:59 ` rjmcmahon
2023-10-04 19:26 ` Dick Roy
[not found] ` <MN2PR16MB3391A66B0DC222C43664DAD6F1CBA@MN2PR16MB3391.namprd16.prod.outlook.com>
2023-10-05 8:44 ` Sebastian Moeller
2023-10-05 19:07 ` David Lang
2023-10-03 23:17 ` Mark Steckel
2023-10-04 7:51 ` Sebastian Moeller
2023-10-02 6:48 ` Sebastian Moeller
2023-10-02 13:43 ` Livingood, Jason
2023-10-02 14:51 ` Mark Steckel
2023-10-02 18:09 ` Livingood, Jason
2023-10-02 18:15 ` Patrick Maupin
2023-10-02 19:18 ` Dick Roy
2023-10-02 6:34 ` Sebastian Moeller
2023-10-02 13:27 ` Livingood, Jason
2023-10-02 6:06 ` [NNagain] Some backstory on the nn-again mailing list Sebastian Moeller
2023-10-02 12:36 ` Bless, Roland (TM)
2023-10-03 7:15 ` Sebastian Moeller
2023-10-02 20:18 [NNagain] On "Throttling" behaviors Livingood, Jason
2023-10-02 20:28 ` Dick Roy
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=6cbc586778ec5a4ae123b6783d2cd72b@rjmcmahon.com \
--to=rjmcmahon@rjmcmahon.com \
--cc=dandenson@gmail.com \
--cc=moeller0@gmx.de \
--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