From: "Joel Wirāmu Pauling" <joel@aenertia.net>
To: Michael Richardson <mcr@sandelman.ca>
Cc: Wes Felter <wmf@felter.org>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] 10GigE nics and SFP+ modules?
Date: Thu, 11 Sep 2014 09:54:33 +1200 [thread overview]
Message-ID: <CAKiAkGSZg289_PGFj59ed2so-3kPKe=wANs0VPPmUJCogqzaow@mail.gmail.com> (raw)
In-Reply-To: <11431.1410379395@sandelman.ca>
I have been heavily involved with the UFB (Ultrafast Broadband) PON
deployment here in New Zealand.
I am not sure how the regulated environment is playing out in Canada
(I am moving there in a month so I guess I will find out). But here
the GPON architecture is METH based and Layer2 only. Providers (RSP's)
are the ones responsible for asking for Handoffer buffer tweaks to the
LFC(local fibre companies; the layer 0-2 outfits-) which have mandated
targets for Latency (at most 4.5ms) accross their PON Access networks
to the Handover port.
Most of the time this has been to 'fix' Speedtest.net TCP based
results to report whatever Marketed service (100/30 For example) is in
everyones favourite site speedtest.net.
This has meant at least for the Chorus LFC regions where they use
Alcatel-Lucent 7450's as the handover/aggregation switches we have
deliberately introduced buffer bloat to please the RSP's - who
otherwise get whingy about customers whinging about speedtest not
showing 100/30mbit. Of course user education is 'too hard' .
-Joel
On 11 September 2014 08:03, Michael Richardson <mcr@sandelman.ca> wrote:
>
> >> I don't like when people create their cable plant to match what GPON
> >> needs. It's done because of the illusion that long-haul fiber is
> >> expensive. It isn't, if you have to dig anyway. The difference in cost
> >> of a 12 fiber cable, and a 1000 fiber cable, isn't huge compared to
> >> the digging costs. Splicing a 1000 fiber cable isn't huge
> >> either. Point-to-point fiber cabling is the way to go. If you then
> >> decide to light it up using PON of some kind, fine, that's up to you,
> >> at least you have the flexibility to change technology in the future.
>
> I went through a GPON install. It started as a PtP install.
> The problem is that while we were installing for 90% of the way, there were
> a number of places where we could not: conduits under highways, etc.
>
> In *Canada* at least, fiber construction is a regulated activity, and
> people who own fiber are required to lease to others who want it.
>
> So, the GPON because of the 10% of places where we had to lease fiber,
> and leasing 2-3 strands is much easier than 1000. In one case, my
> understanding was there was only a dozen strands installed, period, under,
> for instance, the Trans-Canada highway (quebec hwy 40/25 interchange was
> involved).
>
> I'm not otherwise very fond of the GPON stuff. The "terminals"
> are too smart, and not flexible enough, and yes, they had hidden bufferbloat.
>
> --
> ] Never tell me the odds! | ipv6 mesh networks [
> ] Michael Richardson, Sandelman Software Works | network architect [
> ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
>
>
>
next prev parent reply other threads:[~2014-09-10 21:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 18:05 Dave Taht
2014-09-10 18:09 ` Nicholas Weaver
2014-09-10 19:31 ` dpreed
2014-09-11 15:30 ` Dave Taht
2014-09-13 2:48 ` Chuck Anderson
2014-09-10 20:03 ` Michael Richardson
2014-09-10 21:54 ` Joel Wirāmu Pauling [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-09-06 18:36 Dave Taht
2014-09-06 19:05 ` dpreed
2014-09-06 20:44 ` Dave Taht
2014-09-09 0:09 ` Wes Felter
2014-09-09 4:03 ` Joel Wirāmu Pauling
2014-09-09 4:06 ` Joel Wirāmu Pauling
2014-09-09 16:26 ` dpreed
2014-09-09 16:54 ` Dave Taht
2014-09-10 7:01 ` Mikael Abrahamsson
2014-09-09 19:06 ` Wes Felter
2014-09-10 1:14 ` Dave Taht
2014-09-10 6:43 ` Mikael Abrahamsson
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='CAKiAkGSZg289_PGFj59ed2so-3kPKe=wANs0VPPmUJCogqzaow@mail.gmail.com' \
--to=joel@aenertia.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=mcr@sandelman.ca \
--cc=wmf@felter.org \
/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