Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
* Re: [Starlink] [Bloat] On fiber as critical infrastructure w/Comcast chat
@ 2023-03-27  8:45 David Fernández
  0 siblings, 0 replies; 39+ messages in thread
From: David Fernández @ 2023-03-27  8:45 UTC (permalink / raw)
  To: starlink

>> 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

^ permalink raw reply	[flat|nested] 39+ messages in thread
* Re: [Starlink] [Rpm]    On FiWi
@ 2023-03-17 19:19 rjmcmahon
  2023-03-17 20:37 ` Bruce Perens
  0 siblings, 1 reply; 39+ messages in thread
From: rjmcmahon @ 2023-03-17 19:19 UTC (permalink / raw)
  To: Sebastian Moeller
  Cc: Dave Täht, Dave Taht via Starlink, Mike Puchol, bloat, Rpm,
	libreqos

I think the low-power transceiver (or RRH) and fiber fronthaul is doable 
within the next 5 years. The difficult part to me seems the virtual APs 
that could service 12-256 RRHs including security monitoring & customer 
privacy.

Is there a VMWARE NSX approach to reducing the O&M costs by at least 1/2 
for the FiWi head end systems?

For power: My approach to the Boston historic neighborhood where my kids 
now live would be AC wired CPE treated as critical, life support 
infrastructure. But better may be to do as modern garage door openers 
and have standard AC charge a battery so one can operate even during 
power outages.

https://www.rsandrews.com/blog/hardwired-battery-powered-smoke-alarms-you/

Our Recommendation: Hardwired Smoke Alarms
Hardwired smoke alarms, while they require slightly more work upfront, 
are the clear choice if you’re considering replacing your home’s smoke 
alarm system. You’ll hardly ever have to deal with the annoying 
“chirping” that occurs when a battery-powered smoke detector begins to 
go dead, and your entire family will be alerted in the event that a fire 
does occur since hardwire smoke detectors can be interconnected.

Bob
> Hi Dave,
> 
> 
> 
>> On Mar 17, 2023, at 17:38, Dave Taht via Starlink 
>> <starlink@lists.bufferbloat.net> wrote:
>> 
>> This is a pretty neat box:
>> 
>> https://mikrotik.com/product/netpower_lite_7r
>> 
>> What are the compelling arguments for fiber vs copper, again?
> 
> 	As far as I can tell:
> 
> Copper:
> 	can carry electric power
> 
> Fiber-PON:
> 	much farther reach even without amplifiers (10 Km, 20 Km, ...
> depending on loss budget)
> 	cheaper operation (less active power needed by the headend/OLT)
> 	less space need than all active alternatives (AON, copper ethernet)
> 	likely only robust passive components in the field
> 	Existing upgrade path for 25G and 50G is on the horizon over the same
> PON infrastructure
> 	mostly resistant to RF ingress along the path (as long as a direct
> lightning hit does not melt the glas ;) )
> 
> Fiber-Ethernet:
> 	like fiber-PON but
> 	no density advantage (needs 1 port per end device)
> 	even wider upgrade paths
> 
> 
> I guess it really depends on how important "carry electric power" is
> to you ;) feeding these from the client side is pretty cool for
> consenting adults, but I would prefer not having to pay the electric
> bill for my ISPs active gear in the field outside the CPE/ONT...
> 
> Regards
> 	Sebastian
> 
> 
>> 
>> 
>> On Tue, Mar 14, 2023 at 4:10 AM Mike Puchol via Rpm 
>> <rpm@lists.bufferbloat.net> wrote:
>> Hi Bob,
>> 
>> You hit on a set of very valid points, which I'll complement with my 
>> views on where the industry (the bit of it that affects WISPs) is 
>> heading, and what I saw at the MWC in Barcelona. Love the FiWi term 
>> :-)
>> 
>> I have seen the vendors that supply WISPs, such as Ubiquiti, Cambium, 
>> and Mimosa, but also newer entrants such as Tarana, increase the 
>> performance and on-paper specs of their equipment. My examples below 
>> are centered on the African market, if you operate in Europe or the 
>> US, where you can charge customers a higher install fee, or even 
>> charge them a break-up fee if they don't return equipment, the 
>> economics work.
>> 
>> Where currently a ~$500 sector radio could serve ~60 endpoints, at a 
>> cost of ~$50 per endpoint (I use this term in place of ODU/CPE, the 
>> antenna that you mount on the roof), and supply ~2.5 Mbps CIR per 
>> endpoint, the evolution is now a ~$2,000+ sector radio, a $200 
>> endpoint, capability for ~150 endpoints per sector, and ~25 Mbps CIR 
>> per endpoint.
>> 
>> If every customer a WISP installs represents, say, $100 CAPEX at 
>> install time ($50 for the antenna + cabling, router, etc), and you 
>> charge a $30 install fee, you have $70 to recover, and you recover 
>> from the monthly contribution the customer makes. If the contribution 
>> after OPEX is, say, $10, it takes you 7 months to recover the full 
>> install cost. Not bad, doable even in low-income markets.
>> 
>> Fast-forward to the next-generation version. Now, the CAPEX at install 
>> is $250, you need to recover $220, and it will take you 22 months, 
>> which is above the usual 18 months that investors look for.
>> 
>> The focus, thereby, has to be the lever that has the largest effect on 
>> the unit economics - which is the per-customer cost. I have drawn what 
>> my ideal FiWi network would look like:
>> 
>> 
>> <Hybrid EPON-Wireless network.png>
>> Taking you through this - we start with a 1-port, low-cost EPON OLT 
>> (or you could go for 2, 4, 8 ports as you add capacity). This OLT has 
>> capacity for 64 ONUs on its single port. Instead of connecting the 
>> typical fiber infrastructure with kilometers of cables which break, 
>> require maintenance, etc. we insert an EPON to Ethernet converter (I 
>> added "magic" because these don't exist AFAIK).
>> 
>> This converter allows us to connect our $2k sector radio, and serve 
>> the $200 endpoints (ODUs) over wireless point-to-multipoint up to 10km 
>> away. Each ODU then has a reverse converter, which gives us EPON 
>> again.
>> 
>> Once we are back on EPON, we can insert splitters, for example, 
>> pre-connectorized outdoor 1:16 boxes. Every customer install now 
>> involves a 100 meter roll of pre-connectorized 2-core drop cable, and 
>> a $20 EPON ONU.
>> 
>> Using this deployment method, we could connect up to 16 customers to a 
>> single $200 endpoint, so the enpoint CAPEX per customer is now $12.5. 
>> Add the ONU, cable, etc. and we have a per-install CAPEX of $82.5 
>> (assuming the same $50 of extras we had before), and an even shorter 
>> break-even. In addition, as the endpoints support higher capacity, we 
>> can provision at least the same, if not more, capacity per customer.
>> 
>> Other advantages: the $200 ODU is no longer customer equipment and 
>> CAPEX, but network equipment, and as such, can operate under a longer 
>> break-even timeline, and be financed by infrastructure PE funds, for 
>> example. As a result, churn has a much lower financial impact on the 
>> operator.
>> 
>> The main reason why this wouldn't work today is that EPON, as we know, 
>> is synchronous, and requires the OLT to orchestrate the amount of time 
>> each ONU can transmit, and when. Having wireless hops and media 
>> conversions will introduce latencies which can break down the 
>> communications (e.g. one ONU may transmit, get delayed on the radio 
>> link, and end up overlapping another ONU that transmitted on the next 
>> slot). Thus, either the "magic" box needs to account for this, or an 
>> new hybrid EPON-wireless protocol developed.
>> 
>> My main point here: the industry is moving away from the unconnected. 
>> All the claims I heard and saw at MWC about "connecting the 
>> unconnected" had zero resonance with the financial drivers that the 
>> unconnected really operate under, on top of IT literacy, digital 
>> skills, devices, power...
>> 
>> Best,
>> 
>> Mike
>> On Mar 14, 2023 at 05:27 +0100, rjmcmahon via Starlink 
>> <starlink@lists.bufferbloat.net>, wrote:
>>> To change the topic - curious to thoughts on FiWi.
>>> 
>>> Imagine a world with no copper cable called FiWi (Fiber,VCSEL/CMOS
>>> Radios, Antennas) and which is point to point inside a building
>>> connected to virtualized APs fiber hops away. Each remote radio head
>>> (RRH) would consume 5W or less and only when active. No need for 
>>> things
>>> like zigbee, or meshes, or threads as each radio has a fiber 
>>> connection
>>> via Corning's actifi or equivalent. Eliminate the AP/Client power
>>> imbalance. Plastics also can house smoke or other sensors.
>>> 
>>> Some reminders from Paul Baran in 1994 (and from David Reed)
>>> 
>>> o) Shorter range rf transceivers connected to fiber could produce a
>>> significant improvement - - tremendous improvement, really.
>>> o) a mixture of terrestrial links plus shorter range radio links has 
>>> the
>>> effect of increasing by orders and orders of magnitude the amount of
>>> frequency spectrum that can be made available.
>>> o) By authorizing high power to support a few users to reach slightly
>>> longer distances we deprive ourselves of the opportunity to serve the
>>> many.
>>> o) Communications systems can be built with 10dB ratio
>>> o) Digital transmission when properly done allows a small signal to
>>> noise ratio to be used successfully to retrieve an error free signal.
>>> o) And, never forget, any transmission capacity not used is wasted
>>> forever, like water over the dam. Not using such techniques represent
>>> lost opportunity.
>>> 
>>> And on waveguides:
>>> 
>>> o) "Fiber transmission loss is ~0.5dB/km for single mode fiber,
>>> independent of modulation"
>>> o) “Copper cables and PCB traces are very frequency dependent. At
>>> 100Gb/s, the loss is in dB/inch."
>>> o) "Free space: the power density of the radio waves decreases with 
>>> the
>>> square of distance from the transmitting antenna due to spreading of 
>>> the
>>> electromagnetic energy in space according to the inverse square law"
>>> 
>>> The sunk costs & long-lived parts of FiWi are the fiber and the CPE
>>> plastics & antennas, as CMOS radios+ & fiber/laser, e.g. VCSEL could 
>>> be
>>> pluggable, allowing for field upgrades. Just like swapping out SFP in 
>>> a
>>> data center.
>>> 
>>> This approach basically drives out WiFi latency by eliminating shared
>>> queues and increases capacity by orders of magnitude by leveraging 
>>> 10dB
>>> in the spatial dimension, all of which is achieved by a physical 
>>> design.
>>> Just place enough RRHs as needed (similar to a pop up sprinkler in an
>>> irrigation system.)
>>> 
>>> Start and build this for an MDU and the value of the building 
>>> improves.
>>> Sadly, there seems no way to capture that value other than over long
>>> term use. It doesn't matter whether the leader of the HOA tries to
>>> capture the value or if a last mile provider tries. The value remains
>>> sunk or hidden with nothing on the asset side of the balance sheet.
>>> We've got a CAPEX spend that has to be made up via "OPEX returns" 
>>> over
>>> years.
>>> 
>>> But the asset is there.
>>> 
>>> How do we do this?
>>> 
>>> Bob
>>> _______________________________________________
>>> Starlink mailing list
>>> Starlink@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/starlink
>> _______________________________________________
>> Rpm mailing list
>> Rpm@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/rpm
>> 
>> 
>> --
>> Come Heckle Mar 6-9 at: https://www.understandinglatency.com/
>> Dave Täht CEO, TekLibre, LLC
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/starlink
> 
> _______________________________________________
> Rpm mailing list
> Rpm@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/rpm

^ permalink raw reply	[flat|nested] 39+ messages in thread

end of thread, other threads:[~2023-03-29 19:37 UTC | newest]

Thread overview: 39+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-03-27  8:45 [Starlink] [Bloat] On fiber as critical infrastructure w/Comcast chat David Fernández
  -- 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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox