NCSA Telnet/TUBA 3.0 Available

colella@nist.gov Wed, 19 January 1994 18:19 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07185; 19 Jan 94 13:19 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa07175; 19 Jan 94 13:19 EST
Received: from mailhost.lanl.gov by CNRI.Reston.VA.US id aa12658; 19 Jan 94 13:19 EST
Received: from noc-gw.lanl.gov by mailhost.lanl.gov (8.6.4/1.2) id LAA18939; Wed, 19 Jan 1994 11:18:31 -0700
Received: from localhost by noc-gw.lanl.gov (8.6.4/SMI-4.1) id LAA10494; Wed, 19 Jan 1994 11:18:51 -0700
Received: from mailhost.lanl.gov by noc-gw.lanl.gov (8.6.4/SMI-4.1) id LAA10491; Wed, 19 Jan 1994 11:18:50 -0700
Received: from emu.ncsl.nist.gov by mailhost.lanl.gov (8.6.4/1.2) id LAA18792; Wed, 19 Jan 1994 11:17:42 -0700
Received: by emu.ncsl.nist.gov (4.1/NIST(rbj/dougm)) id AA00432; Wed, 19 Jan 94 13:25:29 EST
Date: Wed, 19 Jan 1994 13:25:29 -0500
Organization: National Institute of Standards and Technology (NIST)
Sub-Organization: Computer Systems Laboratory (CSL)
Message-Id: <9401191825.AA00432@emu.ncsl.nist.gov>
To: tuba@lanl.gov
Subject: NCSA Telnet/TUBA 3.0 Available
Cc: noop@merit.edu, iso@nic.ddn.mil, wg-llt-clns@rare.nl
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: colella@nist.gov
Reply-To: colella@nist.gov

            NCSA Telnet 2.3.05/TUBA 3.0 Now Available
            -----------------------------------------

The next release of NCSA Telnet with TUBA is now available.  The
major changes from earlier versions are:

        - ESIS added,

        - clnp trace program included, and,

        - packet drivers supported.

See the attached release notes for more information.

--Richard




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

        Release Notes for NCSA Telnet 2.3.05 (TUBA 3.0)
        -----------------------------------------------
                         January 1994
                         ------------


This distribution is a modified version of NCSA Telnet 2.3.05
that implements TUBA (TCP and UDP with Bigger Addresses -- see RFC
1347).  The changes allow TCP and a number of Internet applications
to run over both IP and CLNP (the choice is made on a per TCP
connection basis).  For the technical details on TUBA see the list of
references at the end of these notes.

Send questions and comments on NCSA Telnet/TUBA to colella@nist.gov.

                                          --Richard Colella, 1/19/94





Getting Started
---------------
To get started with NCSA Telnet/TUBA:

        1. Retrieve the distribution and unpack it as described
           below in "Obtaining the Distribution".

        2. Edit the 'config.tel' file to reflect your local
           configuration information.  See "Configuration
           Information" below for pointers to the appropriate
           documentation.

        3. If you don't already use one, you'll have to get a
           packet driver to go between NCSA Telnet and your ethernet
           card.  This is covered a bit more in the TUBA-specific
           configuration file, 'config30.txt', referenced in the
           "Configuration Information" section below.

        4. Run any of the executables mentioned in the "Programs
           in the Distribution" section.  If you have CLNP
           connectivity into the Internet, try:

                - ctrace infidel.tuba.ncsl.nist.gov or
                  cursive.tuba.ncsl.nist.gov

                - cping infidel.tuba.ncsl.nist.gov or
                  cursive.tuba.ncsl.nist.gov

                - telnetting to infidel.tuba.ncsl.nist.gov and
                  logging in with user name 'guest' and password
                  'tuba-sys'

           [Note: infidel is a modified BSDi BSD/386 system; cursive
            is a PC running NCSA Telnet/TUBA.  NSAPs for both systems
            are retrieved by the executable from the DNS.]


