Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: =?UTF-8?Q?Jonas_M=C3=A5rtensson?= <martensson.jonas@gmail.com>,
	"Sebastian Moeller" <moeller0@gmx.de>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] a smart SFP
Date: Fri, 14 Jan 2022 14:21:59 -0500	[thread overview]
Message-ID: <18327.1642188119@localhost> (raw)
In-Reply-To: <CAM9iV=LoJoQ8C_iS+dQAqAk0Jh3=mHEKL0Zc3Q5BrZjyQ__oMA@mail.gmail.com>


Jonas Mårtensson <martensson.jonas@gmail.com> wrote:
    >> getting gpon more right has increasingly been on my mind

    > I think more right is to not turn the fiber into a shared medium in the
    > first place but since gpon is so popular, improving it seems like a
    > nice goal.

    >> Nobody in their right mind is going to hook up 128 terminalt to one
    >> OLT
    > port, I hope...

    > Well, sharing one OLT port between many terminals is kind of the (only)
    > advantage of PON, although split ratios of 32 or 64 are more
    > typical. But often it's the loss budget that limits the ratio.

And, there are also situations, many of them industrial, where the fiber
allows one to avoid ground loops, and where the bandwidth/latency
requirements are very modest.
it's not all youtube downloads and zoom meetings :-)

I was involved in a GPON build back in 2010 into a very poorly served
industrial park.  (That was for email/web browsing by the industries).
A reason they were so poorly served is that there were two expressways (one
of them the TransCanada) and a river that bordered the area.
There were only eight strands in a single conduit available....
We considered moving (an) OLT into that area actually... DWDM to the rescue
in the end, but that was a bit bleeding edge at the time.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


  parent reply	other threads:[~2022-01-14 19:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 14:18 Dave Taht
2022-01-13 14:23 ` Sebastian Moeller
2022-01-13 14:38   ` Dave Taht
2022-01-13 14:51     ` Sebastian Moeller
2022-01-13 15:28       ` Dave Taht
2022-01-13 15:44         ` Sebastian Moeller
2022-01-13 15:57     ` Sebastian Moeller
2022-01-13 15:59       ` Dave Taht
2022-01-13 16:28         ` Sebastian Moeller
2022-01-14 10:44           ` Jonas Mårtensson
2022-01-14 11:55             ` Sebastian Moeller
2022-01-14 13:12               ` Jonas Mårtensson
2022-01-14 13:23                 ` Sebastian Moeller
2022-01-14 13:50                   ` Jonas Mårtensson
2022-01-14 14:29                     ` Sebastian Moeller
2022-01-15 15:32                 ` Dave Taht
2022-01-14 19:21             ` Michael Richardson [this message]
2022-01-14 20:32               ` Joel Wirāmu Pauling

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=18327.1642188119@localhost \
    --to=mcr@sandelman.ca \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=martensson.jonas@gmail.com \
    --cc=moeller0@gmx.de \
    /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