|
DataMuseum.dkPresents historical artifacts from the history of: DKUUG/EUUG Conference tapes |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about DKUUG/EUUG Conference tapes Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - downloadIndex: T
Length: 49572 (0xc1a4)
Types: TextFile
Names: »TCP«
└─⟦a0efdde77⟧ Bits:30001252 EUUGD11 Tape, 1987 Spring Conference Helsinki
└─⟦this⟧ »EUUGD11/euug-87hel/sec7/RFC/TCP«
NIC 50002
TCP/IP IMPLEMENTATIONS
AND
VENDORS GUIDE
January 1986
\f
TCP/IP IMPLEMENTATIONS
AND
VENDORS GUIDE
January 1986
Editors:
Ole Jacobsen
Francine Perillo
Anne Sauer
Additional copies of this document may be obtained from the DDN Network
Information Center, SRI International, 333 Ravenswood Avenue, Room
EJ291, Menlo Park, CA 94025.
\f
The TCP/IP Implementations and Vendors Guide was published by the DDN
Network Information Center, SRI International, Menlo Park, CA using the
Scribe document production system. Camera ready copy was produced with
an Imagen laser printer.
Scribe is a registered trademark of Unilogic, Ltd. Imagen is a
trademark of the Imagen Corporation.
Date: January 1986
ii
\f
ACKNOWLEDGEMENTS
The TCP/IP Implementations and Vendors Guide was prepared by the DDN
Network Information Center for the Defense Data Network Program
Management Office of the Defense Communications Agency under contract
number DCA-200-84-C-0024, CDRLs E009 and E009A. This Guide was compiled
with the assistance of many people, most of whom are the contacts for
products listed within this documen or product on the
part of the Defense Communications Agency (DCA), the Defense Advanced
Research Projects Agency (DARPA), the NIC or DoD. It is not complete.
Omission of any vendor or implementor has no significant implication,
other than that the NIC has no information about that vendor or
implementor, or that the information was not available at the time of
this printing. Likewise, only completed fields of the product templates
are included, and unfilled fields have been deleted to conserve space.
Anyone planning to use either a product or an implementation is urged to
do their own investigation of the details, costs, and support of the
product.
This guide is divided into software implementations (listed
alphabetically by machine type) and hardware implementations (listed
alphabetically by company). The guide is also indexed by operating
system, with the machine type listed under each and by company name.
Vendors who wish to have their TCP/IP products tested and
certified for use on the DDN should contact Code B617, the Test and
Evaluation Branch of the DDN PMO for details.
Throughout the document, references are made to RFCs and IENs.
RFCs, or Requests for Comments, are network technical notes used
primarily to introduce proposed internet protocols and related network
topics to the DDN. IENs, or Internet Experiment Notes, are Internet
Working Group technical notes. Both RFCs and IENs are available on the
SRI-NIC host. You may obtain copies of either by using the FTP
facility, if it is available at your host. Connect to the SRI-NIC host
[10.0.0.51 or 26.0.0.73] and log in as ANONYMOUS with GUEST as password.
RFC filenames are of the format RFC:RFCxxx.TXT (where xxx is the number
of the RFC) and IENs are of the format IEN:IEN-xxx.TXT (where xxx is the
number of the IEN -- note the dash in the IEN filename.)
Online copies of the guide are available through FTP in the file
named NETINFO:TCP-IP-IMPLEMENTATIONS.TXT. For those who are not on the
network, contact the DDN Network Information Center to request copies of
RFCs, IENs or this guide by calling our toll-free number 1-(800)
235-3155. Network users without FTP capability may send requests to
NIC@SRI-NIC.ARPA.
The NIC also welcomes your comments, additions and corrections.
The last page of this document contains a Feedback form for your
1
\f
convenience in sending us your comments.
Note: UNIX is a trademark of AT&T Information Systems; VAX,
TOPS-10 and TOPS-20 are trademarks of Digital Equipment Corporation.
Key to Symbols:
v Taken from vendor literature
[ ] Not yet available
Last edit: January, 1986
2
\f
1. TCP/IP SOFTWARE IMPLEMENTATIONS BY MACHINE TYPE
1.1. APPLE
1.1.1. Stanford Ethernet Appletalk Gateway
PRODUCT-OR-PACKAGE-NAME: STANFORD ETHERNET APPLETALK GATEWAY
(SEAGATE)
DESCRIPTION:
SEAGATE is a gateway that connects an Ethernet using the
internet protocols, to an applebus (AppleTalk) using Apple or IP
protocols. With such a gateway in place, it becomes possible to
create server daemons to provide file, printing, mail, etc.
services for Macintoshes.
This diout 8 chips) which
takes an afternoon to wirewrap.
- A UNIX (usually VAX) running 4.2 BSD, 4.1 BSD or Eunice.
This is because the source distributed is written in the
PCC/MIT 68000 C compiler. [This is the same compiler
included with the SUMACC Mac C cross development kit.]
You can probably substitute any 68K C compiler and
assembler, but it will be harder.
- Inside Mac, update service, and the Mac software
supplement.
- Applebus Developer's Kit, includes: protocol manual,
applebus taps and interconnecting cable, Mac applebus
drivers on SONY disks.
Software usable through the gateway includes:
- MAT (Mac / ATP transfer program). A simple file transfer
utility and daemon. Also serves as a skeleton application
for general Mac transaction services. For example you
3
\f
could easily build a Mac program to read and create
'internet mail' containing pictures and speech.
- EFS (external file system). Allows UNIX to act as a
general file server for the Macintosh. The Mac user sees
the standard 'desktop' iconic model of his remote
directory on UNIX. This software was written by John
Seamons of LucasFilm and adapted by us for AppleTalk.
- TELNET and TFTP. These correspond to the UNIX programs
used to access virtual terminal and file transfer
services. The Mac programs here were developed by MIT
(Romkey) / Dartmouth (Mark Sherman) and CMU (Tim Maroney).
This software has been released by Tim to net.sources.mac
(usenet) and is FTPable from CMU.
The released material for all of the above includes source
code and documentation. These files are currently publicly
accessable on-line via FTP to our SUMEX host, in the <info-mac>
directory. There are also tar magtapes available of SUMACC and
INFO-MAC (which contains the seagate files). Magtape info:
The tape duplication company below charges $65 to send each
tape. This includes the new reel of tape and surface (book
rate) postage. They will accept prepaid checks or money orders.
Call the number below for additional info about postage for
airmail or international mail.
Maria Code
Data Processing Services
Info-Mac TAR tape, and/or SUMACC TAR tape
1371 Sydney Drive
Sunnyvale, CA 94087
(408) 735-8006
DOCUMENTATION:
On [SUMEX]<info-mac> the files are:
seagate.ms documentation in -ms format
seagate.hard the wirelist for the applebus interface
seagate.shar1 the main gateway sources (including above docs)
seagate.shar2 the ddt, dlq, testscc, and tftp subdirectories
seagate-efs.shar the file service (client and server)
seagate-mat.shar the MAT service
All these files are plain ASCII and can be FTP'd from SUMEX
with the 'anonymous' login. The shar (shell archive) files are
large so we would appreciate it if you would avoid transfers
during 9 AM to 5 PM PST.
CPU:
4
\f
Apple Macintosh
O/S:
UNIX and others
IMPLEMENTATION-LANGUAGE:
C
CONTACT:
Bill Croft, (croft@sumex.arpa), SUMEX, Stanford University
PROPRIETY-STATUS:
Public domain (Copyrighted by can
be used by Macintosh programs written in Lisa Pascal to provide
access to implementations of IP, TCP and UDP protocols on
AppleTalk.
DOCUMENTATION:
Preliminary documentation is available as a technical report
from the Mathematics and Computer Science Department, Dartmouth
College, Hanover, NH 03755. A later (more complete and accurate)
document may be forthcoming from the University Computation
Center, Carnegie-Mellon University, Pittsburgh, PA 15213. (See
contacts below). Some documentation accompanies the sources.
CPU:
Apple Macintosh (TFTP: 128K; Telnet: 512K)
O/S:
Apple Macintosh
IMPLEMENTATION-LANGUAGE:
Lisa Pascal and 68000 Assembler
DISTRIBUTOR:
1) Usenet (net.sources.mac)
2) Mark Sherman (see below)
3) Tim Maroney (see below)
CONTACT:
1) Tim Maroney, Tim.Maroney@CMU-CS-K.ARPA
University Computation Center
Carnegie-Mellon University
Pittsburgh, PA 15213
2) Mark Sherman, mss%Dartmouth@CSNET-RELAY.ARPA
Dept. of Mathematics and Computer Science
6
\f
Dartmouth College
Hanover, NH 03755
ORDERING-PROCEDURE:
Under revision. Generally, Tim Maroney handles Usenet
postings, Mark Sherman handles individual requests. Currently,
send a request to Mark Sherman along with five blank
single-sided microdisks (3.5 Sony compatible). We will return
five disks with sources and programs (payment instead of disks
is acceptable. Current estimate is $5/disk.)
PROPRIETY-STATUS:
None.
INFORMATION-UPDATED:
November 1985
7
\f
1.2. BOLT BERANEK AND NEWMAN
1.2.1. BBN-C/70
PRODUCT-OR-PACKAGE-NAME: BBN-C/70
DESCRIPTION:
The C/70 processor is a BBN-designed system with a native
instruction set oriented toward executing the C language. It
supports UNIX Version 7 and provides for user processes with a
20-bit address space. The TCP/IP implementation for the C/70
was ported from the BBN VAX TCP/IP, and shares all of its
features. This version of TCP/IP is running experimentally at
BBN, but is still under development. Performance tuning is
underway, to make it more compatible with the C/70's memory
management system.
CPU:
C/70
O/S:
UNIX
IMPLEMENTATION-LANGUAGE:
C
CONTACT:
Dennis Rockwell, (drockwel@BBN-UNIX.ARPA), (617) 497-2643
8
\f
1.2.2. BBN-Gateways
DESCRIPTION:
In an effort to provide improved service in the gateways
maintained at BBN, a new gateway implementation written in
MACRO-11 instead of BCPL has been developed. The MACRO-11
gateway provides users with internet service that is
functionally equivalent to that provided by the current BCPL
gateways with the following exceptions:
- Packets with options will be fragmented if necessary.
- ICMP protocol is supported.
- The gateway sends Time Exceeded, Parameter Problem, Echo,
Information Request, Destination Unreachable, and Redirect
ICMP messages.
- Initially, Source Quench and Timestamp packets will not be
supported.
- Class A, B, and C Network Address formats as specified in
the Septe GATEWAY, NTARE-GATEWAY, UCL-GATEWAY, BBN-GATEWAY, SRI-C3PO,
DCEC-GATEWAY
9
\f
1.3. BURROUGHS
1.3.1. [B5000]
TYPE: DDN-contracted TCP/IP Implementation
DESCRIPTION:
This will be a package of software and technical support
services for interfacing Burroughs computing environments to the
Defense Data Network. The contract has not yet been awarded as
of this writing.
CPU:
B5000 family
DISTRIBUTOR:
Not yet determined
10
\f
1.3.2. [BURROUGHS/HYPERLINK]
PRODUCT-OR-PACKAGE-NAME: Hyperlink/DDN Software
DESCRIPTION:
Hyperlink/DDN is being implemented in accordance with the
ARPANET Upper Layer Protocols (presentation/application layers),
Transmission Control Protocol (session/transport layers), and
Internet Protocol (network layer functions for internetwork
communications). The software includes the host driver (either
with Ethernet or Hyperchannel connections), transmission control
protocol, internet protocol, network administrator and
application software. Applications include file transfer,
electronic mail and Telnet.
Hyperlink/DDN integrates ARPANET's packet switching protocol
standards with Internet Systems Corporation's proprietary
Ethernet-based hardware connection devices or with Network
Systems Corporation's HYPERchannel connection devices for
complete connections between LANs and/or long-haul networks. A
product option is available which provides an LSI 11/73 based
host front-end processor which will contain the TCP and IP
layers and an X.25 communications subsystem. Internet also
offers high speed local-area network solutions for non-DDN
requirements which can be integrated with DDN offerings.
DOCUMENTATION:
A full set of documentation is in process
CPU:
Burroughs
O/S:
Burroughs MCP
IMPLEMENTATION-LANGUAGE:
C or Pascal
DISTRIBUTOR:
Internet Systems Corporation
8360 West Oakland Park Blvd.
Sunrise, Florida 33321
CONTACT:
Mary Bloch
(305) 742-0301
11
\f
ORDERING-PROCEDURE:
See above contact
PROPRIETY-STATUS:
Product of Internet Systems Corporation
12
\f
1.4. CONTROL DATA CORPORATION
1.4.1. [CDC-CYBER]
DESCRIPTION:
This will be a package of software and technical support
services for interfacing Cyber computing environments to the
Defense Data Network. The expected date of completion is the
end of 1985.
CPU:
Cyber 170
O/S:
NOS
DISTRIBUTOR:
Control Data Corporation
13
\f
1.5. DATA-GENERAL
1.5.1. [DATA-GENERAL]
DESCRIPTION:
The TCP/IP product currently supports Ethernet under the
DG/UX operations system and will run under the AOS/VS operating
system in the future. Support for the DDN implementation is
forthcoming. Presently the product includes implementations of
FTP and Telnet protocols. TCP/IP tracks the UNIX 4.2 BSD
implementation.
DOCUMENTATION:
Contact Data General
CPU 9725 Datapoint Drive
MS - M95
San Antonio, TX 78284
CONTACT:
Bill Wimp, (512) 699-5242
15
\f
1.7. DIGITAL EQUIPMENT CORPORATION
1.7.1. BRL GATEWAY
PRODUCT-OR-PACKAGE-NAME: BRL Gateway
DESCRIPTION:
The BRL Gateway is a total redesign. None of the original
MIT code was used. The gateway runs as a set of tasks on a
simple multiprocessing operating system called LOS. Both LOS
and the gateway code as described here were entirely designed
and written by Ron Natalie.
This is an IP gateway with EGP support. The gateway will run
on most PDP-11 series processors, but is designed to be portable
to other machines that have C compilers. Point-to-point serial
links, DEC PCL-11/B, and the ACC LH-DH/11 interfaces are
currently supported. Work is in process to support the Interlan
Ethernet interfaces with the Address Resolution Protocol, the
Network Systems Corporations's HYPERchannel, and the Proteon
Ringnet hardware.
All gateway functions and features of the IP and ICMP
protocols are supported with the following exceptions. The ICMP
timestamp packet is not implemented and ICMP source quench
messages are ignored. IP timestamp and routing options are
supported. The Exterior Gateway Protocol is supported as
described in RFC904. Deviations from the specification are made
to optimize the performance as a stub system from the existing
core networks. The gateway also uses its own UDP based debug
and monitoring protocol. GGP echo packets are also answered.
In addition, the gateway provides Virtual-Host service. TCP
connections to be dynamically directed to an active host on the
BRLNET. This allows the host "BRL" to appear to always be up
for mail purposes.
The original BRL gateway was an early version of the MIT-C
gateway modified to know about class B and C addresses and to
work with the previously mentioned network interfaces. With the
advent of EGP, higher network traffic, and greater routing
intelligence, the modified MIT gateway became ineffective.
DOCUMENTATION:
Not yet
CPU:
Any PDP-11 processor that has memory management. The
16
\f
machines currently in use are a PDP-11/34 and LSI-11/23. A
console terminal interface and a clock are required, as well as
any network interfaces. The built-in line frequency clock on
the LSI-11 processors may be used in lieu of an additional
clock.
O/S:
LOS (the Little Operating System) is a small message-passing,
multitasking operating system written for the implementation of
the gateway, but is also being planned for use in real-time and
file server applications. The Gateway code runs in the hardware
user mode, while LOS itself runs in kernel mode. Interrupts are
serviced in real-time by the user code.
IMPLEMENTATION-LANGUAGE:
With the exception of small parts of the operating system and
some bit manipulation routines, which are written in assembler,
both LOS and the Gateway code are written in the C language.
DISTRIBUTOR:
U.S. Army Ballistic Research Laboratory
ATTN: AMXBR-SECAD/R. Natalie
APG, MD 21005-5066
CONTACT:
Ron Natalie, (RON@BRL.ARPA), (301) 278-6678 or above address
ORDERING-Psting, evaluation and experimentation with other
implementations. It currently runs in a sizable number of
PDP11s and LSI-11s with varying configurations and applications.
The system is designed to be used with the DCNET local network
and BOS/VOS operating system for a multi-media internet
workstation (so-called "fuzzball"), which operates using
emulation techniques to support ordinary RT-11 system and
application programs. However, the system has also been used on
other networks, including the DDN, and with other operating
systems, including RSX-11. An RSX-11 based version
incorporating only IP/TCP modules is presently used to support
the INTELPOST electronic-mail network.
The software system consists of a package of MACRO-11 and C
modules structured into levels corresponding to local-net, IP,
TCP and application levels, with user interfaces at each level.
The local-net level supports several communication devices,
including synchronous and asynchronous serial lines, 16-bit
parallel links and 1822 interfaces. Hosts using these devices
have been connected to DDN IMPs, Satellite IMPs, MACRO-11
Internet Gateways, SRI Port Expanders and to the DCNET local
network. When used on DCNET the system provides automatic
routing, time-synchronization and error-reporting functions.
The IP level conforms to the RFC791 specification, including
fragmentation, reassembly, extended addressing and options, but
currently does not interpret options. A full set of ICMP
features compatible with RFC792 is available, including
destination-unreachable, timestamp, redirect and source-quench
messages. Destination-unreachable and source-quench information
is conveyed to the user level via the TCP and raw-datagram
protocol modules. Internet gateway (routing and non-routing)
facilities compatible with RFC823 can be included on an optional
basis. This support can be configured to include hierarchically
structured gateways and subnets.
The TCP level conforms to the RFC793 specification, including
PUSH, URGENT and options. Its structure is based on circular
buffers for reassembly and retransmission, with repacketizing on
each retransmission. Retransmission timeouts are dynamically
determined using measured roundtrip delays, as adjusted for
backoff. Data flow into the network is controlled by measured
network bandwidth, as adjusted by source-quench information.
Features are included to avoid excessive segment fragmentation
and retransmission into zero windows. The user interface level
provides error and URGENT notification, as well as a means to
18
\f
set outgoing IP/TCP options.
A raw-datagram interface is available for non-TCP protocols
such as (RFC768). It includes internal congestion and fairness
controls, multiple-connection management and timestamping.
Protocols above UDP supported in the present system include Time
Server (IEN-142) and Name Server (IEN-116). Other raw-datagram
services include XNET (IEN-158), GGP Gateway (RFC823), along
with developmental versions of an EGP Gateway (RFC827) and a
DECnet Gateway. A number of user-level protocol modules above
TCP have been built and tested with other internet hosts,
including user/server Telnet (RFC764) user/server FTP (RFC765),
user/server SMTP (RFC788) and various other file-transfer,
debugging and control/monitoring protocols.
Code sizes and speeds depend greatly on the system
configuration and features selected. A typical 30K-word
LSI-11/2 single-user configuration with all features selected
and including the operating system, device drivers and all
buffers and control blocks, leaves about 16K words for
user-level application programs and protocol modules. A typical
124K-word LSI-11/23 configuration provides the same service to a
half-dozen individually relocated users. Disk-to-disk FTP
transfers across a DMA interprocessor link between LSI-11/23s
operate in the range 30-50 Kbps with 576-octet packets. The
124K-word PDP11/34 INTELPOST adaptation supports two 56-Kbps
lines and a number of lower-speed lines.
DOCUMENTATION:
Online help files distributed with system plus annotated
source code
CPU:
LSI-11 or PDP11 with disk, EIS and 28K or more words of
memory
O/S:
None (self-contained)
IMPLEMENTATION-LANGUAGE:
MACRO-11 and C
DISTRIBUTOR:
Linkabit Corporation
Eastern Operations
1517 Westbranch Drive
McLean, VA 22102
19
\f
CONTACT:
Dave Mills, (Mills@ISID.ARPA), (703) 734-8660
ORDERING-PROCEDURE:
Source and/or object modules on double-density DEC RX02
diskettes only. DARPA approval required and redistribution is
limited. Contact Dennis Perry (Perry@IPTO.ARPA) for approval
only; contact D. Mills (Mills@ISID.ARPA) for distribution.
PROPRIETY-STATUS:
DARPA
HOSTS:
DARPA Internet system: 8 (Linkabit), 10 (Ford Scientific
Research Labs), 1 (Ford Aerospace), 4 University of Maryland), 1
(Purdue), 1 (Norwegian Telecommunications Administration), 4
(DFVLR - Germany), 1 (University College London), 1 (Royal
Signals and Radar Establishment - UK); INTELPOST system: 13
worldwide
INFORMATION-UPDATED:
October 1985
20
\f
1.7.3. RSX-11M
DESCRIPTION:
This TCP/IP Implementation supports file transfer operations
between DEC RSX-11M, RSX-11M-PLUS and IAS operating systems.
Both user and server FTP are implemented. Full support is
included for Ethernet (DEUNA and DEQNA) as well as proNET ring
hardware interfaces. Process Software Corporation can modify
the software for other interfaces.
DOCUMENTATION:
Fully documented; supplied with User's Manual
CPU:
PDP-11 and LSI-11
O/S:
RSX-11M, RSX-11M-PLUS, IAS
IMPLEMENTATION-LANGUAGE:
Macro-11
DISTRIBUTOR:
Process Software Corporation
P. O. Box 746
35 Montague Road
Amherst, MA 01004
CONTACT:
Phil Denzer
(413) 549-6994
Telex 517891
ORDERING-PROCEDURE:
Contact Process Software Corporation
21
\f
1.7.4. UNIX 2.9 BSD
DESCRIPTION:
2.9 BSD TCP/IP is an adaptation of Berkeley's original VAX
TCP/IP (running under BSD 4.1 UNIX) which in turn is an offshoot
of BBN's VAX TCP/IP. 2.9 BSD TCP/IP runs on PDP-11/44s and
PDP-11/70s. The 2.8 version from SRI was adapted by Bill Croft
(formerly at SRI), then Tektronix adapted it for 2.9. Berkeley
took over modification of the software and brought it back to
SRI where Dan Chernikoff and Greg Satz adapted it for a later
release of 2.9. In addition to TCP/IP, UDP, ARP and the raw
packet interface is available. ICMP redirects are not supported.
User software implementations include Telnet and FTP, plus
Berkeley-developed local net protocols, RWHO, RSH, RLOGIN, and
RCP.
2.9 BSD with TCP/IP support could probably be made to run on
smaller PDP-11s although the address space would be very tight
and might present problems.
DOCUMENTATION:
Some documentation available; will be sent with tape request
CPU:
PDP-11/44, PDP-11/70
O/S:
2.9 UNIX
IMPLEMENTATION-LANGUAGE:
C (some system-dependent sections written in assembler)
CONTACT:
For technical information:
Carl Smith, (Carl@BERKELEY.ARPA)
(415) 644-1230
ORDERING-PROCEDURE:
For distribution, contact the PDP-11 Distribution office at:
Valerie Hanson
University of California
Berkeley, CA
415-642-6258
PROPRIETY-STATUS:
22
\f
Governed by stipulations of Berkeley BSD license
HOSTS:
SRI-TSC, SRI-PRMH
23
\f
1.7.5. GUELPH 2.9 BSD
PRODUCT-OR-PACKAGE-NAME: GUELPH 2.9BSD
DESCRIPTION:
This is a variation of the 2.9 BSD kernel that will run on
the entire range of PDP11's from 11/23 up. It uses a modified
kernel text segment scheme that does not require separate I/D
for the TCP/IP code. Various fixes have been applied so that
the kernel runs compatibly with UNIX 4.2 BSD on a 10Mbit/sec.
ethernet. For more information see 2.9 BSD.
DOCUMENTATION:
Same as for 2.9 BSD
CPU:
PDP-11/23 to PDP-11/70 including Professional 350 PC's
O/S:
2.9 BSD UNIX
IMPLEMENTATION LANGUAGE:
C plus some assembler
DISTRIBUTOR:
Rick Macklem,
Department of Computing and Information Science
University of Guelph
Guelph, Ontario Canada N1G 2W1
CONTACT:
Rick Macklem,
(519) 824-4120 x3284
rick%uogvax2.BITNET@wiscvm.ARPA
ORDERING PROCEDURE:
Send a tape and a 2.9 BSD source license to the above address
PROPRIETY STATUS:
2.9 BSD source licensees only (see 2.9 BSD)
INFORMATION-UPDATED:
October 1985
24
\f
1.7.6. Venix/11 TCP/IP
PRODUCT-OR-PACKAGE-NAME: Venix/11 TCP/IP
DESCRIPTION:
This is based on the "PDP-11/45" implementation available
from the MIT Laboratory for Computer Science. It has been
ported to a V7 UNIX system, in particular VenturCom's Venix/11
V2.0.
As little of the processing as possible takes place in the
kernel, to minimize the code space required. It fits
comfortably on I&D machines, but is almost hopeless on the
smaller machines. The kernel includes a proNET device driver,
IP fragment reassembly, IP header processing, local-net header
processing, and simple routing. The rest of the IP processing,
and all of the UDP and TCP functions, are in user libraries.
The psuedo-teletype driver is also in the kernel, and is used by
Server TELNET.
User programs handle ICMP processing; User and Server TELNET,
SMTP, TFTP, Finger, and Discard. There are User programs for
Nicname and Hostname. IEN-116 nameservers are used by all
programs, and an IEN-116 nameserver is also provided. The TCP
used is very simple, not very fast, and lies about windows. No
FTP is available, nor is one currently planned.
DOCUMENTATION:
There is a full set of manual pages, and some internals
documentation. The kernel code is well commented.
CPU:
PDP-11/44, 45, 70, 73, 84
O/S:
Venix/11 V2.0, should be simple to port to other V7 UNIX
systems.
IMPLEMENTATION LANGUAGE:
C
DISTRIBUTOR:
Proteon, Inc.
4 Tech Circle
Natick, MA 01760
CONTACT:
25
\f
John Shriver, jas@proteon.ARPA, (617) 655-3340
ORDERING-PROCEDURE:
Vendor product, available only in source form.
PROPRIETARY-STATUS:
Improvements are proprietary to Proteon.
26
\f
1.7.7. PDP-11/45
DESCRIPTION:
In the UNIX kernel we have modules to drive a "Pronet" device
(10 Mb/s token-passing ringnet), to transmit and receive
internet packets, to demultiplex incoming TCP and UDP packets,
to reassemble internet fragments, and to maintain a cache of
internet hosts and their best first hop gateways. Kernel code
and data use from 9k to 10.5k bytes depending on the size of the
receive packets buffer.
Outside the kernel we have: TCP, user and server Telnet,
SMTP, ICMP, and TFTP. All are running but are in varying stages
of development.
DOCUMENTATION:
Some documentation about the user/kernel interface and about
the kernel code
CPU:
PDP-11/45
O/S:
Version 6 UNIX
IMPLEMENTATION-LANGUAGE:
C
DISTRIBUTOR:
Laboratory for Computer Science
MIT
545 Technology Square
Cambridge, MA 02139
CONTACT:
Liza Martin, (martin@MIT-CSR.ARPA)
Larry Allen, (lwa@MIT-CSR.ARPA)
(617) 253-6011
ORDERING-PROCEDURE:
We are willing to give this software to anyone who wants it,
has a UNIX source license, and will agree to a few constraints.
We should point out that it would be difficult for someone who
is not a UNIX wizard to install this code. To find out more
about the software send mail to martin@MIT-CSR.ARPA or to
27
\f
lwa@MIT-CSR.ARPA.
PROPRIETY-STATUS:
Copyright MIT Laboratory for Computer Science
28
\f
1.7.8. v UNIQ-SYS5
PRODUCT-OR-PACKAGE-NAME: PASSAGE TCP/IP
DESCRIPTION:
PASSAGE TCP/IP is a complete implementation of TCP/IP that
allows a UNIX System V (5.2) to participate as a routing or
nonrouting (end) host over a wide spectrum of communication
systems ranging from hard-wired connections to packet-switched
or circuit-switched networks. It communicates with adjacent
hosts over synchronous communication lines, Ethernet, LANs, and
standard 1822 interface to an IMP. Features include TCP/IP,
ICMP, Telnet, FTP, UDP, and SMTP. Plans are to implement X.25
in the near future.
DOCUMENTATION:
Included in package
CPU:
DEC VAX (PDP-11 in the future)
O/S:
UNIX System V (5.2)
IMPLEMENTATION-LANGUAGE:
C
DISTRIBUTOR:
UNIQ Digital Technologies UNIQ Digital Technologies
28 S. Water St. 37 Wheaton Drive
Batavia, Ill 60510 Nashua, NH 03063
(312) 879-1008 (603) 883-4860
UNIQ Digital Technologies UNIQ Digital Technologies
8150 Leesburg Pike 2040 Avenue of the Stars
Suite 600 Suite 400
Vienna, VA 22180 Los Angeles, CA 90067
(703) 448-8508 (213) 277-6288
CONTACT:
Sales department (see above)
ORDERING-PROCEDURE:
Contact distributors
29
\f
PROPRIETY-STATUS:
PASSAGE is a product of UNIQ Digital Technologies
30
\f
1.7.9. PURDUE
DESCRIPTION:
The IP/X.25 effort is supported at Purdue by CSNET for
distribution to CSNET sites. It is based on the TCP/IP
implementation from BBN (for 4.1 BSD) or Berkeley (for 4.2 BSD).
A device driver was added which allows IP datagrams to be sent
over X.25 virtual circuits. An Interactive Systems INcard is
required.
DOCUMENTATION:
Complete manual available if CSNET subscriber
CPU:
VAX-11/750 and VAX-11/780
O/S:
UNIX 4.1 BSD and 4.2 BSD
IMPLEMENTATION-LANGUAGE:
C
DISTRIBUTOR:
CSNET CIC
Bolt Beranek and Newman Inc.
10 Moulton Street
Cambridge, MA 02238
(CIC@CSNET-SH.ARPA)
(617) 497-2777
CONTACT:
Tim Korb, (JTK@PURDUE.ARPA)
Computer Science Dept.
Math Bldg.
Purdue University
West Lafayette, IN 47909
(317) 494-6184
ORDERING-PROCEDURE:
Contact CIC (see above under DISTRIBUTOR)
PROPRIETY-STATUS:
For CSNET users only
31
\f
1.7.10. BBN-VAX-UNIX
PRODUCT-OR-PACKAGE-NAME: BBN-VAX-UNIX
DESCRIPTION:
BBN has developed an implementation of TCP/IP for DEC's
VAX(TM) family of processors, that runs under the Berkeley 4.1
BSD version of UNIX(TM). The development effort was funded by
DARPA. Some important features of the BBN VAX TCP/IP are that it
runs in the UNIX kernel for enhanced performance, it is a
complete implementation of the TCP and IP protocols, and
provides facilities for direct user access to the IP and
underlying network protocols. The IP module supports checksums,
option interpretation, fragmentation and reassembly, extended
internet address support, gateway communication with ICMP, and
support of multi-homing (multiple interfaces and addresses on
the same or different networks). The TCP supports checksums,
sequencing, the ability to pass options through to the IP level,
and advulton St.
Cambridge, MA 02238
(617) 497-3827
You will then receive a copy of the licensing agreement.
Tapes will be mailed upon receipt of a completed agreement and
the distribution fee.
This tape is supplied as-is to UNIX 4.1 BSD licensees, with
no warranties or support expressed or implied. BBN would be
pleased to arrange separate agreements for providing
installation assistance and/or software support services, if
desired.
PROPRIETY-STATUS:
Requires a 4.1 BSD license from U.C. Berkeley
HOSTS:
BBN-VAX (development site)
33
\f
1.7.11. BERKELEY-VAX-UNIX-4.2
PRODUCT-OR-PACKAGE-NAME: BERKELEY-VAX-UNIX-4.2
DESCRIPTION:
This implementation was developed by the Computer Research
Group of the University of California at Berkeley as part of a
number of research projects. It is based on the BBN
implementation for the VAX. It provides support for TCP, IP,
ICMP, and UDP with user and server programs for Telnet, FTP,
TFTP and SMTP. Hardware supported includes ACC and DEC/CSS Imp
Interfaces, 10M bit/s and 3M bit/s Ethernet, and Proteon PRONET.
DOCUMENTATION:
Online documentation of user programs, system call
interfaces, etc.; "4.2 BSD Networking Implementation Notes",
CSRG TR/6
CPU:
VAX-11/780, 11/750, 11/730
O/S:
UNIX 4.2 BSD
IMPLEMENTATION-LANGUAGE:
C
DISTRIBUTOR:
Computer Systems Research Group
Computer Science Division
University of California
Berkeley, CA 94720
CONTACT:
Pauline Schwartz, (Pauline@BERKELEY.ARPA)
Distribution Coordinator
(415) 642-7780
ORDERING-PROCEDURE:
Contact Distribution Coordinator
PROPRIETY-STATUS:
Requires a 4.2 BSD license agreement and Western Electric
UNIX/32V, System III, or System V UNIX license.
34
\f
The licensing procedure smission Control Protocol (session/transport layers), and
Internet Protocol (network layer functions for internetwork
communications). The software includes the host driver (either
with Ethernet or Hyperchannel connections), transmission control
protocol, internet protocol, network administrator and
application software. Applications include file transfer,
electronic mail and Telnet.
Hyperlink/DDN integrates ARPANET's packet switching protocol
standards with Internet Systems Corporation's proprietary
Ethernet-based hardware connection devices or with Network
Systems Corporation's HYPERchannel connection devices for
complete connections between LANs and/or long-haul networks. A
product option is available which provides an LSI 11/73 based
host front-end processor which will contain the TCP and IP
layers and an X.25 communications subsystem. Internet also
offers high speed local-area network solutions for non-DDN
requirements which can be integrated with DDN offerings.
DOCUMENTATION:
A full set of documentation is in process
CPU:
DEC/VAX
O/S:
VMS
IMPLEMENTATION-LANGUAGE:
C or Pascal
DISTRIBUTOR:
Internet Systems Corporation
8360 West Oakland Park Blvd.
Sunrise, Florida 33321
CONTACT:
Mary Bloch
(305) 742-0301
36
\f
ORDERING-PROCEDURE:
See above contact
PROPRIETY-STATUS:
Product of Internet Systems Corporation
37
\f
1.7.13. TEKTRONIX-VAX
PRODUCT-OR-PACKAGE-NAME: VAX/VMS
DESCRIPTION:
This implementation runs under VAX 780/VMS. It has a
hyperchannel interface with a home-grown VMS driver. TCP/IP
from 3COM interoperates with VMS TCP/IP over HYPERchannel. They
have added TCP and IP options to UNET. Currently, there is no
plan to market TCP/IP software, although it is available to the
network research community for internal use only. Support has
been added for Ethernet using an Interlan driver.
- TCP: Has no security or precedence.
- IP: No datagram reassembly or fragmentation. Neither
Internet control protocol nor gateway protocol have been
implemented. There are no plans to implement
fragmentation.
- FTP: Not compatible with UNIX 4.2 BSD but compatible
with 3COM's implementation of FTP. There are plans,
however, to make it compatible with UNIX 4.2 BSD.
DOCUMENTATION:
Source is well-commented
CPU:
VAX/780,750 and any DEC machine running VMS (including
micros)
O/S:
UNIX for UNET, VMS for homegrown TCP/IP
IMPLEMENTATION-LANGUAGE:
BLISS (an equivalent of C) and some MACRO
DISTRIBUTOR:
TEKTRONIX
PO Box 500
Stop 50/454
Beaverton, OR 97077
CONTACT:
Jeff Mulick (jeffm%tektronix@CSNET-RELAY.ARPA)
(503) 627-5007
38
\f
ORDERING-PROCEDURE:
Contact Jeff Mulick
PROPRIETY-STATUS:
Not available for OEM resale
39
\f
1.7.14. WOLLONGONG MICROVAX
PRODUCT-OR-PACKAGE-NAME: WIN/MVX
DESCRIPTION:
This TCP/IP implementation includes Telnet (remote login),
FTP (file transfer), SMTP (Mail) Netstat, Finger, TFTP. Supports
the following network interface: DEC DEUNA Ethernet Controller.
DOCUMENTATION:
Installation Guide and Users Manual available
CPU:
DEC MicroVAX I and II
O/S:
Micro VMS 4.0 or greater
IMPLEMENTATION LANGUAGE:
C
DISTRIBUTOR:
The Wollongong Group
1129 San Antonio Road
Palo Alto, CA 94303
CONTACT:
Wollongong Sales
(415) 962-7200
ORDERING PROCEDURE:
Available with support from The Wollongong Group
PROPRIETY STATUS:
Wollongong
40
\f
1.7.15. WOLLONGONG VAX-VMS
PRODUCT-OR-PACKAGE-NAME: WIN/VX
DESCRIPTION:
This TCP/IP implementation includes Telnet (remote login),
FTP (file transfer), SMTP (Mail) Netstat, Finger, TFTP.
Supports the following network interfaces:
- ACC LH-DH (1822 interface)
- ACC HDH (1822-J) (For WIN/VX (DDN))
- ACC X.25 (For WIN/VX (DDN))
- Interlan Ethernet Controller
- DEC Deuna Ethernet Controller
- Ungermann-Bass
- DEC DMR-11
DOCUMENTATION:
Installation Guide and Users Manual available
CPU:
DEC VAX
O/S:
VMS 3.1 or greater and VMS 4.x
IMPLEMENTATION LANGUAGE:
C
DISTRIBUTOR:
The Wollongong Group
1129 San Antonio Road
Palo Alto, CA 94303
CONTACT:
Wollongong Sales
(415) 962-7200
ORDERING PROCEDURE:
41
\f
Available with support from The Wollongong Group
PROPRIETY STATUS:
Wollongong
42
\f
1.7.16. SOFTSEL-VMS
PRODUCT-OR-PACKAGE-NAME: SOFTSEL-VMS
DESCRIPTION:
Software implementation of File Transfer Protocol (FTP),
Network Virtual Terminal Protocol (TELNET) and Simple Mail
Transfer Protocol (SMTP). Runs on top of TCP/IP or NETEX (using
a separate TCP Emulator).
DOCUMENTATION:
On-line VAX/VMS HELP and installation instructions are
provided.
CPU:
VAX family
O/S:
VMS (Versions 4.0 and higher)
IMPLEMENTATION-LANGUAGE:
C
DISTRIBUTOR:
Softsel Incorporated
601 Ewing Street
Princeton, NJ 08540
(601) 683-1150
ORDERING-PROCEDURE:
Contact SCP Product Manager at Softsel Incorporated
PROPRIETY-STATUS:
Proprietary product of Softsel Incorporated (NETEX is a
trademark of Network Systems Corporation)
INFORMATION-UPDATED:
December 1985
43
\f
1.7.17. SOFTSEL-GATEWAY
PRODUCT-OR-PACKAGE-NAME: SOFTSEL-GATEWAY
DESCRIPTION:
Software implementation of translating gateway that allows
the connection of NETEX based networks (such as HYPERchannel,
HYPERbus and DATApipe) to TCP/IP based networks. Runs in an
enviroment with both TCP/IP and NETEX.
DOCUMENTATION:
On-line VAX/VMS HELP and installation instructions are
provided for the VMS implementation and UNIX man pages for the
UNIX implementation.
CPU:
VAX family
O/S:
VMS (Versions 4.0 and higher) UNIX 4.2 BSD
IMPLEMENTATION-LANGUAGE:
C
DISTRIBUTOR:
Softsel Incorporated
601 Ewing Street
Princeton, NJ 08540
(601) 683-1150
ORDERING-PROCEDURE:
Contact SCP Product Manager at Softsel Incorporated
PROPRIETY-STATUS:
Proprietary product of Softsel Incorporated (NETEX,
HYPERchannel, HYPERbus and DATApipe are trademarks of Network
Systems Corporation)
INFORMATION-UPDATED:
December 1985
44
\f
1.7.18. WOLLONGONG-SYSTEM-V-UNIX
PRODUCT-OR-PACKAGE-NAME: WIN/SVX
DESCRIPTION:
This TCP/IP implementation includes Telnet Available with support from The Wollongong Group
PROPRIETY STATUS:
Wollongong
45
\f
1.7.19. SRI-TENEX/FOONEX/AUGUST
DESCRIPTION:
SRI has implemented TCP/IP for the TENEX (FOONEX and AUGUST)
operating system running on DEC-10 KA or KI and F2, F3 or F4
Foonly processors. It was adapted from the BBN and ISI versions
of TENEX TCP/IP, with contributions from Ed Taft of Xerox and
Phil French of Tymshare, and resides in the operating system.
It is largely upward-compatible with TOPS-20 implementations and
fully compatible with AUGMENT. Telnet, FTP, SMTP, ICMP, ECHO,
TIME, WHOIS, and NAME service are available although some are
still under development.
This is an implementation done at BBN. DARPA has dropped
funding for continued support for Tenex development, and thus
the latest versions done for BBN and DEC for TOPS-20 are not
available for Tenex.
DOCUMENTATION:
None available at this time other than that embedded in the
programs
CPU:
DEC-10(KA, KI) F2,F3,F4
O/S:
TENEX-134,135/FOONEX/AUGUST
IMPLEMENTATION-LANGUAGE:
MACRO
DISTRIBUTOR:
SRI International
Network Information Center
Room EJ286
333 Ravenswood Ave.
Menlo Park, CA 94025
CONTACT:
Vivian Neou, (VIVIAN@SRI-NIC.ARPA), (415) 859-4781
ORDERING-PROCEDURE:
Contact Vivian Neou
PROPRIETY-STATUS:
46
\f
DCA-owned software
INFORMATION-UPDATED:
January 1986
47
\f
1.7.20. LLL-TOPS-10
DESCRIPTION:
A TOPS-10 implementation was begun by Don Provan while at
WPAFB-AFWAL and was completed by him at LLL-MFE. There have
been no serious problems since April of 1983. System supports
IP/ICMP and TCP. User level software available for FTP and
Telnet connections.
DOCUMENTATION:
Scarce: existing code (both system code and user level code)
is the only reliable source of information; user level code
maintained by nedved@CMU-CS-A.ARPA
CPU:
PDP-10 or PDP-10 look alikes
O/S:
TOPS-10 (also runs under WAITS at SU-AI)
IMPLEMENTATION-LANGUAGE:
MACRO-10
DISTRIBUTOR:
Don Provan
Lawrence Livermore Laboratory
MFE Computer Center
P.O. Box 5509
Livermore, CA 94550
CONTACT:
Don Provan, (provan@LLL-MFE.ARPA), (415) 422-4474
ORDERING-PROCEDURE:
All files are in [70,71,monitor]@LLL-MFE, available via FTP.
Also available on 9-track tape
HOSTS:
LLL-MFE running TOPS-10 7.01a on a KL-10, WPAFB-AFWAL running
TOPS-10 7.01 on a KL-10, CMU-CS-A running TOPS-10 6.02a on a
KL-10, SU-AI running WAITS on a PDP-10 look-alike, WHARTON
running TOPS-10 7.01a on a KL-10
48
\f
1.7.21. MIT-ITS-10/20
DESCRIPTION:
This is a TCP/IP implementation that runs under the MIT
Incompatible Timesharing System (ITS) on DEC-10/20 machines (KA
or KL), written by Ken Harrenstien of SRI International under
contract to MIT. Includes Telnet, FTP and SMTP. Bug reports
and interest group is BUG-TCP@MIT-MC.ARPA.
DOCUMENTATION:
Available from contact
CPU:
DEC-10/20 (KA and KL)
O/S:
ITS
IMPLEMENTATION-LANGUAGE:
MIDAS( supports multiple
networks, multiple interfaces on a single network, and multiple
protoco
-------