               Software           Product            Description   J           ________________________________________________________________  I           PRODUCT NAME:  VAX Packetnet System Interface      SPD 25.40.15 .                          (P.S.I.), Version 4.3             DESCRIPTION   H           The VAX Packetnet System Interface (VAX P.S.I.) product allowsF           suitably configured VAX systems to connect to Packet Switch-F           ing Data Networks (PSDNs) conforming to CCITT recommendationE           X.25 (1978, 1980 or 1984) and/or to International Standards I           (ISO) 7776 and 8208. VAX P.S.I. allows a VAX system to function F           as Data Terminal Equipment (DTE) or Data Circuit Terminating%           Equipment (DCE) as follows:   <           o  A packet-mode DTE connected to a supported PSDN  H           o  A packet-mode DTE connected to a DCE conforming to ISO 7776              and 8208   H           o  A packet-mode DCE connected to a DTE conforming to ISO 7776              and 8208   H           o  A combination of the above modes chosen on a per-line basis  I           In this SPD, descriptions referring to PSDNs also apply to sup- H           ported ISO point-to-point connections unless otherwise stated.  F           VAX P.S.I. can be configured for either Native or Multi-host           mode operation:   J           o  VAX P.S.I. Native mode supports direct connections from a VAXG              system to one or more PSDNs, each of which may have one or               more DTEs.   J                                        DIGITAL                   July 1990  J                                                                AE-L066P-TE         E           VAX Packetnet System Interface                 SPD 25.40.15             (P.S.I), Version 4.3      H           o  VAX P.S.I. Multi-host mode provides the features offered byH              VAX P.S.I. Native and also allows VAX P.S.I. Access systems?              to connect to a PSDN as though directly connected.              Features  D           VAX P.S.I. is a VMS layered product and can be used in the           following ways:   4           o  Process-to-process (X.25) communication  5           o  Process-to-terminal (X.29) communication   5           o  Terminal-to-Process (X.29) communication   "           o  DECnet communications  (           o  Open System Interconnection  1           Process-to-process (X.25) Communication   I           VAX P.S.I. supports access for VMS user programs written in VAX F           MACRO and high-level languages such as VAX FORTRAN. ProgramsF           executing in PDP-11 compatibility mode cannot use VAX P.S.I.  F           The VAX P.S.I. programming interface allows application pro-G           grams to access the service interface to the packet level via G           the standard VMS QIO interface. Functions include the setting G           up and breaking of network connections, data transmission and I           reception, sending and receiving of interrupt messages, and re- J           setting of virtual circuits. The interface also allows splittingF           and recombining of messages which are longer than the packet(           size selected for the circuit.  H           The programming interface enables an application program usingH           VMS System Services to communicate with complementary softwareG           on other systems (Digital or non-Digital DTEs) accessible via            the X.25 connection.  G           Process-to-terminal and Terminal-to-process (X.29) Communica-            tion  +                                           2        E           VAX Packetnet System Interface                 SPD 25.40.15             (P.S.I), Version 4.3        H           VAX P.S.I. supports terminal communications according to CCITT2           recommendations X.3, X.28, and X.29 for:  &           o  Outgoing terminal traffic  I              VAX P.S.I. host users may make outgoing calls to other Digi- I              tal or non-Digital CPUs, or suitable network PADs accessible I              via a PSDN, using the X.29 programming interface or by using F              the host-based Packet Assembly/Disassembly (PAD) suppliedH              with VAX P.S.I. The PAD facility accepts DCL-style commands$              or CCITT X.28 commands.  &           o  Incoming terminal traffic  H              The X.29 Interactive Terminal Interface allows remote asyn-F              chronous terminals (character-mode DTEs) connected to theH              network to communicate with the VAX P.S.I. host in a mannerH              similar to local terminals. Dissimilarities may appear as aJ              result of delays caused by the PSDN(s) and various PAD param-I              eter settings chosen by the user or peculiar to the PSDN(s). G              In this case, the remote PAD must perform code conversions J              between ASCII and the code the terminal uses. Note that there=              may be some restrictions imposed by the PSDN(s).   G           Terminal parameters defined in the X.3 recommendation are ex- I           plicitly supported. Network-specific enhancements or extensions J           to the X.3 parameters are available at both the X.29 programmingH           interface and the host-based PAD user interface. Terminal pro-H           cesses that depend on these extensions may cause problems whenI           used on other PSDNs or when accessing one PSDN via another (for )           example, international access).   I           The X.29 terminal interface is compatible with the local termi- I           nal interface except for the facilities where the PSDN does not G           provide adequate support. The X.29 interface includes support H           for specific X.29 signaling. For example, the break key can beH           used to disable output and the interrupt message can be mapped2           directly to the VMS interrupt character.  +                                           3      E           VAX Packetnet System Interface                 SPD 25.40.15             (P.S.I), Version 4.3        H           The host-based PAD employs a DCL-style command syntax offeringI           the ability to reference the CCITT PAD parameters symbolically, E           as well as an interface that conforms to the standard CCITT H           command signals. The host-based PAD also offers the capabilityJ           of running multiple X.29 sessions using the VMS SPAWN and ATTACHH           commands. The host-based PAD supports reception of reselectionG           messages to allow X.29 calls to be redirected to another DTE.   H           The X.29 programming interface is similar to the X.25 program-H           ming interface and allows a VMS process to control the virtualJ           circuit (for example, to modify PAD parameters or clear a call).I           The X.29 programming interface can also be used to make an out- F           going call to a remote PAD. The programming interface allows1           generation of PAD reselection messages.   J           The maximum number of terminals supported (both local and remoteG           X.29) must not exceed the number supported by VMS. The use of G           PVCs for X.29 connections is not defined by the 1980 and 1984 E           CCITT recommendations, and is not available with VAX P.S.I.                    DECnet Communication  F           VAX P.S.I. allows the use of DECnet-VAX facilities over X.25I           circuits. This technique is known as Data Link Mapping (DLM). A I           DECnet-VAX license is required to communicate with other DECnet H           nodes via a PSDN(s). For details, refer to DECnet-VAX Software-           Product Description (SPD 25.03.xx).   %           Open System Interconnection   F           VAX P.S.I. may be used for Open System Interconnection (OSI)I           communication using the OSI Applications Kernel product (OSAK). G           Refer to the VAX OSI Applications Kernel Software Product De- #           scription (SPD 27.47.xx).     +                                           4      E           VAX Packetnet System Interface                 SPD 25.40.15             (P.S.I), Version 4.3        H           VAX P.S.I may be used with VAX FTAM for managing files on openE           systems (refer to VAX FTAM Software Product Description SPDSH           29.86.xx), and with VAX Message Router X.400 Gateway to enableF           message exchange with other X.400 systems in X.400 public orJ           private networks (refer to the VAX Message Router X.400 Software,           Product Description SPD 27.50.xx).  J           VAX P.S.I. also provides features of X.25 which permit a Connec-I           tion Oriented Network Service (CONS) over X.25 according to ISO            8348.e             Virtual Circuits  F           VAX P.S.I. (in Native or Multi-host mode) supports both Per-F           manent Virtual Circuits (PVCs) and Switched Virtual CircuitsF           (SVCs), and supports up to 512 virtual circuits in total per=           host machine. One virtual circuit is used for each:c  :           o  Incoming or outgoing X.29 terminal connection  0           o  X.25 call using either a SVC or PVC  3           o  Active Data Link Mapping (DLM) circuitn             Configuratione  J           VAX P.S.I. provides a configuration procedure to configure a VAXI           P.S.I. system locally. This allows network managers to create arG           configuration after initial installation or subsequently whenV'           reconfiguration is necessary.n             Network Management  E           VMS provides a Network Control Program (NCP) for management G           of both DECnet-VAX and VAX P.S.I. This program allows network H           managers to define the line(s) and PSDN(s) to which the systemE           is connected, select the mode (DTE or DCE) of each, specifyaG           destinations for incoming calls, access counters, and perform &           other maintenance functions.  +                                           5X S   E           VAX Packetnet System Interface                 SPD 25.40.15c            (P.S.I), Version 4.3                   Problem Solving   J           The TRACE utility assists problem solving by tracing and analyz-I           ing information at various stages as it passes between the PSDN I           and the VAX P.S.I. node. Event logging is available by means ofr            normal VMS mechanisms.             P.S.I. Accountingm  E           The P.S.I. Accounting utility enables the system manager tosH           obtain information on VAX P.S.I. and network usage. The P.S.I.F           Accounting utility can extract the information collected andF           display the information directly on a terminal, or write theJ           information to a file. Information can be extracted for selectedF           records or a summary produced. The P.S.I. Accounting utility@           product is compatible with the VMS Accounting utility.  J           In the case of incoming X.29 calls, no information can be storedI           relating to the process/account on which a user is logged; thisdJ           may be obtained through correlation with VMS accounting records.             P.S.I. Securityo  G           The P.S.I. Security utility allows control of both remote DTEhJ           access to VAX P.S.I. and access to the PSDN(s) by VMS processes.I           The Security utility allows for access control on the basis of:r  G           o  The remote DTE numbers involved either on the basis of in-sF              dividual DTE numbers or groups of DTE numbers with common              leading digits.  D           o  The process making the outgoing call or the application(              handling the incoming call.  D           o  Whether or not the call is normally or reverse charged.  I           In addition, when configured in Multi-host mode, VAX P.S.I. canpF           apply security checks to both incoming calls to and outgoingD           calls from any suitably configured VAX P.S.I. Access node.H           Security on both the VAX P.S.I. and the VAX P.S.I. Access node3           is required for comprehensive protection.l  +                                           6P ,  iE           VAX Packetnet System Interface                 SPD 25.40.15a            (P.S.I), Version 4.3                   P.S.I. Mailt  H           The P.S.I. Mail utility allows communication across a PSDN viaG           electronic mail between two VMS systems running VAX P.S.I. or L           VAX P.S.I. Access, using the VMS Mail facility even in the absenceJ           of any DECnet communications between the two DTEs. Refer to the J           VMS Operating System Software Product Description (SPD 25.01.xx).           for more information about VMS Mail.    "           Conformance to Standards  9           VAX P.S.I. conforms to the following standards:e  I           o  CCITT Recommendation X.25 (1978, 1980, or 1984) and ISO 8208cG              and 7776 using the LAPB or LAPBE variants of the data linkA3              level and X.25 packet level protocols.   G           o  ISO 3309 - Frame generation and recognition (not protocol) E              using High-Level Data Link Control (HDLC). Bisynchronous ,              (BSC) framing is not supported.  F           Table 1 (Optional Facility Support) describes the particularJ           aspects of the CCITT X.25 recommendation supported by VAX P.S.I.G           Note that actual support for any given feature depends on they           PSDN used.             Line Interface  D           The electrical line interface used for PSDN communicationsG           depends on the hardware device used. VAX P.S.I. provides only F           the electrical interface of a DTE rather than a DCE and doesH           not provide clock signals. Therefore, an external clock source&           (e.g., a modem) is required.    +                                           7        E           VAX Packetnet System Interface                 SPD 25.40.15p            (P.S.I), Version 4.3        G           The range of supported devices cover V.24, V.35, V.10, RS232, I           RS422 and RS423 over point-to-point, 4-wire, synchronous, full- H           duplex lines at transmission rates up to 256K bits per second,G           as well as ISDN Basic Rate Access at transmission rates up toC           64K bits per second.  ,           Synchronous Communications Devices  E           The communications devices supported by VAX P.S.I. are dif- F           ferent, particularly in the amount of CPUs used. For optimumI           performance, customers are recommended to use a DMA device. Re-oH           fer to the VAX P.S.I. System Support Addendum (25.40.15-x) forI           details of the hardware configurations supported by VAX P.S.I., I           supported line-speeds, and information about the supported syn-c#           chronous driver products.              Prerequisite Support  F           For new PSDNs, the customer and Digital must jointly prepareF           a Network Profile and Customer Support Plan covering all theF           intended network nodes, their usage of SVCs, PVCs, and otherE           network facilities, and their support. Without this NetworktG           Profile and Customer Support Plan, Digital cannot support theb           network connections.                              +                                           8T e  m                   INSTALLATION  I           Digital requires that a customer's first purchase of this soft-.H           ware product include Digital Installation Services. These ser-F           vices provide for installation of the software product by an2           experienced Digital Software Specialist.  H           Only customers experienced with Digital's X.25 products shouldH           attempt second or subsequent installations. Digital recommendsG           that all other customers purchase Digital's Installation Ser-I           vices.  #           Customer ResponsibilitiesS  G           In some cases, the PSDN supplier (or PTT) may impose restric-iE           tions, limitations, or requirements on the proposed Digital)J           network configuration. The customer must ensure that they under-H           stand and adhere to these controls for each and every network.  A           Before installation of the software, the customer must:   I           o  Previously have installed all required software and hardwared!              including terminals.8  F           o  Obtain, install and demonstrate that any modems and otherI              equipment and facilities necessary to interface to Digital's 5              communication equipment are operational.e  G           o  Demonstrate equivalence of operation for modems other than E              Bell[TM] 208A, 208B, 209, 212A synchronous modems, or ine)              Europe, PTT approved modems.g  D           o  Demonstrate that, where necessary, modems used meet the-              appropriate interface standards.s  F           o  Subscribe to the Open User Group and to at least two SVCsH              to complete the product's installation checkout (this testsE              loops information from the VAX P.S.I. system to the PSDN E              and back to VAX P.S.I. system). Systems that use PVCs or H              Closed User Groups only, or where the PSDN does not supportH              calls to the same DTE address, require specially negotiatedB              arrangements for Digital installation of the product.  +                                           9r o  e  E           VAX Packetnet System Interface                 SPD 25.40.15y            (P.S.I), Version 4.3        I           o  Make available, for a reasonable period of time, as mutuallykG              agreed by Digital and the customer, all hardware, communi-VG              cation facilities and terminals that are to be used duringl              installation.  H           Delays caused by any failure to meet the responsibilities willJ           be charged, at the then prevailing rate, for time and materials.  '           Courtesy Installation Service.  H           This software product will be installed by Digital at no addi-H           tional charge if purchased concurrently with a Startup ServiceJ           Package that includes installation service. This service may not(           be available in all countries.  I           This service is available for those configurations which complyPE           with the restrictions described under the SOFTWARE WARRANTYmG           section. Consult the System Support Addendum (SSA 25.40.15-x)mD           for a list of countries and networks where this service is           available.             HARDWARE REQUIREMENTSo  H           VAX, MicroVAX, VAXstation or VAXserver configuration as speci-?           fied in the System Support Addendum (SSA 25.40.15-x).   !           SOFTWARE REQUIREMENTS *o             VMS Operating System  E           For use with the synchronous communications interfaces, thePG           appropriate device driver in the VAX Wide Area Network DevicecJ           Drivers software is required. Refer to the VAX Wide Area NetworkC           Device Drivers Software Product Description SPD 29.64.xx.h  H           For use with the ISDN Basic Rate Access communications device,F           VAX ISDN software and hardware is required. Refer to the VAX9           ISDN Software Product Description SPD 31.23.xx.              ORDERING INFORMATION  +                                          10      E           VAX Packetnet System Interface                 SPD 25.40.15             (P.S.I), Version 4.3        (           Software Licenses: QL-071A*-**%           Software Media: QA-071A*-**e-           Software Documentation: QA-071AA-GZ 0           Software Product Services: QT-071A*-**  I           *  Denotes variant fields. For additional information on avail-WH              able licenses, services and media, refer to the appropriate              price book.             SOFTWARE LICENSING  F           This software is furnished under the licensing provisions ofH           Digital Equipment Corporation's Standard Terms and Conditions.H           For more information about Digital's licensing terms and poli-9           cies, please contact your local Digital office.   %           LICENSE MANAGEMENT FACILITY   I           This layered product supports the VMS License Management Facil-            ity.  H           License units for this product are allocated on a CPU-capacity           basis.  H           For more information on the License Management Facility, referG           to the VMS Operating System Software Product Description (SPD B           25.01.xx) or the VMS Operating System documentation set.  H           For more information about Digital's licensing terms and poli-2           cies, contact your local Digital office.                  +                                          11S d  s      #           SOFTWARE PRODUCT SERVICESl  G           A variety of service options are available. For more informa-r9           tion, please contact your local Digital office.o             SOFTWARE WARRANTYn  H           Warranty for this software product is provided by Digital withE           the purchase of a license for the product as defined in theu1           Software Warranty Addendum of this SPD.n  J           Digital has designed or adapted this software product to operateD           with equipment conforming to ISO 7776/8208 with the publicI           networks in the countries listed in the System Support AddendumcI           (SSA 25.40.15-x), and with certain private PSDNs that have been            approved by Digital.  #           Optional Facility Supportd  I           VAX P.S.I. support for any given CCITT X.25 facility depends onPJ           support for it in the appropriate supported PSDN. Generally, VAXH           P.S.I. is designed to disallow use of facilities that the PSDNG           will not support. Table 1 shows what VAX P.S.I. is capable of H           doing, rather than what it will do when used on any particularE           PSDN. The product documentation describes specific facility36           availability for the supported public PSDNs.  F           Note: Not all optional facilities are supported for use withE           VAX P.S.I. Mail, DECnet Data Link Mapping (DLM) and VAX OSIt           Transport (VOTS).,                  +                                          12a    t  E           VAX Packetnet System Interface                 SPD 25.40.15s            (P.S.I), Version 4.3        J           ________________________________________________________________  +                                   Table 1:  2                          Optional Facility Support  @                                                        Paragraph=                                                        NumberrP                                                        in CCITT X.25  VAX P.S.I.M           Number  Description of the Option              (1984)       Supportr  L           1.      Extended packet sequence numbering     6.2             Yes  L           2.      Non-standard default window size       6.10            Yes  L           3.      Default throughput classes assign-     6.11            N/A                   ment  O           4.      Packet re-transmission                 6.4         See Note 1t  L           5.      Incoming calls barred                  6.5             N/A  L           6.      Outgoing calls barred                  6.6             N/A  L           7.      One-way logical channel outgoing       6.7             N/A  L           8.      One-way logical channel incoming       6.8             Yes  L           9.      Closed User Group                      6.14.1          Yes  L           10.     CUG with outgoing access               6.14.2          Yes  L           11.     CUG with incoming access               6.14.3          Yes  L           12.     Incoming Calls barred within CUG       6.14.4          Yes  L           13.     Outgoing Calls barred within CUG       6.14.5          Yes  L           14.     CUG selection                          6.14.6          Yes    +                                          13r q  e  E           VAX Packetnet System Interface                 SPD 25.40.15o            (P.S.I), Version 4.3    /                               Table 1: (Cont.) c2                          Optional Facility Support    @                                                        Paragraph=                                                        NumbercP                                                        in CCITT X.25  VAX P.S.I.M           Number  Description of the Option              (1984)       Supporti  J           15.     CUG with outgoing access selection     6.14.7         No  K           16.     Absence of both CUG selection          6.14.8         Yes[                   facilities  K           17.     Bilateral CUG                          6.15.1         Yes   K           18.     Bilateral CUG with outgoing access     6.15.2         Yesr  K           19.     Bilateral CUG selection                6.15.3         Yes   K           20.     Reverse charging                       6.18           Yeso  K           21.     Reverse charging acceptance            6.19           Yese  K           22.     Local charge prevention                6.20           N/A   K           23.     Network User identification            6.21           Yes   K           24.     Charging information                   6.22           Yes   K           25.     RPOA selection                         6.23           Yes   O           26.     Hunt group                             6.24        See Note 2   L           27.     Call redirection                       6.25            N/A          +                                          14k  /                               Table 1: (Cont.) l2                          Optional Facility Support    t@                                                        Paragraph=                                                        NumberlP                                                        in CCITT X.25  VAX P.S.I.M           Number  Description of the Option              (1984)       Supportd  J           28.     Called line address modified noti-     6.26          Yes                   fication  J           29.     Call redirection notification          6.27          Yes  J           30.     Transit delay selection and indi-      6.28          Yes                   cation  J           31.     On-line facility registration          6.1            No  K           32.     Non-standard packet size               6.9            YesS  K           33.     Flow control parameter negotiation     6.12           Yesc  K           34.     Throughput class negotiation           6.13           Yes,  K           35.     Fast select                            6.16           Yesh  K           36.     Fast select acceptance                 6.17           Yes   J           37.     D-bit modification                     6.3            No  K           38.     Abbreviated address                    -              N/AX  J           39.     Datagram queue length selection ex     -              No  J           40.     Datagram service signal logical        -              No                   channel       +                                          15t s0                                Table 1: (Cont.) 2                          Optional Facility Support    @                                                        Paragraph=                                                        Number P                                                        in CCITT X.25  VAX P.S.I.M           Number  Description of the Option              (1984)       Supporto  J           41.     Datagram non-delivery indication       -              No  J           42.     Datagram delivery confirmation         -              No  N           43.     Call statistics (non-X.25)             -          See Note 3             Notes:  D           1.    This is not applicable to a DTE. VAX P.S.I. does notF                 support receiving a level 3 Reject packet and will not                 generate one.m  H           2.    The individual DTEs must be assigned their own addressesJ                 independent of the hunt group address. VAX P.S.I. can thenF                 ignore the hunt group. Alternatively, each line on theH                 same CPU can be configured as if connected to a separate5                 PSDN; each with the same DTE address.s  G           3.    VAX P.S.I. does not generate these statistics, however, I                 incoming statistics supplied by the PSDN are available ineH                 the accounting records and at the programming interface.  F           4.    VAX P.S.I. does not support the following items of the*                 CCITT X.25 recommendation:  &                 o  Multi-link protocol  7                 o  Use of the D-bit in outgoing packets       +                                          16T E  OE           VAX Packetnet System Interface                 SPD 25.40.15             (P.S.I), Version 4.3            >           [TM] Bell is a trademark of Bell Telephone Companies  D           [R]  The DIGITAL Logo is a registered trademark of Digital%                Equipment Corporation.e  G           [TM] DECnet-VAX, VAX, MicroVAX, VAXstation, and VAXserver arem;                trademarks of Digital Equipment Corporation.h                                                            +                                          17 