From: Sebastian Moeller <moeller0@gmx.de>
To: Michael Richardson <mcr@sandelman.ca>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] CeroWRT and "FTTN" 50/10 VDSL2 (aka "FIBE")
Date: Mon, 30 Jun 2014 21:17:52 +0200 [thread overview]
Message-ID: <3FD2D434-D099-4251-BA38-A98A382EB067@gmx.de> (raw)
In-Reply-To: <26292.1404142678@sandelman.ca>
Hi Michael,
On Jun 30, 2014, at 17:37 , Michael Richardson <mcr@sandelman.ca> wrote:
>
> Sebastian Moeller <moeller0@gmx.de> wrote:
>>> Bell Canada and nortel ATM equipment is involved.
>
>> Oh, that would be quite interesting vdsl2 and atm at the same
>> time. Could you by chance post the status page of your vdsl modem (the
>> more detailed the statistics the better)? (Typically vdsl2 should use
>> packet transfer mode (PTM) instead of ATM between modem and DSLAM,
>> though the DSLAM might still connected to an ATM fabric. It would be
>> interesting to measure whether you still "see" the effects of ATM
>> encapsulation along your link.
>
> I can't say what the VDSL2 interface is, but the backhaul network with Bell
> has been historically all nortel passport ATM (with way over buffered LANE).
I would be amazed if they would manage to extend the reach of their ATM network while most other telco's seem to be moving away from ATM… Since bell advertises this as a fiber to the cabinet product, my bet is on ethernet over fiber from the slam/msan to the core network, but I digress. Not that it matters, only for the modem slam connection one needs to take ATM encapsulation into account for bandwidth shaping purposes. So what is your direct uplink to the slam using PTM or ATM?
Best Regards
Sebastian
>
> --
> ] 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-06-30 19:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 22:48 Michael Richardson
2014-06-27 19:37 ` Dave Taht
2014-06-27 20:15 ` Dave Taht
2014-06-30 15:35 ` Michael Richardson
2014-06-30 15:59 ` Dave Taht
2014-06-29 8:33 ` Baptiste Jonglez
2014-06-29 14:00 ` dpreed
2014-06-30 13:24 ` Michael Richardson
2014-06-30 13:55 ` Sebastian Moeller
2014-06-30 15:37 ` Michael Richardson
2014-06-30 19:17 ` Sebastian Moeller [this message]
2014-07-02 20:45 ` Michael Richardson
2014-07-03 9:39 ` Sebastian Moeller
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=3FD2D434-D099-4251-BA38-A98A382EB067@gmx.de \
--to=moeller0@gmx.de \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=mcr@sandelman.ca \
/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