From: "David Fernández" <davidfdzp@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] [Bloat] On fiber as critical infrastructure w/Comcast chat
Date: Mon, 27 Mar 2023 10:45:09 +0200 [thread overview]
Message-ID: <CAC=tZ0qf_mdNK7zOddp4W=r5ErryW3xuGJk-Q7oryy4y56Jjgw@mail.gmail.com> (raw)
>> The point of the thread is that we still do not treat digital
>> communications infrastructure as life support critical.
5G has MCx. Fire alarms should be an MCx application of 5G.
x does stand for several mission critical (mc) services like PTT (push
to talk, meaning voice), data, video and other services.
Regards,
David
> Date: Sun, 26 Mar 2023 12:34:11 +0200
> From: Sebastian Moeller <moeller0@gmx.de>
> To: rjmcmahon <rjmcmahon@rjmcmahon.com>
> Cc: Rpm <rpm@lists.bufferbloat.net>, dan <dandenson@gmail.com>,
> Frantisek Borsik <frantisek.borsik@gmail.com>, brandon@rd.bbc.co.uk,
> libreqos <libreqos@lists.bufferbloat.net>, Dave Taht via Starlink
> <starlink@lists.bufferbloat.net>, bloat <bloat@lists.bufferbloat.net>
> Subject: Re: [Starlink] [Bloat] On fiber as critical infrastructure
> w/Comcast chat
> Message-ID: <6EB62755-EF23-44BA-B2FF-66FAC708653D@gmx.de>
> Content-Type: text/plain; charset=us-ascii
>
> Hi Bob,
>
>
>> On Mar 25, 2023, at 21:43, rjmcmahon <rjmcmahon@rjmcmahon.com> wrote:
>>
>> It's not just one phone call. I've been figuring this out for about two
>> years now. I've been working with some strategic people in Boston, colos &
>> dark fiber providers, and professional installers that wired up many of
>> the Boston universities, some universities themselves to offer co-ops to
>> students to run networsk, trainings for DIC and other high value IoT
>> offerings, blue collar principals (with staffs of about 100) to help them
>> learn to install fiber and provide better jobs for their employees.
>>
>> My conclusion is that Comcast is best suited for the job as the broadband
>> provider, at least in Boston, for multiple reasons. One chat isn't going
>> to block me ;)
>
> Yes, but they clearly are not the party best selected to to the internal
> wiring... this is a question of incentives and cost... if you pay their
> technicians by the hour to do the internal wiring according to your plan
> (assuming that they would accept that) then your goals are aligned, if the
> cost of the installation is to be carried by the ISP, they likely are
> motivated to the the kind of job I saw in California*.
> Over here the situation is slightly different, in-house cabling from the
> first demarking socket (which is considered to be ISP owned) is clearly the
> responsibility of the owner/resident not the ISP. ISPs offer to route
> cables, but on a per-hour basis, or for MDUs often used to make contracts
> with the owner that they would build the internal wiring (in an agreed upon
> fashion) for the right to be sole provider of e.g. cable TV services (with
> the cable fees mandatorily folded into the rent) for a fixed multi-year
> period (10-15 IIRC), after that the plant would end-up property of the
> building owner. Recent changes in law made the "mandatory cable fees as part
> of the rent" much harder/impossible, turning the in-house wiring back into
> an owner/resident problem.
>
>
>>
>> The point of the thread is that we still do not treat digital
>> communications infrastructure as life support critical.
>
> Well, let's keep things in perspective, unlike power, water (fresh and
> waste), and often gas, communications infrastructure is mostly not critical
> yet. But I agree that we are clearly on a path in that direction, so it is
> time to look at that from a different perspective.
> Personally, I am a big fan of putting the access network into communal
> hands, as these guys already do a decent job with other critical
> infrastructure (see list above, plus roads) and I see a PtP fiber access
> network terminating in some CO-like locations a viable way to allow ISPs to
> compete in the internet service field all the while using the communally
> build access network for a few. IIRC this is how Amsterdam organized its
> FTTH roll-out. Just as POTS wiring has beed essentially unchanged for
> decades, I estimate that current fiber access lines would also last for
> decades requiring no active component changes in the field, making them
> candidates for communal management. (With all my love for communal ownership
> and maintenance, these typically are not very nimble and hence best when we
> talk about life times of decades).
>
>
>> It reminds me of Elon Musk and his claims on FSD.
>
> ;) I had to look up FSD, I guess full self driving (aka pie-in-the-sky)?
>
>
>> I could do the whole thing myself - but that's not going to achieve what's
>> needed. We need systems that our loved ones can call and those systems
>> will care for them. Similar to how the medical community works, though
>> imperfect, in caring for our loved one's and their healths.
>
> I think I get your point. The question is how do we get from where we are
> now to that place your are describing here and in the FiWi concept?
>
>
>> I think we all are responsible for changing our belief sets & developing
>> ourselves to better serve others. Most won't act until they can actually
>> see what's possible. So let's start to show them.
>
> Sure, having real implemented examples always helps!
>
> Regards
> Sebastian
>
>
>>
>> Bob
>
>
> P.S.: Bruce's point about placing ducts/conduits seems like to only way to
> gain some future-proofeness. For multi-story and/or multi-dweller units this
> introduces the question how to stop fire using these conduits to "jump"
> between levels, but I assume that is a solved problem already, and can be
> squelches with throwing money in its direction.
>
>
>
> *)A IIRC charter technician routing coaxial cable on the outside of the two
> story building and drilling through the (wooden) wall to set the cable
> socket inside, all the while casually cutting the Dish coaxial cable that
> was still connected to a satellite dish... Not that I cared, we were using
> ADSL at the time, and in accordance with the old "when in Rome..." rule, I
> bridged over the deteriorated in-house phone wiring by running a 30m Cat5
> cable on the outside of the building to the first hand-over box.
>
>
>>
>>> Hi Bob,
>>> somewhat sad. Have you considered that your described requirements and
>>> the use-case might be outside of the mass-market envelope for which
>>> the big ISPs taylor/rig their processes? Maybe, not sure that is an
>>> option, if you approach this as a "business"* asking for a fiber
>>> uplink for an already "wired" 5 unit property you might get better
>>> service? You still would need to do the in-house re-wiring, but you
>>> likely would avoid scripted hot-lines that hang up when in the
>>> allotted time the agent sees little chance of "closing" the call. All
>>> (big) ISPs I know treat hotline as a cost factor and not as the first
>>> line of customer retention...
>>> I would also not be amazed if Boston had smaller ISPs that are willing
>>> and able to listen to customers (but that might be a bit more
>>> expensive than the big ISPs).
>>> That or try to get your foot into Comcast's PR department to sell them
>>> on the "reference installation" for all Boston historic buildings, so
>>> they can offset the custom tailoring effort with the expected good
>>> press of doing the "right thing" publicly.
>>> Good luck
>>> Sebastian
>>> *) I understand you are not, but I assume the business units to have
>>> more leeway to actually offer more bespoke solutions than the likely
>>> cost-optimized to Mars and back residental customer unit.
>>>> On Mar 25, 2023, at 20:39, rjmcmahon via Bloat
>>>> <bloat@lists.bufferbloat.net> wrote:
>>>> Hi All,
>>>> I've been trying to modernize a building in Boston where I'm an HOA
>>>> board member over the last 18 mos. I perceive the broadband network as a
>>>> critical infrastructure to our 5 unit building.
>>>> Unfortunately, Comcast staff doesn't seem to agree. The agent basically
>>>> closed the chat on me mid-stream (chat attached.) I've been at this for
>>>> about 18 mos now.
>>>> While I think bufferbloat is a big issue, the bigger issue is that our
>>>> last-mile providers must change their cultures to understand that life
>>>> support use cases that require proper pathways, conduits & cabling can
>>>> no longer be ignored. These buildings have coaxial thrown over the
>>>> exterior walls done in the 80s then drilling holes without consideration
>>>> of structures. This and the lack of environmental protections for our
>>>> HOA's critical infrastructure is disheartening. It's past time to remove
>>>> this shoddy work on our building and all buildings in Boston as well as
>>>> across the globe.
>>>> My hope was by now I'd have shown through actions what a historic
>>>> building in Boston looks like when we, as humans in our short lives, act
>>>> as both stewards of history and as responsible guardians to those that
>>>> share living spaces and neighborhoods today & tomorrow. Motivating
>>>> humans to better serve one another is hard.
>>>> Bob<comcast.pdf>_______________________________________________
>>>> Bloat mailing list
>>>> Bloat@lists.bufferbloat.net
>>>> https://lists.bufferbloat.net/listinfo/bloat
next reply other threads:[~2023-03-27 8:45 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 8:45 David Fernández [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-17 19:19 [Starlink] [Rpm] On FiWi rjmcmahon
2023-03-17 20:37 ` Bruce Perens
2023-03-17 20:57 ` rjmcmahon
2023-03-17 22:50 ` Bruce Perens
2023-03-18 18:18 ` rjmcmahon
2023-03-18 19:57 ` [Starlink] [LibreQoS] " dan
2023-03-18 20:40 ` rjmcmahon
2023-03-19 10:26 ` Michael Richardson
[not found] ` <CAJUtOOgC8O2jvT7eZ0O8nU8kCPOeCgVPTBNKaA3ZqLpJf4obJw@mail.gmail.com>
2023-03-20 21:28 ` [Starlink] [Rpm] [LibreQoS] " dan
2023-03-21 0:10 ` Brandon Butterworth
2023-03-21 12:30 ` Sebastian Moeller
2023-03-21 17:42 ` rjmcmahon
2023-03-21 18:08 ` rjmcmahon
[not found] ` <CAJUtOOiMk+PBK2ZRFsZA8EFEgqfHY3Zpw9=kAkJZpePx9OzeMw@mail.gmail.com>
2023-03-21 19:58 ` rjmcmahon
2023-03-25 19:39 ` [Starlink] On fiber as critical infrastructure w/Comcast chat rjmcmahon
2023-03-25 20:15 ` [Starlink] [Bloat] " Sebastian Moeller
2023-03-25 20:43 ` rjmcmahon
2023-03-25 21:08 ` Bruce Perens
2023-03-25 22:04 ` Robert McMahon
2023-03-25 22:50 ` dan
2023-03-25 23:21 ` Robert McMahon
2023-03-25 23:35 ` David Lang
2023-03-26 0:04 ` Robert McMahon
2023-03-26 0:07 ` Nathan Owens
2023-03-26 0:50 ` Robert McMahon
2023-03-26 8:45 ` Livingood, Jason
2023-03-26 18:54 ` rjmcmahon
2023-03-26 0:28 ` David Lang
2023-03-26 0:57 ` Robert McMahon
2023-03-25 22:57 ` Bruce Perens
2023-03-25 23:33 ` David Lang
2023-03-25 23:38 ` Robert McMahon
2023-03-25 23:20 ` David Lang
2023-03-26 18:29 ` rjmcmahon
2023-03-26 10:34 ` Sebastian Moeller
2023-03-26 18:12 ` rjmcmahon
2023-03-26 20:57 ` David Lang
2023-03-26 21:11 ` Sebastian Moeller
2023-03-26 21:26 ` David Lang
2023-03-28 17:06 ` Larry Press
2023-03-28 17:47 ` rjmcmahon
2023-03-28 18:11 ` Frantisek Borsik
2023-03-28 18:46 ` rjmcmahon
2023-03-28 20:37 ` David Lang
2023-03-28 21:31 ` rjmcmahon
2023-03-28 22:18 ` dan
2023-03-28 22:42 ` rjmcmahon
2023-03-29 8:28 ` Sebastian Moeller
2023-03-29 12:27 ` Dave Collier-Brown
2023-03-29 13:22 ` Doc Searls
2023-03-29 13:46 ` Frantisek Borsik
2023-03-29 19:02 ` rjmcmahon
2023-03-29 19:37 ` dan
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAC=tZ0qf_mdNK7zOddp4W=r5ErryW3xuGJk-Q7oryy4y56Jjgw@mail.gmail.com' \
--to=davidfdzp@gmail.com \
--cc=starlink@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