Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!hplabs!hpda!hpcuhb!hp-ses!wunder
From: wunder@hp-ses.SDE.HP.COM (Walter Underwood)
Newsgroups: comp.sys.hp
Subject: Re: HP/3000 TCP/IP - is it standard?
Message-ID: <920017@hp-ses.SDE.HP.COM>
Date: 4 Feb 89 00:07:31 GMT
References: <1078@pyrltd.UUCP>
Organization: HP SW Engineering Systems - Palo Alto, CA
Lines: 33

Well, I hate to disagree with Don, since he is from a networking
division, but ...

   The 3000 has a real TCP/IP implementation.

Correct, but it does not have UDP and thus does not support domain
name service.

   However, the only networking and network services currently running
   on 3000s in the field is the HP-proprietary NS (HP Network Services).
   No ARPA/Berkeley services exist yet; ...

ARPA services are available for MPE (the "classic" 3000) from The
Wollongong Group.  ARPA services are not available for MPE/XL
(Precision Architecture).  I don't think that the Berkeley services
(rlogin, rcp, rsh, lp) are available from anywhere, but they are
pretty Unix-specific anyway.

   ... only IEEE 802.2/.3 link level transport is supported (no
   Ethernet); and all IP-to-physical address resolution is done by HP's
   proprietary Probe protocol.

MPE release V-Delta-5 supports Ethernet and ARP.  Configure it with
NMMGR, of course.  Ether support is promised for MPE/XL, but the exact
release has not been announced.

Also, if you login to MPE, then telnet out to a Unix machine, the
character mode performance (for vi or Emacs, say) will be miserable.
MPE talks to the terminal in half-duplex, so telnet has to turn the
line around for every character!

Walter Underwood
HP Software Engineering Systems (not a networking division)