Many ISPs need the kinds of quality shaping cake can do
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: libreqos <libreqos@lists.bufferbloat.net>
Subject: [LibreQoS] Fwd: [AusNOG] curious about lessons learned from your fiber rollouts?
Date: Wed, 29 Mar 2023 17:34:00 -0700	[thread overview]
Message-ID: <CAA93jw6Xi-M7x_r9KK0NxtkWOVp+WJDLb6+i8FP=FSuk-SUU=w@mail.gmail.com> (raw)
In-Reply-To: <CAOSsYkqBftyJiQa42+GAncZku5c-BwRT9seBWcDbjfpsRO74gA@mail.gmail.com>

---------- Forwarded message ---------
From: John Edwards <jaedwards@gmail.com>
Date: Wed, Mar 29, 2023 at 5:22 PM
Subject: Re: [AusNOG] curious about lessons learned from your fiber rollouts?
To: Dave Taht <dave.taht@gmail.com>
Cc: <ausnog@lists.ausnog.net> <ausnog@lists.ausnog.net>


My tips:

Rural networks are economically tentative at the best of times, they
are low density and the majority of the demographic that they serve
don't have disposable income for tech entertainment. Government
funding likes to be directed to announceables, and nobody announces a
maintenance plan. Budget accordingly.

Driving time for maintenance personnel is going to become the majority
of your operating budget. Build networks to be bulletproof and have no
need for maintenance, and consider that the added expense of a ring
topology or diverse path might still cost less than a single
unscheduled callout by a contractor. For a rural network, redundant
systems buy time to attend to outages on more relaxed timelines.

Fixed wireless
- is all about waterproofing, be it customer rooftops, cabling joints
or especially equipment shelters.
- rigging teams are at the mercy of safety standards, weather and
personal leave, so you can't expect more than 100 days/year of
productive work
- a certain type of person wants to climb towers all day, and they may
not be productive if you try and force them into a soft office
environment on the other days of the year

Fibre Networks
- use a conduit that is a size larger than you need. If you have any
kind of success you're going to need a second cable in that conduit at
some point, even if it's just to do a graceful upgrade
- always use a fibre cleaning kit
- with single-fibre optics (ie: BX), put the transceiver that sends at
a lower frequency at the far end. This gives you a chance to spot the
difference between a fibre fault and a power fault

John



On Thu, 30 Mar 2023 at 02:19, Dave Taht <dave.taht@gmail.com> wrote:
>
> I am doing an AMA friday, in part about the $70B dollar USA NTIA
> broadband and BEAD programs, which are largely targetted at improving
> rural access to the internet. The target audience is one with which I
> am mostly unfamiliar, the directors of the 50 US states administering
> these programs.
>
> I am very interested about what y'all have learned about how to roll
> out fiber and fixed wireless right, in your country, so far, and what
> could be done better, in mine.
>
> Please let me know what you think here, (links to studies would be
> great, too)
>
> and/or come heckle!
>
> --
> AMA March 31: https://www.broadband.io/c/broadband-grant-events/dave-taht
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> AusNOG mailing list
> AusNOG@lists.ausnog.net
> https://lists.ausnog.net/mailman/listinfo/ausnog



-- 
AMA March 31: https://www.broadband.io/c/broadband-grant-events/dave-taht
Dave Täht CEO, TekLibre, LLC

           reply	other threads:[~2023-03-30  0:34 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAOSsYkqBftyJiQa42+GAncZku5c-BwRT9seBWcDbjfpsRO74gA@mail.gmail.com>]

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='CAA93jw6Xi-M7x_r9KK0NxtkWOVp+WJDLb6+i8FP=FSuk-SUU=w@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=libreqos@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