                          Software           Product            Description   M           ___________________________________________________________________   M           PRODUCT NAME:   HP TCP/IP Services for OpenVMS Version 5.4      SPD            46.46.17             DESCRIPTION   P           The HP TCP/IP Services for OpenVMS software product is the OpenVMS im-M           plementation of the industry-standard TCP/IP protocol suite and in- M           ternet services for OpenVMS Alpha and OpenVMS VAX systems. The ker- O           nel software is ported from the Tru64 UNIX product, which is based on M           the Berkeley Software Distribution (BSD) Versions 4.3 and 4.4, with            enhancements from HP.   E           Note: TCP/IP Services V5.4 is not supported on VAX systems.   N           Internetworking with TCP/IP hides the hardware details of each indi-Q           vidual network and allows computers to communicate independent of their M           physical network connections. Internetworking uses a uniform set of N           protocols to define behavior on an internet for all nodes using sup-O           ported network media. TCP/IP provides both a standard transport mech- R           anism and full-duplex, reliable, stream communication services for soft-           ware applications.             Licenses  N           The following HP TCP/IP Services for OpenVMS licenses are available:                M                                                                September 2003   M                                                                   AE-Q088N-TE            M           HP TCP/IP Services for OpenVMS Version 5.4             SPD 46.46.17   M           ___________________________________________________________________ M           License__________Description_______________________________________   K           Client           For customers who require only client components G                            (FTP [client and server], IMAP, LPD, TELNET, J                            SNMP, NTP, NFS client, Metric Server, POP, FIN-F                            GER, RLOGIN, REXEC, RSH, RMT/RCD, and XDM).  K           Server           For customers who require full product function- J                            ality including all the client components, plusK                            BIND, BOOTP, DHCP, TFTP, NFS Server, PC-NFS, and '                            load broker.   J           Client up-       For customers who previously purchased a clientJ           grade            license and now require full server functional-M           _________________ity.______________________________________________   )           Network Interface Layer Support   M           With support for multiple network interfaces for each physical net- M           work controller, the HP TCP/IP Services for OpenVMS software allows N           OpenVMS systems to connect to individual host computers on different           types of networks:  '           o  Ethernet for IPv4 and IPv6   F           o  Fiber Distributed Data Interface (FDDI) for IPv4 and IPv6              o  Token Ring for IPv4  K           o  Asynchronous transfer mode (ATM) (Alpha systems only) for IPv4   M           Individual host computers can also connect with other hosts or net- M           works over serial communications lines using either the Serial Line Q           Internet Protocol (SLIP or CSLIP) or the Point-to-Point Protocol (PPP).               ,                                            2           M           HP TCP/IP Services for OpenVMS Version 5.4             SPD 46.46.17                 Internet Layer Support  O           The HP TCP/IP Services for OpenVMS product supports the following In- O           ternet layer protocols that work together to move data around the in-            ternet:   M           o  Internet Protocol (IP) provides a connectionless packet delivery '              service for IPv4 and IPv6.   O           o  Internet Control Message Protocol (ICMP) provides diagnostic func- L              tions and handles error and control messages for IPv4 and IPv6.  M           o  Address Resolution Protocol (ARP) dynamically maps an IP address 5              to a physical hardware address for IPv4.   M           o  Neighbor Discovery discovers neighbors in the same link, dynami- P              cally detects routers, dynamically maps all IP addresses to a phys-P              ical hardware address for IPv6, and maintains information about the'              paths to active neighbors.   S           o  Path MTU for TCP and UDP calculates the most efficient means of trans- +              porting data across a network.   R           o  Classless Interdomain Routing (CIDR) reduces routing tables and makes8              more efficient use of the IP address space.  M           o  IPv6 mobile correspondent node allows the OpenVMS host to commu- D              nicate with mobile nodes and other correspondent nodes.  N           o  Routing protocols and routing daemons enable gateways to exchangeP              current routing information about hosts and directly connected net-0              works. Supported protocols include:  O              -  Routing Information Protocol (RIP) Version 1 (RFC 1058) and RIP L                 Version 2 (RFC 1388) for IPv4, and RIPng (RFC 2080) for IPv6  D              -  Open Shortest Path First (OSPF) Version 2 (RFC 1583)  9              -  Exterior Gateway Protocol (EGP) (RFC 904)   B              -  Border Gateway Protocol (BGP) (RFC 1163, RFC 1267)  4              -  Router Discovery (RFC 1256) for IPv4  ,                                            3           M           HP TCP/IP Services for OpenVMS Version 5.4             SPD 46.46.17     M           The routing daemons ROUTED and GATED communicate with the kernel to M           add new routes or to delete or modify existing routes. The Enhanced Q           Gateway Routing Daemon (GATED) is based on GateD Unicast Version 4.0.6, (           with advanced routing options.                                                                          ,                                            4           M           HP TCP/IP Services for OpenVMS Version 5.4             SPD 46.46.17                High Availability   N           failSAFE IP provides higher availability of IP addresses by removingM           the NIC as a single point of failure. failSAFE IP is cluster aware, R           so standby IP addresses can be configured within the same node or acrossM           a cluster. Typical failures that failSAFE IP guards against include P           NIC failure, broken cable, failed port on a switch, and node shutdown.    !           Transport Layer Support   M           To provide either connection-oriented or connectionless data trans- M           mission between two hosts (local or remote), the HP TCP/IP Services M           for OpenVMS product supports both TCP and UDP protocols. These pro- M           tocols form the bridge between the Application layer and the Inter-            net layer:  O           o  Transmission Control Protocol (TCP) provides reliable, connection- P              oriented, sequenced data transfers for applications that must guar-(              antee delivery of the data.  S           o  User Datagram Protocol (UDP) provides fast, connectionless data trans- M              fers for applications that do not require delivery confirmation.   P           The TCP Extensions for High Performance (RFC 1323), and the IETF Wire-P           less TCP Standards help prevent congestion on low-bandwidth high-delayP           wireless and satellite networks. The wireless TCP set of standards en-M           compasses TCP Extensions for High Performance (RFC 1323), SACK (RFC P           2018), and Path MTU Discovery for IPv4 (RFC 1191) and IPv6 (RFC 1981).  O           -  RFC 1323 includes support for PAWS (Protection Against Wrapped Se- P              quence) numbers, which supplies time stamps on transactions to pre-O              vent wrapped sequence numbers and for TCP window scale, which pro- <              vides window scale factors for TCP connections.  N           -  RFC 2018 defines TCP selective acknowledgment options, supportingN              multiple acknowledgment windows and allowing outstanding acknowl-@              edgments even if sequence numbers are not in order.      ,                                            5           M           HP TCP/IP Services for OpenVMS Version 5.4             SPD 46.46.17     #           Application Layer Support   M           The HP TCP/IP Services for OpenVMS product supports numerous Appli- =           cation layer protocols that allow OpenVMS users to:   +           o  Run software on remote systems   A           o  Transfer data files between local and remote systems   P           o  Share remote system resources such as disk storage space and print-N              ers as if they were directly connected to the user's local system  S           o  Send and receive electronic mail messages locally or across the world-               wide Internet  P           o  Provide consistent, reliable, and efficient network services to all"              users on the internet             Remote Computing  M           With TELNET, an OpenVMS user can log in to remote hosts in the net- ,           work. The TELNET features include:  +           o  Simultaneous multiple sessions   7           o  IBM 3270 model terminal emulation (TN3270)   E           o  Support for both OpenVMS style and UNIX style interfaces   N           o  Support for window sizing (rows and columns) and location options  $           o  Kerberos authentication  P           The popular UNIX Remote commands, called R commands, let OpenVMS usersS           work in accounts on remote internet hosts that are either UNIX or OpenVMS S           systems. The HP TCP/IP Services for OpenVMS software supports the RLOGIN, +           RSH, REXEC, and RMT/RCD commands.   O           The SSH command logs into a remote server and provides remote command O           execution using authentication and data encryption to ensure a secure            connection.   ,                                            6           M           HP TCP/IP Services for OpenVMS Version 5.4             SPD 46.46.17     P           The FINGER utility enables users to obtain information about each userN           on local or remote systems. This information includes user name, ac-:           count name, and the program the user is running.  O           The X Display Manager Control Protocol (XDMCP) allows display devices B           to request that the login server present a login screen.             File Transfer   T           OpenVMS users transfer data files between local and remote systems through.           the use of the following components:  P           o  File Transfer Protocol (FTP) creates, deletes, and copies files and'              directories between hosts.   M           FTP supports OpenVMS Extended File Specifications (long file names, I           deep directories, and extended character sets) for ODS-5 disks.   P           o  Trivial File Transfer Protocol (TFTP) transfers files using the UDPR              protocol and no authentication and is typically used during the boot-/              strap process of diskless systems.   N           o  The remote copy (rcp) command copies files between the local host;              and a remote host or between two remote hosts.   O           o  The secure copy (SCP) and secure file transfer (SFTP) commands en- O              sure secure file copy operations using authentication and data en-               cryption.             Resource Sharing  M           The HP TCP/IP Services for OpenVMS software provides network print- M           ing services through the line printer/line printer daemon (LPR/LPD) 4           and the TELNET print symbiont (TELNETSYM).  N           o  LPD provides remote printing services for UNIX and OpenVMS clientN              hosts through local and remote print queues. Once the system man-N              ager sets up the print queues, OpenVMS client users enter the DCLH              command PRINT, and UNIX client users enter the lpr command.  Q           LPD can be configured for clusterwide availability, providing load bal- N           ancing and automatic failover for LPD-controlled print queues on the           OpenVMS host.   ,                                            7           M           HP TCP/IP Services for OpenVMS Version 5.4             SPD 46.46.17     R           o  TELNETSYM provides remote print services that enable the use of stan-G              dard OpenVMS printing features not available with LPR/LPD.              Network File System   O           The Network File System (NFS) server software allows NFS client users N           to gain transparent access to remote file services. With NFS, when aO           user accesses files and directories from a remote system, they appear M           to reside on the local system regardless of operating system, hard- N           ware type, or architectural differences between the local and remoteO           systems. The PC-NFS daemon provides authentication services to PC-NFS            clients.  M           TCP/IP Services provides support for NFS Version 2 and Version 3 in O           the NFS server. The NFS client is limited to Version 2. The main ben- O           efit of NFS Version 3 is increased maximum file size-up to 1 terabyte O           for an OpenVMS file system and up to 4 gigabytes for a container file            system.   N           Performance gains may result from the improvements to file-size pro-O           cessing and the enhanced write performance that allows the NFS server N           to acknowledge a write operation before the files are actually writ-P           ten to disk. Afterward, the server's response to a commit message con-7           firms that the data has been written to disk.   O           The NFS server supports communication over both TCP and UDP. NFS over M           TCP offers better support for file access over wide area links than 5           UDP. The NFS client is limited to UDP only.   Q           The NFS server and client support OpenVMS Extended File Specifications, M           including long file names, deep directories, and extended character (           sets on ODS-5 file structures.                  ,                                            8           M           HP TCP/IP Services for OpenVMS Version 5.4             SPD 46.46.17                Electronic Mail   O           With the Simple Mail Transfer Protocol (SMTP), OpenVMS users can send M           and receive electronic mail to and from local and remote hosts. The P           HP TCP/IP Services for OpenVMS implementation of SMTP uses the OpenVMSO           Mail facility, which automatically recognizes an SMTP host address in P           the format smith@widgets.com. SMTP provides support for SFF (Send From1           File) and outbound alias specification.   P           The following mail systems work with SMTP, providing reliable, server-.           based mail repositories for clients:  .           o  Post Office Protocol (POP) server  2           o  IMAP Mail server (Alpha systems only)             Network Services  M           With the following HP TCP/IP Services for OpenVMS management compo- N           nents, network and system managers can provide consistent, reliable,J           and efficient services to their users with minimal interruption:  P           o  Simple Network Management Protocol (SNMP) Version 2 includes a mas-M              ter agent and subagents that allow the OpenVMS system to be man- O              aged by a management station on the network. This version includes P              the same features found in the HP Tru64 UNIX SNMPv2 implementation,+              along with other improvements.   O           o  Network Time Protocol (NTP) Version 4 provides a means to synchro- P              nize time and coordinate time distribution throughout a TCP/IP net-O              work. NTP provides accurate and dependable timekeeping for OpenVMS &              hosts on TCP/IP networks.  P           o  Berkeley Internet Name Domain (BIND) is a distributed database sys-O              tem that distributes and manages host information so that hosts do N              not need to locally manage the address of every other host on theM              internet. The BIND 9 server (available on Alpha systems only) is M              based on the Internet Software Consortium's (ISC) BIND 9.2.1 im- N              plementation. It includes dynamic updates and BIND server clusterP              failover, which allows multiple BIND master servers to share a com-N              mon database, thus providing both redundancy and a failover mech-?              anism when one of the servers becomes unavailable.   ,                                            9           M           HP TCP/IP Services for OpenVMS Version 5.4             SPD 46.46.17     N           The BIND resolver on both VAX and Alpha systems, and the BIND serverK           on VAX systems, are based on the ISC's BIND 8.1.2 implementation.   N           o  Load broker supplies cluster load balancing, round-robin schedul-)              ing, and automatic failover.   Q           o  Metric server calculates and reports the DNS load on the local host. M              It includes dynamic configuration of logical names, which can be O              defined for CPU rating, compute interval, and debug level, as well M              as support for multihomed systems to allow load balancing of in- 9              coming traffic across multiple IP addresses.   N           o  Portmapper allocates ports so that system managers do not need toM              preconfigure client applications with port numbers for each ser-               vice.  O           o  Auxiliary server process is the HP TCP/IP Services for OpenVMS im- S              plementation of the UNIX internet daemon (inetd). The auxiliary server O              greatly simplifies application writing, manages overhead by reduc- P              ing simultaneous server processes, provides system security throughM              authentication of service requests, and supports event and error               logging.   R           o  Dynamic Host Configuration Protocol (DHCP) is a superset of the Boot-P              strap Protocol (BOOTP). In addition to BOOTP functionality (answer-P              ing bootstrap requests), DHCP offers robust configuration services,O              including IP address, subnet masks, and default gateways. The DHCP O              server can be configured to support BOOTP clients. If BOOTP is en- E              abled without DHCP, DHCP functionality is not available.   S           o  DHCP dynamically updates BIND using a feature that allows DHCP clients P              to be configured with a registered name. DHCP uses this name to as-Q              sign an address when it updates the BIND database. In addition, this P              release offers both a DHCP client and server, which provides a cen-M              tralized approach to the configuration and maintenance of IP ad- N              dress space. With DHCP server, the system manager can provide dy-C              namic allocation of IP addresses from an OpenVMS host.         -                                            10            M           HP TCP/IP Services for OpenVMS Version 5.4             SPD 46.46.17                Security  O           The HP TCP/IP Services for OpenVMS product provides optional security             mechanisms, including:             o  Secure POP   M           SSL (Secure Sockets Layer) is supported for POP (Post Office proto- 3           col), providing secure retrieval of mail.   O           The secure POP server accepts connections on port 995. Secure POP en- Q           crypts passwords, data, and POP commands and is compatible with clients 5           that use SSL, such as Microsoft[R] Outlook.   O           To use this feature, you must download the HP SSL kit for OpenVMS Al- 
           pha                                                   -                                            11            M           HP TCP/IP Services for OpenVMS Version 5.4             SPD 46.46.17                o  SSH for OpenVMS  M           The Secure Shell (SSH) for OpenVMS client and server provide secure N           login, remote command execution, and file transfer. This implementa-O           tion is based on SSH2 Version 2.4.1, from SSH Communications Security            Corp.   %           Performance and Scalability   N           The TCP/IP kernel has been modified to provide increased performanceQ           on symmetric multiprocessing (SMP) systems. The new kernel is optional. ?           The default is to run with the classic TCP/IP kernel.   O           This complete redesign of the TCP/IP kernel provides enhanced perfor- N           mance on SMP systems by removing CPU contention among users. The newP           kernel uses a dynamic spinlock to lock the main internal database. AllM           processing that requires locking is directed to a designated TCP/IP N           CPU, thereby eliminating CPU contention with other CPU users. Essen-Q           tially, network I/O becomes a series of asynchronous, transaction-based            operations.   $           Management Control Program  Q           The HP TCP/IP Services for OpenVMS product provides the Management Con- M           trol Program, which is a comprehensive, easy-to-use network manage- P           ment tool based on familiar OpenVMS DCL command syntax. These commandsN           let system managers configure and monitor the product components lo-           cally.  M           The flexible configuration process includes an interactive configu-            ration procedure.   N           Startup and shutdown files are provided for individual services, al-N           lowing system managers to stop and start individual services withoutL           affecting the operation of the remaining TCP/IP Services software.  O           Support for both DCL or UNIX management commands provides a choice of N           methods for configuring and managing the network connections and the#           TCP/IP Services software.     -                                            12            M           HP TCP/IP Services for OpenVMS Version 5.4             SPD 46.46.17     +           UNIX Network Management Utilities   M           The HP TCP/IP Services for OpenVMS product provides UNIX networking N           management utilities for system managers who are experienced in man-O           aging and troubleshooting the UNIX network subsystem. Supported util-            ities include:             o  arp             o  finger              o  ifconfig              o  netstat             o  ping              o  ripquery              o  route             o  sysconfig             o  sysconfigdb             o  tcptrace              o  traceroute              o  tcpdump  D           Subsystems can be configured in the sysconfigtab database.  H           Note that some UNIX flags and parameters may not be supported.  %           Error Message Documentation   M           The HP TCP/IP Services for OpenVMS product provides online help for N           error messages for TCP/IP facilities and components. The informationK           is included as part of the OpenVMS Help Message utility (MSGHLP).   -                                            13            M           HP TCP/IP Services for OpenVMS Version 5.4             SPD 46.46.17     3           Application Programming Interfaces (APIs)   P           The HP TCP/IP Services for OpenVMS product provides the following APIs=           for programmers to develop customized applications:   N           o  Berkeley Sockets and Sockets Library provide UNIX like access forN              TCP, UDP, and raw IP to applications written in the C programming8              language. The library includes support for:  M              -  Both IPv4 and IPv6 basic socket interface extensions for IPv6 +                 (RFC 2553 and IETF updates)   I              -  Advanced sockets API for IPv6 (RFC 2292 and IETF updates)   N           o  The $QIO interface extends the OpenVMS system services for socketN              communications, providing access to TCP, UDP, and IP for applica->              tions written in supported programming languages.  O           o  The SRI $QIO interface translates older, incompatible SRI $QIO in- +              terfaces into $QIO interfaces.   M           o  ONC RPC provides an industry-standard, portable API for program- P              mers who do not have an in-depth knowledge of networking protocols.N              This is an efficient alternative to application development using              sockets.   P           o  Extensible Simple Network Management Protocol (eSNMP) provides rou-/              tines for building SNMP subagents.   <           PATHWORKS, Advanced Server, and DECnet over TCP/IP  N           The HP TCP/IP Services for OpenVMS product includes the PATHWORKS IPM           (PWIP) driver and the PWIP ancillary control process (PWIP_ACP) for D           improved PATHWORKS/Advanced Server and TCP/IP integration.  N           The PWIP driver allows communication between OpenVMS systems runningS           both PATHWORKS Advanced Server or Advanced Server for OpenVMS, and TCP/IP O           Services software, and personal computers running PATHWORKS 32 client P           software. It also enables the DECnet-over-TCP/IP feature, which is in-M           cluded with the DECnet-Plus for OpenVMS. (For more information, see 5           the DECnet-Plus for OpenVMS documentation.)   -                                            14            M           HP TCP/IP Services for OpenVMS Version 5.4             SPD 46.46.17     (           INSTALLATION AND CONFIGURATION  P           System managers install the HP TCP/IP Services for OpenVMS product us-N           ing the POLYCENTER Software Installation utility. A menu-driven con-P           figuration procedure makes it easy to enable either all components and(           services or only those needed.             HARDWARE REQUIREMENTS              Supported Processors  N           The HP TCP/IP Services for OpenVMS product supports central process-Q           ing units (CPUs) running OpenVMS. For a complete list of hardware prod- N           ucts, see the SPD for the specific OpenVMS operating system release.  &           Required Network Controllers  N           The HP TCP/IP Services for OpenVMS software supports all network de-N           vices listed in the Software Product Description for the OpenVMS Op-B           erating System for Alpha and VAX systems (SPD 25.01.xx).  O           The HP TCP/IP Services for OpenVMS software can share an Ethernet in- T           terface with other HP networking products such as DECnet-Plus for OpenVMS.             Memory Requirements   M           The following table shows the minimum amount of memory required for O           the HP TCP/IP Services for OpenVMS product under the client or server            license.  M           ___________________________________________________________________ M           System___________Minimum_Memory____________________________________   M           OpenVMS_Alpha____32_MB_____________________________________________               -                                            15            M           HP TCP/IP Services for OpenVMS Version 5.4             SPD 46.46.17     !           Disk Space Requirements   M           The approximate amount of space required on the system disk to sup- P           port the HP TCP/IP for OpenVMS software under the client or server li-P           cense is as follows. Actual sizes may vary depending on the system en-9           vironment, configuration, and software options.   M           ___________________________________________________________________ M           System_________________Free_Blocks_Required________________________   M           OpenVMS_Alpha__________125,000_____________________________________              CLUSTER SUPPORT   P           The HP TCP/IP Services for OpenVMS product is fully supported when in-J           stalled on any valid and licensed OpenVMS Cluster configuration.             SOFTWARE REQUIREMENTS   P           To qualify for a software support contract, the HP TCP/IP Services forN           OpenVMS Version 5.4 product requires the following OpenVMS operating           system versions:  7           OpenVMS Alpha systems, Version 7.3-1 or 7.3-2   O           Client access requires a system that supports the protocols specified M           by NFS Version 2 or Version 3, and all TCP/IP application protocols <           defined by the TCP/IP Request for Comments (RFCs).  O           For Systems Running XDMCP: DECwindows Motif for OpenVMS, Version 1.2-            5 (or later)             GROWTH CONSIDERATIONS   O           The minimum hardware and software requirements for any future version M           of the HP TCP/IP Services for OpenVMS product may be different from ;           the minimum requirements for the current version.         -                                            16            M           HP TCP/IP Services for OpenVMS Version 5.4             SPD 46.46.17                DISTRIBUTION MEDIA  N           Media and documentation for the HP TCP/IP Services for OpenVMS prod-J           uct are available on the HP CD-ROM Software Library for OpenVMS.  O           o  To order the HP CD-ROM Software Library for OpenVMS for Alpha sys- 0              tems, use order number QA-03XAA-H8.  M           o  To order the HP CD-ROM Software Library for OpenVMS for VAX sys- 0              tems, use order number QA-5G88A-H8.             ORDERING INFORMATION  5           HP TCP/IP Services for OpenVMS Alpha Server   +              Software Licenses: QL-0LXA*-** 0              Software Documentation: QA-0LXAA-GZ3              Software Product Services: QT-0LXA*-**   5           HP TCP/IP Services for OpenVMS Alpha Client   +              Software Licenses: QL-0M2A*-** 0              Software Documentation: QA-0LXAA-GZ3              Software Product Services: QT-0M2A*-**   =           HP TCP/IP Services for OpenVMS Alpha Client Upgrade   *              Software License: QL-0PHA*-**0              Software Documentation: QA-0LXAA-GZ3              Software Product Services: QT-0PHA*-**   3           HP TCP/IP Services for OpenVMS VAX Server   +              Software Licenses: QL-VHRA*-** (              Software Media: QA-VHRAA-H*0              Software Documentation: QA-VHRAA-GZ3              Software Product Services: QL-VHRA*-**   3           HP TCP/IP Services for OpenVMS VAX Client   +              Software Licenses: QL-GL7A*-** 0              Software Documentation: QA-VHRAA-GZ  -                                            17            M           HP TCP/IP Services for OpenVMS Version 5.4             SPD 46.46.17     3              Software Product Services: QT-GL7A*-**   ;           HP TCP/IP Services for OpenVMS VAX Client Upgrade   *              Software License: QL-OPJA*-**0              Software Documentation: QA-VHRAA-GZ3              Software Product Services: QT-OPJA*-**   O           *  Denotes variant fields. For additional information about available P              licenses, services, and media, refer to the appropriate price book.M              This ordering information was valid at the time of release. Con- J              tact your HP representative for current ordering information.             SOFTWARE LICENSING  M           This software is furnished under license only. For more information P           about HP licensing terms and policies, contact your HP representative.  O           The client license provides complete product functionality except for R           the following server components: NFS server, BIND server, PC-NFS server,J           the remote BOOT server, the DHCP server, and the RMT/RCD server.  -           License Management Facility Support   M           The HP TCP/IP Services for OpenVMS product supports the OpenVMS Li- *           cense Management Facility (LMF).  N           For information about the License Management Facility, see the soft-M           ware product description for the OpenVMS operating system for Alpha O           and VAX systems (SPD 25.01.xx), or consult the OpenVMS documentation.r             SOFTWARE WARRANTY   O           This software is provided by HP with a 90-day conformance warranty in N           accordance with the HP warranty terms applicable to the license pur-           chase.          -                                            18v s  r      M           HP TCP/IP Services for OpenVMS Version 5.4             SPD 46.46.17s    #           SOFTWARE PRODUCT SERVICES   N           A variety of service options are available from HP. For detailed in-L           formation about the service options, contact your local HP office.  O           The product information in this SPD was valid at time of release. For D           current product information, contact your local HP office.  :            2003 Hewlett-Packard Development Company, L.P.  M           Microsoft[R] is a US registered trademark of Microsoft Corporation.d  >           UNIX[R] is a registered trademark of The Open Group.  O           The information contained herein is subject to change without notice.tO           The only warranties for HP products and services are set forth in thedN           express warranty statements accompanying such products and services.O           Nothing herein should be construed as constituting an additional war-aR           ranty. HP shall not be liable for technical or editorial errors or omis-!           sions contained herein.:  P           Proprietary computer software. Valid license from HP required for pos-N           session, use or copying. Consistent with FAR 12.211 and 12.212, Com-O           mercial Computer Software, Computer Software Documentation, and Tech-4M           nical Data for Commercial Items are licensed to the U.S. Government_5           under vendor's standard commercial license._                              -                                            19     r      M           HP TCP/IP Services for OpenVMS Version 5.4             SPD 46.46.17n                                                                                      -                                            20 