The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jsteve@superglobalmegacorp.com (Jason Stevens)
Subject: [TUHS] TUHS Digest, Vol 14, Issue 63
Date: Tue, 17 Jan 2017 19:43:11 +0800	[thread overview]
Message-ID: <A5761372-A00A-4FF5-B51E-E84AFF33E605@superglobalmegacorp.com> (raw)
In-Reply-To: <20170116164421.GJ6647@mcvoy.com>

Oh wow flashbacks to the joys of using ATM LANE over OC-3 as that 155Mb was "so superior" to 10 Mbit Ethernet and how "straightforward" it was getting pvp's from the phone company and setting up the LECS, BUS, LES, and each LEC.  And how all the consultants scoffed at PC's with 100mbit Ethernet as the old 33Mhz bus couldn't push 100mbit in their crazy minds of thinking all buses push data one byte at a time.  It was great once we started to get Cisco fast Etherchannel on the acquired catalyst switches so we could dump ATM at the core and even better to get those dance Intel NICs that could also FEC for super high bandwidth servers.  It's a shame it took a while to get metroE and ether WAN, but here we are in that awesome future devoid of the disaster of ATM as it couldn't even begin to scale at and beyond OC-128, 10 gig E put an end to all that nonsense.

There was a brief window I made some good money setting up ATM networks, but they all went from oc12 to at the end being over t1 bonds for rural areas.  Can't say I miss it.

On January 17, 2017 12:44:21 AM GMT+08:00, Larry McVoy <lm at mcvoy.com> wrote:
>On Mon, Jan 16, 2017 at 11:00:00AM -0500, Doug McIlroy wrote:
>> The highest levels of AT&T were happy to carry digital data, but
>> did not see digital as significant business. Even though digital T1
>> was the backbone of long-distance transmission, it was IBM, not
>> AT&T, that offered direct digital interfaces to T1 in the 60s.
>
>AT&T seemed pretty clueless about networking.  I gave a short talk at
>Hot
>Interconnects in the heyday of ATM.  Paul Borrill got me a speaking
>spot,
>I wasn't well known person but inside of Sun I had been railing against
>ATM and pushing for 100Mbit ethernet and Paul decided to see what the
>rest of the world thought.
>
>The gist of my talk was that ATM was a joke.  I had an ATM card (on
>loan
>from Sun Networking), I think it was 155 Mbit card.  I also had an 
>ethernet card that I had bought at Fry's on my way to the talk.
>The ATM card cost $4000.  The ethernet card cost $49 IIRC.
>
>The point I was making was that ATM was doomed.  This was at the time
>in
>history when every company was making long bets on ATM, they all
>thought
>it was the future; well, all meaning the execs had been convinced.
>
>I held up the two cards, disclosed the cost, and said "this ATM card is
>always going to be expensive but the ethernet card is gonna be $10 in
>a year or two.  Why?  Volume.  Every computer has ethernet, it's gonna
>do nothing but get cheaper.  And you're gonna see ethernet over fiber,
>long haul, you're going to see 100 Mbit, gigabit ethernet, and it's
>going to be cheap.  ATM is going nowhere."
>
>There was a shocked silence.  Weirdest talk ever, the room just went
>silent for what seemed forever.  Then someone, I'm sure it was an
>engineer
>who had been forced to work on ATM, started clapping.  Just one guy.
>And then the whole room joined in.
>
>I took the silence as "yeah, but my boss says I have to" and the
>clapping
>as "we agree".
>
>At the time AT&T was the biggest pusher of ATM.  Telephone switches
>were
>big and expensive and it was clear, to me at least, that AT&T looked at
>all those cheap ethernet switches and said "yeah, let's get the
>industry
>working on phone switching and we'll get cheap switches too".  Nice
>idea,
>didn't work out.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170117/8205a8ba/attachment-0001.html>


  parent reply	other threads:[~2017-01-17 11:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1484532001.2693.tuhs@minnie.tuhs.org>
2017-01-16 16:00 ` Doug McIlroy
2017-01-16 16:22   ` Marc Rochkind
2017-01-16 16:44   ` Larry McVoy
2017-01-16 16:52     ` Marc Rochkind
2017-01-16 19:17     ` Steve Johnson
2017-01-16 19:21       ` Larry McVoy
2017-01-16 19:57         ` Ken Thompson
2017-01-16 23:41     ` Tim Bradshaw
2017-01-16 23:45       ` Brantley Coile
2017-01-17  4:07       ` Jason Stevens
2017-01-17  5:22         ` William Corcoran
2017-01-17 11:43     ` Jason Stevens [this message]
2017-01-17 14:27     ` Joerg Schilling
2017-01-17 14:21   ` Joerg Schilling
2017-01-16 19:46 Noel Chiappa
2017-01-17  0:30 ` Brad Spencer
2017-01-17 15:32 Noel Chiappa
2017-01-18 14:29 ` Paul Ruizendaal

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=A5761372-A00A-4FF5-B51E-E84AFF33E605@superglobalmegacorp.com \
    --to=jsteve@superglobalmegacorp.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;
as well as URLs for NNTP newsgroup(s).