From: Jan Ceuleers <jan.ceuleers@gmail.com>
To: Benjamin Cronce <bcronce@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] 22 seconds til bloat on gfiber?
Date: Wed, 26 Oct 2016 16:49:52 +0200 [thread overview]
Message-ID: <77a4abf0-bc94-0d2e-eebe-d72e2e676255@gmail.com> (raw)
In-Reply-To: <CAJ_ENFHmSX-YhOWKQEa9RFiLkUfeCOMjqnDR310eqbHXhRewVA@mail.gmail.com>
On 26/10/16 03:05, Benjamin Cronce wrote:
> Sorry to side track
>
> 1:1 split bandwidth wise, still a 1:16 or whatever fiber split. Each
> port can handle 40Gb/s, which is 32 lambdas of 1.25Gb/s, each customer
> getting their own lambda. The ONT can either be WDM-PON or GPON with an
> inline filter. A Google Fiber engineer actually had this in his blog a
> long while back, talking about their design and the "dedicated" aspect
> of an unshared GPON. PON can only handle about a 32 split before the
> signal strength gets too low toe be practical. If each group of
> customers shared a lambda, they would need too many split or repeaters,
> which is more impractical.
I am aware of GPON deployments with splitting factors of 64 and higher,
and these do not (at all) pose a problem with the optical power budget.
> I'm not entirely sure which part you mean "impractical".
What I mean is that the OLT optics become very expensive if you need to
support as many lambdas as you have customers. You'd furthermore need an
OLT port for much fewer customers (e.g. 1 port per 64 or 128 customers)
than the thousands you can support on a (shared) GPON port on a single
lambda.
Also on the ONT side there is the danger of spiraling cost in that I
don't think it is economically feasible yet to incorporate tunable
lasers in the CPE, certainly not across 64 or 128 lambdas, meaning that
you'd need as many hardware variants of the ONT as you have lambdas.
But maybe I'm wrong.
next prev parent reply other threads:[~2016-10-26 14:49 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 21:56 Dave Taht
2016-10-22 23:52 ` Jonathan Morton
2016-10-23 1:33 ` jb
2016-10-23 1:45 ` Dave Taht
2016-10-23 1:47 ` Dave Taht
2016-10-23 2:27 ` jb
[not found] ` <CAJq5cE3DsV9v6ATVeq+vF_kVFjKy+8Qjwe-P01ZZbyKZB9HC6w@mail.gmail.com>
2016-10-23 8:29 ` Jonathan Morton
2016-10-23 9:23 ` jb
2016-10-23 16:14 ` Klatsky, Carl
2016-10-24 0:46 ` jb
2016-10-24 13:13 ` Klatsky, Carl
2016-10-24 16:11 ` Noah Causin
2016-10-24 20:27 ` Klatsky, Carl
2016-10-23 2:30 ` Benjamin Cronce
2016-10-25 7:10 ` Jonas Mårtensson
2016-10-23 5:50 ` Mikael Abrahamsson
2016-10-24 16:57 ` Jonas Mårtensson
2016-10-24 22:10 ` Benjamin Cronce
2016-10-25 0:09 ` jb
2016-10-25 12:01 ` Benjamin Cronce
2016-10-25 13:11 ` Klatsky, Carl
2016-10-25 21:20 ` jb
2016-10-26 0:02 ` Klatsky, Carl
2016-10-25 15:59 ` Jan Ceuleers
2016-10-26 1:05 ` Benjamin Cronce
2016-10-26 14:49 ` Jan Ceuleers [this message]
2016-10-26 15:36 ` Mikael Abrahamsson
2016-10-27 14:32 ` Jonas Mårtensson
2016-10-27 16:56 ` Dave Taht
2016-10-27 17:56 ` [Bloat] Sidebar on s-curves David Collier-Brown
2016-10-27 19:30 ` [Bloat] 22 seconds til bloat on gfiber? David Lang
2016-10-27 19:41 ` Dave Taht
2016-10-27 19:48 ` Aaron Wood
2016-10-28 15:51 ` Jan Ceuleers
2016-10-28 15:55 ` Klatsky, Carl
2016-10-27 19:45 ` Aaron Wood
2016-10-27 20:17 ` Mikael Abrahamsson
2016-12-07 5:40 ` Jonathan Morton
2016-12-07 7:05 ` Mikael Abrahamsson
[not found] <mailman.313.1477591111.3555.bloat@lists.bufferbloat.net>
2016-10-27 19:27 ` Jonathan Foulkes
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=77a4abf0-bc94-0d2e-eebe-d72e2e676255@gmail.com \
--to=jan.ceuleers@gmail.com \
--cc=bcronce@gmail.com \
--cc=bloat@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