From: Mark Steckel <mjs@phillywisper.net>
To: "\"Network Neutrality is back! Let´s make the technical aspects
heard this time!\"" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] The non-death of DSL
Date: Sat, 07 Oct 2023 17:34:03 -0400 [thread overview]
Message-ID: <18b0c0fca5a.df21b356967361.3801960253537018542@phillywisper.net> (raw)
In-Reply-To: <CAA93jw5OPSRFaWY31faKSZvFN4Rj_tSKca66MKwBZTpscER9Qg@mail.gmail.com>
My understanding, though I am not 100% certain, is that the baby bells lobbied to have the CLEC equal access provisions revoked/gutted. Before this, the telephone companies were required to provide access to the "last mile" of the copper lines and the switches at wholesale costs. Once the equal access provisions were removed, the telephone companies started charging the small phone and DSL providers close to the retail price for access. The CLEC DSL providers could not stay in business when they charged a customer $35 / month for Internet service while the telephone company charged the DSL ISP $35 / month for access.
---- On Sat, 07 Oct 2023 17:22:10 -0400 Dave Taht via Nnagain wrote ---
> I have a lot to unpack from this:
>
> https://docs.fcc.gov/public/attachments/DOC-397257A1.pdf
>
> the first two on my mind from 2005 are: "FCC adopted its first open
> internet policy" and "Competitiveness" As best as I recall, (and
> please correct me), this led essentially to the departure of all the
> 3rd party DSL providers from the field. I had found something
> referencing this interpretation that I cannot find right now, but I do
> clearly remember all the DSL services you could buy from in the early
> 00s, and how few you can buy from now. Obviously there are many other
> possible root causes.
>
> DSL continued to get better and evolve, but it definately suffers from
> many reports of degraded copper quality, but does an estimate exist
> for how much working DSL is left?
>
> Q0) How much DSL is in the EU?
> Q1) How much DSL is left in the USA?
> Q2) What form is it? (VDSL, etc?)
>
> Did competition in DSL vanish because of or not of an FCC related order?
>
> --
> Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
> Dave Täht CSO, LibreQos
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
>
next prev parent reply other threads:[~2023-10-07 21:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 21:22 Dave Taht
2023-10-07 21:34 ` Mark Steckel [this message]
2023-10-07 22:13 ` rjmcmahon
2023-10-07 23:14 ` Mark Steckel
2023-10-08 0:00 ` rjmcmahon
2023-10-08 0:44 ` rjmcmahon
2023-10-08 9:38 ` Sebastian Moeller
2023-10-08 16:37 ` Robert McMahon
2023-10-08 19:27 ` rjmcmahon
2023-10-08 20:19 ` Sebastian Moeller
2023-10-08 20:44 ` rjmcmahon
2023-10-09 7:40 ` Sebastian Moeller
2023-10-10 0:13 ` Robert McMahon
2023-10-10 6:13 ` Sebastian Moeller
2023-10-10 8:24 ` Robert McMahon
2023-10-08 19:39 ` Sebastian Moeller
2023-10-08 20:18 ` rjmcmahon
2023-10-09 6:30 ` Sebastian Moeller
2023-10-08 0:07 ` Dave Taht
2023-10-08 10:01 ` Sebastian Moeller
2023-10-08 7:14 ` Sebastian Moeller
2023-10-11 13:58 ` Mikael Abrahamsson
2023-10-12 7:25 ` Pedro Tumusok
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=18b0c0fca5a.df21b356967361.3801960253537018542@phillywisper.net \
--to=mjs@phillywisper.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