From: richard <richard@pacdat.net>
To: "Dave Täht" <d@taht.net>
Cc: esr@thyrsus.com, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] First draft of complete "Bufferbloat And You" enclosed.
Date: Sat, 05 Feb 2011 18:50:45 -0800 [thread overview]
Message-ID: <1296960645.32487.54.camel@amd.pacdat.net> (raw)
In-Reply-To: <877hddhouj.fsf@cruithne.co.teklibre.org>
Back in 1996, shortly after iStar (Canada's first national ISP) bought
our Wimsey.COM regional, I got a chance to speak in front of a bunch of
people who were both customers and suppliers of the long distance
backbone (alternative) supplier that had spawned iStar.
As the lone internet speaker of the 3 keynotes, I talked about the
future, including things like $0.01/minute long distance using VOIP and
such.
Got my hand slapped hard right after and never got the opportunity to
speak for that company in public again. The company has gone bust.
Telus - the local ILEC here, has been using VOIP technology for their
long distance trunks for the past 10+ years - a leader in the technology
and the dominant in the field other than Bell here.
The next company my buddies and I formed did a bunch of stuff that
included ATM interface equipment and add/drop multiplexers, etc., all to
interface to IP.
Lately I have not heard much about ATM - seems to have pretty much
disappeared it seems :)
I lived this fight - from being told we could no longer use metered
phone lines for our modems, through being screwed over using Centrex
lines, US Robotics modems velcro'd on the wall, all of it.
I even started out climbing telephone poles and installing Strouger
(electro-mechanical) phone switches back in the late 60's - as the sig
on Slashdot says - "been there, done that..." :)
richard
On Sat, 2011-02-05 at 19:35 -0700, Dave Täht wrote:
> richard <richard@pacdat.net> writes:
>
> > If you believe the telcos, it was (and still should be) as that was the
> > way things like T1s and T3s and ATM all worked.
>
> http://www.wired.com/wired/archive/4.10/atm_pr.html
>
> On the self-similar nature of the internet debate, I'd like to see a
> paper on, until then, repeating this study sounds interesting:
>
> http://eeweb.poly.edu/el933/papers/Willinger.pdf
>
> The plots they have of traffic are rather different that what I've been
> seeing lately.
>
--
Richard C. Pitt Pacific Data Capture
rcpitt@pacdat.net 604-644-9265
http://digital-rag.com www.pacdat.net
PGP Fingerprint: FCEF 167D 151B 64C4 3333 57F0 4F18 AF98 9F59 DD73
next prev parent reply other threads:[~2011-02-06 2:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-05 13:23 Eric Raymond
2011-02-05 13:42 ` Jim Gettys
2011-02-05 15:12 ` Dave Täht
2011-02-05 15:46 ` Dave Täht
2011-02-06 13:37 ` Eric Raymond
2011-02-05 17:56 ` richard
2011-02-05 19:48 ` richard
2011-02-05 22:12 ` Dave Täht
2011-02-06 1:29 ` richard
2011-02-06 2:35 ` Dave Täht
2011-02-06 2:50 ` richard [this message]
2011-02-08 15:17 ` Justin McCann
2011-02-08 18:18 ` Eric Raymond
2011-02-08 18:31 ` richard
2011-02-08 18:50 ` Bill Sommerfeld
2011-02-09 15:50 ` Eric Raymond
2011-02-08 20:10 ` Sean Conner
2011-02-09 4:24 ` Justin McCann
2011-02-10 14:55 ` Jim Gettys
2011-02-10 17:50 ` Dave Täht
2011-02-08 19:43 ` Juliusz Chroboczek
2011-02-08 19:52 ` richard
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=1296960645.32487.54.camel@amd.pacdat.net \
--to=richard@pacdat.net \
--cc=bloat@lists.bufferbloat.net \
--cc=d@taht.net \
--cc=esr@thyrsus.com \
/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