From: "Henning P. Schmiedehausen" <hps@intermeta.de>
To: linux-kernel@vger.kernel.org
Subject: [DEFINITELY OFF-TOPIC] Re: ADSL vs Leased line
Date: Tue, 18 Feb 2003 09:01:08 +0000 (UTC) [thread overview]
Message-ID: <b2ssok$v2k$2@tangens.hometree.net> (raw)
In-Reply-To: 87adgu3ao4.fsf@deneb.enyo.de
Florian Weimer <fw@deneb.enyo.de> writes:
>John Bradford <john@grabjohn.com> writes:
>> A leased line is guaranteed bandwidth,
>Not at all. Welcome to the wonderful world of ATM Traffic Management.
That's the very point John was trying to make. A leased line in the
classic sense (E1/T1/ISDN) _is_ guranteed bandwith. You get 64k, 128k,
1920k, 1984k 2048k [1] guranteed, fixed bandwith synched with a master
clock.
And: bandwidth on a leased line != IP bandwidth. And with DSL lines
(which are either HDLC over copper (e.g. Lucent HST-DST) or simply
ATM-25 over copper (Cisco 14xx / Lucent Cellpipes) you can even get
both.
So your "wonderful world of ATM traffic management" is only correct
for some flavours of DSL lines.
Regards
Henning
Let's kill this thread. :-)
[1] 1920k = 1 slot for network management,
1 slot for connection management,
30 channels data
1984k = 1 slot for connection management,
31 channels data (G.704)
2048k = 32 channels data (G.703)
A least in Germany, a "2 MBit leased line" can come in any of
these flavours.
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
prev parent reply other threads:[~2003-02-18 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030216215008$5ac9@gated-at.bofh.it>
[not found] ` <20030216215008$0db5@gated-at.bofh.it>
2003-02-17 20:38 ` ADSL vs Leased line Florian Weimer
2003-02-18 9:01 ` Henning P. Schmiedehausen [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='b2ssok$v2k$2@tangens.hometree.net' \
--to=hps@intermeta.de \
--cc=linux-kernel@vger.kernel.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