Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!ub!boulder!daemon
From: jnd@sms.com (Jose Nabielsky)
Newsgroups: comp.dcom.sys.cisco
Subject: Re: LAT-Telnet Translation over Ethernet Media
Message-ID: <25977@boulder.Colorado.EDU>
Date: 10 Sep 90 21:42:30 GMT
Sender: daemon@boulder.Colorado.EDU
Lines: 29


Bill,

>	1.      Will the CPT support Ethernet-Ethernet configurations?
>
>	Yes.  You can buy it with a single ethernet interface now (or, when 8.2
>	comes out, anyway.)  It isn't designed to have LAT and TCP on separate
>	ethernets - do you think that would be a useful addition?  It doesn't
>	seem like a common configuration for people to have their LAT network
>	completely distinct from their IP network.
>

The environment in question runs DECNet and TCP/IP over physically- and
administratively-separate ethernets.  (Although these ethernets are colocated
within the same building.) 

I *do not* intend to characterize other people's network environments,
but it seems peculiar that cisco sees *local* Ethernet-Ethernet translations
different from *remote* Ethernet-Serial translations.  That is, I propose a
CPT product whose translation functions are decoupled from the type and
number of network interfaces, allowing nE+mS configurations.

Let the customer vote with his dollars.

(If the customer needs Ethernet-Ethernet, the CSC-2E will do the trick;
if the customer needs Ethernet-Serial, today's CPT-standard CSC-1E1S will do.)

-Jose
(jnd@sms.com)