Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!rpi!uupsi!ccavax!tinkelman From: tinkelman@ccavax.camb.com Newsgroups: comp.protocols.tcp-ip Subject: Message-ID: <26331.26765648@ccavax.camb.com> Date: 13 Jun 90 19:05:43 GMT References: <12369@shlump.nac.dec.com> Organization: Cambridge Computer Associates, Inc. Lines: 30 In article <12369@shlump.nac.dec.com>, goldstein@carafe.enet.dec.com (Fred R. Goldstein) writes a bit about DECnet/OSI Phase V in response to a previous posting from John Franey (also of Digital) Franey> DEC has commited itself to OSI. All of its customers computer Franey> network nodes are going to be converted to OSI with the release of Franey> DECnet Phase V. I work for DEC but not in communications engineering Franey> but please don't think this is a plug. Goldstein> While I'm not a spokesman, I do work for DEC in communications Goldstein> engineering. We have certainly taken a leading role in OSI. But Goldstein> we are also building TCP/IP. And while Phase V is OSI up to Layer Goldstein> 3 it supports OSI and non-OSI in parallel using a "towers" approach. Goldstein> Most DEC-DEC applications won't use the OSI upper layers. Note that Goldstein> it's the upper layers of OSI that are most controversial. DEC is making a significant change in direction, or at least agreeing to the option of using a fairly length detour. DEC made a number of announcements at the New Orleans DECUS Symposium (early May) that indicated that TCP/IP will play a very strong role in Phase V. As a starter, _all_ of the DECnet Phase V routers will be multiprotocol routers, supporting DECnet Phase IV, OSI (DECnet Phase V) *and* IP. Given the Phase V architectural support for protocol towers in the DNS, I would expect (hope for?) support of towers based on a TCP/IP stack. Fred, is that what will happen? -- Bob Tinkelman, Cambridge Computer Associates, Inc., 212-425-5830 bob@camb.com or ...!{uupsi,uunet}!camb.com!bob