FW: Re: ATM comes and goes

tobe@meken.fuchu.toshiba.co.jp Fri, 10 May 1996 21:56 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa25824; 10 May 96 17:56 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa25820; 10 May 96 17:56 EDT
Received: from guelah.nexen.com by CNRI.Reston.VA.US id aa16608; 10 May 96 17:56 EDT
Received: from maelstrom.nexen.com (maelstrom.nexen.com [204.249.97.5]) by guelah.nexen.com (8.7.3/8.7.3) with ESMTP id RAA28041; Fri, 10 May 1996 17:48:48 -0400 (EDT)
Received: (from root@localhost) by maelstrom.nexen.com (8.7.3/8.7.3) id RAA03339 for ip-atm-out; Fri, 10 May 1996 17:39:16 -0400 (EDT)
Received: from guelah.nexen.com (guelah.nexen.com [204.249.96.19]) by maelstrom.nexen.com (8.7.3/8.7.3) with ESMTP id RAA03330 for <ip-atm@nexen.com>; Fri, 10 May 1996 17:39:13 -0400 (EDT)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: tobe@meken.fuchu.toshiba.co.jp
Received: from inet-tsb.toshiba.co.jp (inet-tsb.toshiba.co.jp [202.33.96.40]) by guelah.nexen.com (8.7.3/8.7.3) with SMTP id RAA27946 for <ip-atm@nexen.com>; Fri, 10 May 1996 17:39:09 -0400 (EDT)
Received: from tis2.tis.toshiba.co.jp by inet-tsb.toshiba.co.jp (8.6.12+2.5W/3.3W9-04/12/95) id GAA15293; Sat, 11 May 1996 06:39:04 +0900
Received: from ux37.fuchu.toshiba.co.jp (ux37) by tis2.tis.toshiba.co.jp (5.67+1.6W/6.4J.6-R05) id AA14734; Sat, 11 May 96 06:38:58 JST
Received: from as2233.meken.fuchu.toshiba.co.jp by ux37.fuchu.toshiba.co.jp (8.6.12+2.5W/3.3W9-TOSHIBA-TEMPLATE FOR MX) id GAA14743; Sat, 11 May 1996 06:26:24 +0900
Received: from as1003.meken.fuchu.toshiba.co.jp by as2233.meken.fuchu.toshiba.co.jp (4.1/6.4J.6-FCH-1.0) id AA03415; Sat, 11 May 96 06:41:57 JST
Received: from (pc1820) by as1003.meken.fuchu.toshiba.co.jp (4.1/6.4J.6-FCH-1.0) id AA09226; Sat, 11 May 96 06:40:30 JST
Date: Sat, 11 May 1996 06:40:30 -0000
Message-Id: <9605102140.AA09226@as1003.meken.fuchu.toshiba.co.jp>
To: matsui@sfc.wide.ad.jp
Cc: ip-atm@nexen.com
Mime-Version: 1.0
Subject: FW: Re: ATM comes and goes
Content-Type: text/plain; charset="iso-2022-jp"
X-Mailer: Winbiff [version 0.98A]
X-Orig-Sender: owner-ip-atm@nexen.com
Precedence: bulk
X-Info: Submissions to ip-atm@nexen.com
X-Info: [Un]Subscribe requests to majordomo@nexen.com
X-Info: Archives via http://cell-relay.indiana.edu/cell-relay/archives/IPATM/IPATM.html

松井さん

こんにちは。戸辺@東芝です。来週月曜日に徳田先生の教授就任のお祝いの会に
混ぜていただけることになりました。松井さんもいらっしゃいますか?

以下、ATM関連で、ご参考に。 当方、社内での業務激変で、全然 SFC へ行けなく
なってしまいましたが、機会を見つけて参りたいと思いますのでよろしくお願い
いたします。

------- Forwarded Message
X-POP3-Rcpt: tobe@as1003
X-Authentication-Warning: splash.isl.rdc.toshiba.co.jp: toshi set sender to 
owner-ip-atm@isl.rdc.toshiba.co.jp using -f
Message-Id: <199604301721.KAA24159@aland.bbn.com>
To: Hassan Naser <hnaser@comm.toronto.edu>
Cc: ip-atm@nexen.com
In-Reply-To: Your message of Tue, 30 Apr 96 12:11:08 -0400.
             <96Apr30.121113edt.33621@comsun.comm.toronto.edu> 
Date: Tue, 30 Apr 96 10:21:25 -0700
From: Craig Partridge <craig@aland.bbn.com>
Precedence: bulk
X-Info: Submissions to ip-atm@nexen.com
X-Info: [Un]Subscribe requests to majordomo@nexen.com
X-Info: Archives via http://cell-relay.indiana.edu/cell-relay/archives/IPATM/IPATM.html
X-Distribute: distribute [version 2.1 (Alpha) patchlevel=19]
Subject: Re: ATM comes and goes 
Errors-To: owner-ip-atm@isl.rdc.toshiba.co.jp
Sender: owner-ip-atm@isl.rdc.toshiba.co.jp

    I am quoting one of the speaker's note that "ATM comes and goes"!
    I wonder, if ATM is supposed to go why should (would) it come at all?
    Why no body (in the west coast) would think that it may happen to 
    take away FDDI, Ethernet, or.. in future. 

Without knowing who was speaking or more of what was said it is a bit hard
to comment on this question but here's at least a brief attempt to make
sense of it.

It has become very clear in the past few months (and the signs were there to
see for about a year) that ATM has lost the c. 100 Mb/s desktop market to Fast
Ethernet.  (See for example, the results of the purchasing survey in the
April '96 Data Communications, p. 18).

That means for the next few years, ATM's available markets are:

    * next generation LANs (e.g., what you install after 100 Mb/s which is
    presumably 1 Gb/s).  There should be competition within the next 18
    months or so from 1 Gb/s Ethernet.

    * LAN interconnection (what MAC technology do you use to connect those
    100 Mb/s LANs with, both within campus and wide area?).  Here there's
    competition from Frame Relay (I hear OC-3c speed Frame Relay is in
    the works), and from routers using PPP over SONET.

Another possible market is the LAN supporting video and data -- that's
murky since there's a version of Fast Ethernet that can also provide this
function.

>From the IETF's perspective, not much of this matters.  The rise of Fast
Ethernet simply confirms the Internet model continues to hold (so focus on
making IPv4 and IPv6 do what we want).  And the continued presence of ATM
in the backbone means we still need good ways to encapsulate IP over ATM.

Certain problems get easier if we assume ATM isn't a LAN protocol (e.g.,
multicast is less pressing as is, I suspect, NHRP).  But while ATM's importance
as a LAN is reduced, it is still there, so I wouldn't encourage us to take
this step.

Craig


------- End of Forwarded Message