From: Michael Richardson <mcr@sandelman.ca>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Wes Felter <wmf@felter.org>, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Ideas on how to simplify and popularize bufferbloat control for consideration.
Date: Sat, 02 Aug 2014 16:17:32 -0400 [thread overview]
Message-ID: <18188.1407010652@sandelman.ca> (raw)
In-Reply-To: <00AE9446-35B8-4A09-BA78-840DFC36F1DB@gmx.de>
Sebastian Moeller <moeller0@gmx.de> wrote:
>> Sebastian Moeller <moeller0@gmx.de> wrote:
>>> No idea? How would you test this (any command line to try). The good
>>> thingg with the ping is that often even the DSLAM responds keeping
>>> external sources (i.e. hops further away in the network) of
>>> variability out of the measurement...
>>
>> With various third-party-internet-access ("TPIA" in Canada), the DSLAM
>> is operated by the incumbent (monopoly) telco, and the layer-3 first
>> hop is connected via PPPoE-VLAN or PPP/L2TP.
> So they “own” the copper lines connecting each customer to the DSLAM?
> And everybody else just rents their DSL service and resells them? Do
> they really connect to the DSLAM or to the BRAS?
correct, the copper continues to be regulated; the incumbent was given a
guaranteed 11-14% profit on that service for the past 75 years...
Third parties get an NNI to the incumbent in a data centre.
1) for bridged ethernet DSL service ("HSA" in Bell Canada land), the
each customer shows up to the ISP in a VLAN tag.
2) for PPPoE DSL service, the traffic comes in a specific VLAN, over
IP (RFC1918) via L2TP.
Other parties can put copper in the ground, and in some parts of Canada, this
has occured. Also worth mentioning that
AlbertaGovernmentTelephone/EdmontonTel/BCTel became "TELUS", and then left
the Stentor/Bell-Canada alliance, so Bell can be the third party in the west,
while Telus is the third party in the centre, and Island/Aliant/NBTel/Sasktel
remain government owned... and they actually do different things as a result.
> I think in Germany the incumbent has to either rent out the copper
> lines to competitors (who can put their own lines cards in DSLAMs
> backed by their own back-bone) or rent “bit-stream” access that is the
> incumbent handles the DSL part on both ends and passes the traffic
> either in the next central office or at specific transit points. I
> always assumed competitors renting these services would get much better
> guarantees than end-customers, but it seems in Canada the incumbent has
> more found ways to evade efficient regulation.
This option exists, but the number of CLECs is large, and the move towards
VDSL2 / Fiber-To-The-Neighbourhood (with much shorter copper options!!) means
that this is impractical.
>> my incumbent telco's commercial LAN extension salesperson proudly told
>> me how they never drop packets, even when their links are congested!!!
> I really hope this is the opinion of a sales person and not the
> network operators who really operate the gear in the “field”. On the
> other hand having sufficient buffering in the DSLAM to never having to
> drop a packet sounds quite manly (and a terrible waste of otherwise
> fine DRAM chips) ;)
I think much of the buffer is the legacy Nortel Passport 15K that ties much
of the system together...
>> The Third Party ISP has a large incentive to deploy equipment that
>> supports whatever "bandwidth measurement" service we might cook up.
> As much as I would like to think otherwise, the only way to get a BMS
> in the field is if all national regulators require it by law (well
> maybe if ITU would bake it into the next xDSL standard that the DSLAM
> has to report current line speeds as per SNMP? back to all down stream
> devices asking for it). But I am not holding my breath…
My position is that if there isn't a technical specification, no regulation
could possibly follow...
--
] 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-08-02 20:17 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-24 14:03 R.
2014-07-25 18:37 ` Valdis.Kletnieks
2014-07-25 21:03 ` David Lang
2014-07-26 11:30 ` Sebastian Moeller
2014-07-26 20:39 ` David Lang
2014-07-26 21:25 ` Sebastian Moeller
2014-07-26 21:45 ` David Lang
2014-07-26 22:24 ` David Lang
2014-07-27 9:50 ` Sebastian Moeller
2014-07-26 22:39 ` Sebastian Moeller
2014-07-26 22:53 ` David Lang
2014-07-26 23:39 ` Sebastian Moeller
2014-07-27 0:49 ` David Lang
2014-07-27 11:17 ` Sebastian Moeller
2014-08-01 4:21 ` Michael Richardson
2014-08-01 18:28 ` Sebastian Moeller
2014-07-25 20:48 ` Wes Felter
2014-07-25 20:57 ` David Lang
2014-07-26 11:18 ` Sebastian Moeller
2014-07-26 20:21 ` David Lang
2014-07-26 20:54 ` Sebastian Moeller
2014-07-26 21:14 ` David Lang
2014-07-26 21:48 ` Sebastian Moeller
2014-07-26 22:23 ` David Lang
2014-07-26 23:08 ` Sebastian Moeller
2014-07-27 1:04 ` David Lang
2014-07-27 11:38 ` Sebastian Moeller
2014-08-01 4:51 ` Michael Richardson
2014-08-01 18:04 ` Sebastian Moeller
2014-08-02 20:17 ` Michael Richardson [this message]
2014-08-01 4:40 ` Michael Richardson
2014-07-26 11:01 ` Sebastian Moeller
-- strict thread matches above, loose matches on Subject: below --
2014-05-24 14:12 R.
2014-05-24 17:31 ` Sebastian Moeller
2014-05-24 19:05 ` David P. Reed
2014-05-20 22:11 Frits Riep
2014-05-20 23:14 ` Dave Taht
2014-05-21 11:42 ` Frits Riep
2014-05-21 14:51 ` dpreed
2014-05-21 15:19 ` Dave Taht
2014-05-21 16:03 ` dpreed
2014-05-21 16:30 ` Dave Taht
2014-05-21 17:55 ` dpreed
2014-05-21 17:47 ` Jim Gettys
2014-05-21 17:53 ` Dave Taht
2014-05-21 17:56 ` dpreed
2014-05-21 17:57 ` Jim Gettys
2014-05-21 18:31 ` Dave Taht
2014-05-21 15:07 ` Dave Taht
2014-05-21 16:50 ` Michael Richardson
2014-05-21 17:58 ` David Lang
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=18188.1407010652@sandelman.ca \
--to=mcr@sandelman.ca \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
--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