TS Supplement (Includes RFC-1006 Support)

Overview of the Tandem OSI Architecture

Introduction to RFC-1006

107751 Tandem Computers Incorporated 1–3

TCP/IP as the NSP Process As with previous OSI/AS and OSI/TS releases, X25AM and TLAM may still be

specified as NSP processes, but if you want to run OSI applications over the Internet,

you instead specify TCP/IP as the NSP process.

A single Transport Service Provider (TSP) process can support TCP/IP, X25AM, and

TLAM connections simultaneously. You do not need to add a separate TSP process to

use RFC-1006. Transport connections using X25AM or TLAM as the NSP can co-exist

with transport connections using TCP/IP as the NSP. Configurations for existing

applications using X25AM or TLAM as the NSP are not affected by adding

applications that use RFC-1006.

Figure 1-2 shows how a single TSP process (in the OSI/TS subsystem) can interface

with multiple NSP processes.

Figure 1-2. TSP Process Supporting Multiple NSP Processes

Layer

Transport

Network

Data Link

NSP

(TLAM)

NSP

(X25AM)

010

TSP

NSP

(TCP/IP)

When TCP/IP is the NSP process, it runs as a nonprivileged process in the Tandem

TCP/IP subsystem. The TCP/IP process runs as a Tandem NonStop process pair that

performs services for both client and server programs. It is the base process for all the

other components of the Tandem TCP/IP subsystem.