UUCP (AT&T BNU) over STREAMS-based TCP/IP/(Ethernet,X.25)

[Joshua L Mindel]

Initial part of question:
-------------------------
Does anyone have experience with setting up uucp (AT&T BNU) files on 
AT&T 3B2s for a STREAMS-based network?  In particular, for AT&T Enhanced 
TCP/IP WIN/3B Release 3.0 over Ethernet and X.25.

Background:
-----------
I'd like to configure BNU files (on AT&T 3B2s with UNIX System V Release 3.2.2)
so that uucp and cu requests both go through login to connect over an Ethernet
and X.25 network.

Section 9.6 of the AT&T 3B2 Computer UNIX System V Release 3 Sys Admin guide 
provides guidelines for setting up uucp on a STREAMS-based network.  An example
procedure is included for uucp on the AT&T STARLAN network, with the qualifier 
that a similar procedure could be applied for setting up uucp to run on a 
transport provider that is compatible with the AT&T Transport Interface (TLI).

The WIN/3B TCP/IP Release 3.0 product is a transport provider compatible with 
TLI.

After scouring the AT&T Sys Admin guide, WIN/3B docs, and talking with 
Wollongong, I came to realize that there is one critical piece missing from
this picture; the STREAMS module(s) providing the interface between the TTY 
server and TCP.  Using AT&T's terminology for describing the software 
components of a uucp-over-STARLAN configuration, these STREAMS modules are
called Remote Login Modules.  For uucp over STARLAN, these STREAMS modules are 
called LDO and NTTY.

Final part of question:
-----------------------
Do these remote login modules exist for TCP/IP?  If yes, how and where can
I obtain them?

Further clarification of question:
----------------------------------
Leaning heavily on the definition used within the STARLAN environment, I presume
the precise function of these missing modules can be stated as follows:

The remote login modules are the software modules that act as an interface
between the TCP modules and the remote login services provided by the TTY
server.  These modules provide the UNIX character processing and read/write
interface of the standard TTY driver.  This allows existing UNIX TTY
services ("sh", "cu", etc.) to operate over the TCP/IP network.

Paper references for this note:
-------------------------------
 WIN/3B TCP/IP Install/Admin Guide : pages 1-20 to 1-23
 AT&T STARLAN User's Guide	   : pages 4-3 to 4-4

------------------------------
Thanks in advance.

-- 
-------------------------------------------------------------------------------
Joshua L Mindel, Senior Analyst		Internet:  mindel%netwrx1 at uunet.uu.net
NetWorks One				Usenet:	   uunet!netwrx1!mindel
Vienna, VA				Phone:     (703) 827-7767