That's it.  For more information on what's happening with TUBA see
the "References" section at the end of this file and join the TUBA WG
mailing list:

        tuba-request@lanl.gov        -- add/delete requests
        tuba@lanl.gov                -- discussion



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

   ./pub/ncsa_tuba/tuba3-0.exe            -- executables only
   ./pub/ncsa_tuba/tuba3-0s.exe           -- sources and executables

(Don't forget to use image mode transfer!)

The *.exe files were created with pkzip version 2.04g as self-
extracting executables.  The tuba3-0.exe file contains everything you
need to run NCSA Telnet/TUBA.  After retrieving it to your DOS PC,
just type "tuba3-0" and it will unpack itself.

Only pick up the tuba3-0s.exe if you *really* want the sources.  When
unpacking the sources type "tubas3-0s -d" and it will unpack itself
(the -d flag maintains the directory structure during unpacking).

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 2.* and TUBA 3.0
-----------------------------------------
Three major features have been added for TUBA 3.0:

        - clnp trace program:  An initial version of a CLNP
          traceroute program has been added (thanks to Raoul Alcala,
          Erik Sherk, and Jack Waters of SURANet).  Try 'ctrace' with
          no parameters for usage info.  [Note:  this program will
          get a bit of polish later on, but it's quite useful in its
          present form].

        - ESIS:  Full ESIS is supported.  ESIS is roughly equivalent
          to ARP and RARP.  It enables ESs (hosts) and ISs (routers)
          to locate each other with no a priori configuration
          information (this eliminates the need for those !#@*&
          static ES routes in the routers!).  ESIS also allows ESs on
          the same wire to communicate with each other in the absense
          of an IS (with no additional configuration info).

        - Packet Drivers:  Packet drivers are "in".  Although packet
          drivers are a stock feature of NCSA Telnet, they were not
          used to support TUBA operations in the TUBA 2.0 release
          (although support for PDs was added in an interim 2.*
          release).  Note that packet drivers *must* be used to
          support ESIS -- see 'config30.txt' for details.


One significant change has also been made between 2.* and 3.0:

        - The LPORT ftp command has been renamed LPRT to maintain
          the four-character de facto limit on ftp commands (see
          RFC 1545).  NCSA Telnet/TUBA 3.0 continues to *accept*
          the LPORT command (in addtion to LPRT) from other ftp
          initiators, but will only generate the LPRT command.
          TUBA users are *strongly* encouraged to move to 3.0. to
          avoid interoperability problems.

Other minor changes have been made, too numerous to mention (or
remember).



Programs in the Distribution
----------------------------
The following executables are compiled and ready to go in either
the binaries-only or full distribution:

    telbin.exe - The basic NCSA Telnet program.  Includes
         an ftp responder that supports operation over TUBA
         using the LPRT 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 LPRT command.

    ctrace.exe - A clnp version of traceroute.

    telpass.exe - The stock NCSA Telnet password management utility.


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' in the source distribution executes 'make' on
the five makefiles for the telbin, finger, clnping, ftpbin and ctrace
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 'config30.txt' file included in this
distribution.  Also see 'tubaread.3-0' (this file).



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

        - Various improvements to ctrace, such as reverse lookup of NSAPs.

        - Prototype autoconfiguration of DNS names.



References
----------

RFC 1347, "TCP and UDP with Bigger Addresses (TUBA), A
        Simple Proposal for Internet Addressing and Routing,"
        Ross Callon, June 1992.

RFC 1561, "Use of ISO CLNP in TUBA Environments," Dave
        Piscitello, December 1993.

RFC 1545, "FTP Operation Over Big Address Records (FOOBAR),"
        Dave Piscitello, November 1993.

Internet-Draft, "DNS NSAP Resource Records"
        (draft-manning-dns-nsap-04.txt), Bill Manning and
        Richard Colella, December 1, 1993.

Internet-Draft, "An Echo Function for ISO 8473"
        (draft-ietf-noop-echo-02.txt), Cathy Wittbrodt and
        Sue Hares, April 13, 1993.