HUNEYCUTT%GUNTER-ADAM@sri-unix.UUCP (01/22/84)
From: Doug <HUNEYCUTT@GUNTER-ADAM>
I'm looking for some general feedback, both from the university and
personal micro users and from government-oriented users.
I've been looking at the general networking environment for several
years now, most recently dealing closely with the government office
environment. We've been told by the Management that, at least for the
Air Force, TCP/IP is the only networking protocol that will be
allowed, acquired, and supported.
Actually, TCP/IP is probably a very fine protocol for the multi-path,
long- haul packet-switched system of ARPANet/DDN. However, at first
glance it seems a bit bulky for the local-area coax/fibre type
network. Can anyone tell me:
1) Do any LANs currently support TCP/IP (base or broadband)?
2) If a LAN supports TCP/IP, does any micro hooked to it (as a server,
not just a terminal) have to support the high-powered packages
like FTP, TN, MM, etc???
3) Does anybody realistically expect a 5MHz 8088 in a single-tasking
environment to handle this kind of comm?
It seems to me that LANs are just beginning to be offered with the
kind of support software that makes the idea attractive to the public.
The EtherNet (at least 3Com's implementation) is advertised to support
shared resource capability, mail, and other utilities that bring the
paperless office idea almost into grasp. Forcing the TCP/IP issue,
when the military is the only one using it, puts us even further
behind the general industry.
I'd appreciate any comments/suggestions/experiences/FLAMES/etc. I've
been seeing net addresses for a few years now that appear to originate
at a LAN site connected to an ARPANet host.....this may be a way
around the problem (TCP/IP on the gateway, whatever on the LAN). If
you'd like to reply, please include the word LAN in the subject
line; I'm on about 5 mailing lists and I like to sort out things on
subject. Sorry for the length, but confusion breeds wordiness.
Dougdarrelj@sdcrdcf.UUCP (01/23/84)
LAN and protocol are mostly independent issues, since the only thing
required is to define some encapsulation into the LAN transport.
Ethernet packets include a 16-bit protocol identifier, and there are
assigned codes for PUP, DOD IP, Xerox NS and probably others.
4.2 bsd specifically supports many TCP/IP services (SUN is especially
committed to this, it's how they connect their workstations together).
Symbolics (lisp machine mfg) also supports TCP/IP on their machines as well
as several large mainframes (VAX unix, VAX VMS, TOPS-20). The only real
complication in putting TCP/IP on Ethernet is adress translation: IP
addresses are 32 bit (with some internal structure) while Ethernet II
adresses are 48 bits (all but one bit have no special significance).
As far as which services must or should be implemented, the
definitive answers are in the RFC series documenting the protocols, but all
you "have to" implement are the IP transport layer (including honoring
certain supervisory messages such as "use gateway X to net Y") and
realistically TCP and UDP protocols. User and server functions need only be
implemented for services you use. 99% of needs can likely be met with
TELNET (virtual terminal), FTP (file transfer) and SMTP mail. A nominally
single-user workstation needs TELNET user, both FTP server and user, and
maybe SMTP (unless you do all mail on a large host you TELNET to).
--
Darrel J. Van Buer, PhD
System Development Corp.
2500 Colorado Ave
Santa Monica, CA 90406
(213)820-4111 x5449
...{allegra,burdvax,cbosgd,hplabs,ihnp4,sdccsu3,trw-unix}!sdcrdcf!darrelj
VANBUER@USC-ECL.ARPA