NCSA Telnet/TUBA 2.0 now available

colella@nist.gov Tue, 22 June 1993 20:09 UTC

Date: Tue, 22 Jun 1993 16:07:34 -0400
Organization: National Institute of Standards and Technology (NIST)
Sub-Organization: Computer Systems Laboratory (CSL)
Message-Id: <9306222007.AA20392@emu.ncsl.nist.gov>
To: tuba@lanl.gov, noop@merit.edu, wg-llt-clns@rare.nl
Subject: NCSA Telnet/TUBA 2.0 now available
Cc: colella@nist.gov
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: colella@nist.gov
Reply-To: colella@nist.gov

My apologies for the multiple copies....

Also, Alex Reijnierse suggested I put this up for ftp on
nic.switch.ch:./incoming/clns, so I have.  It would be nice
to have a few test sites before the IETF :^).

--Richard


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


   Release notes for NCSA Telnet 2.3.05 (TUBA 2.0)
   -----------------------------------------------


This distribution is a modified version of NCSA Telnet, version
2.3.05.  It incorporates a prototype of TUBA (TCP and UDP with Bigger
Addresses -- see RFC 1347).



Obtaining the Distribution
--------------------------
The distribution is available on osi.ncsl.nist.gov
(129.6.48.100) via anonymous ftp.  Retrieve the files:

   ./pub/ncsa_tuba/tuba2-0.exe.zip	-- executables only
   ./pub/ncsa_tuba/tuba2-0.src.zip	-- sources and executables

If there are problems unzipping the file, retrieve the DOS
executable, dos_pkunzip.exe, from the same directory.

osi.ncsl.nist.gov supports "anonymous" FTAM as well:

   Paddr  = {1,1,1,47:0005:80:005A00:0000:0001:E137:080020079EFC:00}
   userid = anon, no password, realstore = unix

The corresponding "ISODE isoentities" entry is:

   osi.ncsl.nist.gov   filestore NULL \
           #1/#1/#1/NS+47000580005a0000000001e137080020079efc00



Differences Between TUBA 1.0 and TUBA 2.0
-----------------------------------------
Two major features have been added for TUBA 2.0:

	- Full ftp/TUBA support: In addition to ftp over TCP/IP,
	  this release supports ftp over TUBA (i.e., over TCP/CLNP)
	  in both initiator and responder modes.  As in the non-TUBA
	  NCSA distribution, the responder is integral to telbin.exe,
	  and so is operational whenever telbin.exe is running.  The
	  initiator is a stand-alone executable, ftpbin.exe.

	  ftp operates over TUBA using the LPORT ftp command (see the
	  I-D draft-ftp-bigports-02.txt).

	- DNS access for NSAPs: Absent an entry in the local
	  configuration file for a given host, the programs in the
	  distribution will query the DNS for NSAPs (in addition to IP
	  addresses) according to I-D draft-manning-dns-nsap-02.txt.
	  When both are present either in the local configuration file
	  or in the DNS, preference is given to use of TUBA.

A new option has been added to clnping, '-z', which permits pinging
of CLNP-capable Suns that have been patched for long-term ping.
These Suns still require that a destination NSel of 0x1e be used in
the ping packets.  (Note: unpatched Suns don't support the long-term
ping at all).



Programs in the Distribution
----------------------------
The following executables are compiled and ready to go:

    telbin.exe - The basic NCSA Telnet program.  Includes
	 an ftp responder that supports operation over TUBA
         using the LPORT command.

    finger.exe - The finger initiator

    clnping.exe - A clnp version of ping (the "new" kind as
         described in I-D draft-ietf-noop-echo-01.txt).

    ftpbin.exe - Ftp initiator, including support for operation
         over TUBA using the LPORT command.

In addition to the precompiled executables, the source version of the
distribution also contains the source code.  The tools used to create
the binaries are:

    Microsoft C Compiler, Version 5.1
    Microsoft ASM (MASM), Version 5.1

The file 'build.bat' executes 'make' on the four makefiles
for the telbin, finger, clnping, and ftpbin executables.



Configuration Information
-------------------------
For information on how to configure NCSA Telnet in general,
ftp to ftp.ncsa.uiuc.edu and look in the ./PC/Telnet/docs
directory.

For specific information concerning configuration for TUBA,
see directions in the 'config20.txt' file included in this
distribution.  Also see 'tubaread.2-0' (this file).



Future Enhancements
-------------------
Features that may be added in the future:

	- ES-IS -- This will relieve the need to configure a static
	  route into the immediately adjacent router.

	- Packet driver support

	- Prototype autoconfiguration of NSAPs and DNS names




Send questions and comments to colella@nist.gov.

--Richard Colella, 6/22/93

NCSA Telnet/TUBA 2.0 now available colella