                          Software           Product            Description   M           ___________________________________________________________________   D           PRODUCT NAME:   HP TCP/IP Services for OpenVMS Version 5.6           SPD 46.46.21             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- P           ternet services for OpenVMS Industry standard 64 (I64) and OpenVMS Al-O           pha systems. The kernel software is ported from the Berkeley Software M           Distribution (BSD) Versions 4.3 and 4.4, with enhancements from HP.   M           TCP/IP Services installation is integrated with the OpenVMS instal- N           lation. It provides interoperability between OpenVMS and other oper-M           ating systems that support TCP/IP, such as UNIX[R] and Microsoft[R] O           Windows[R]. A comprehensive suite of functions and applications based M           on industry-standard protocols allow heterogeneous network communi- X           cations and file sharing, as well as network services such as IP/multicasting,P           dynamic load balancing, remote login, network file access, remote ter-O           minal access, remote printing, email, application development, remote M           client booting, domain name system (DNS), and network time protocol            (NTP).  M           TCP/IP Services operates in both IPv4 and IPv6 networks, as well as R           in mixed environments, and provides high availability, performance scal-N           ability for SMP systems, and secure authentication and data transfer?           for remote sessions, network applications, and email.               M                                                                     June 2006            M           HP TCP/IP Services for OpenVMS Version 5.6             SPD 46.46.21                Licenses  O           For Alpha systems, the following TCP/IP Services for OpenVMS licenses            are available:  M           ___________________________________________________________________ M           License__________Description_______________________________________   C           Server           Provides complete product functionality.   G           Client           Provides a subset of the server license. The G                            client license does not include BIND, BOOTP, K                            DHCP, failSAFE IP, TFTP, NFS server, PC-NFS, and +                            the load broker.   K           Client up-       Provides a subset of the server license for cus- K           grade            tomers who previously purchased a client license M           _________________and_now_require_full_functionality._______________   M           For OpenVMS I64, the Operating Environment (OE) includes the TCP/IP C           Services for OpenVMS product and a server license for it.   )           Network Interface Layer Support   M           With support for multiple network interfaces for each physical net- R           work controller, the TCP/IP Services for OpenVMS software allows OpenVMSO           systems to connect to individual host computers on different types of            networks:   G           o  Ethernet for IPv4 and IPv6 (OpenVMS I64 and OpenVMS Alpha)   M           o  Fiber Distributed Data Interface (FDDI) for IPv4 and IPv6 (Open-               VMS Alpha only)  5           o  Token Ring for IPv4 (OpenVMS Alpha only)   K           o  Asynchronous transfer mode (ATM) for IPv4 (OpenVMS Alpha only)         ,                                            2           M           HP TCP/IP Services for OpenVMS Version 5.6             SPD 46.46.21     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).   8           Note: SLIP is supported on Alpha systems only.              Internet Layer Support  O           The TCP/IP Services for OpenVMS product supports the following Inter- O           net layer protocols that work together to move data around the Inter-            net:  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.  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  M              -  Open Shortest Path First (OSPF) Version 2 (RFC 1583) for IPv4   B              -  Exterior Gateway Protocol (EGP) (RFC 904) for IPv4  ,                                            3           M           HP TCP/IP Services for OpenVMS Version 5.6             SPD 46.46.21     K              -  Border Gateway Protocol (BGP) (RFC 1163, RFC 1267) for IPv4   4              -  Router Discovery (RFC 1256) for IPv4  M              -  Routing daemons communicate with the kernel to add new routes M                 or to delete or modify existing routes. The following routing &                 daemons are supported:  "                 *  ROUTED for IPv4  %                 *  GATED for IPv4 [1]   #                 *  ip6rtrd for IPv6              High Availability   &           o  failSAFE IP supports IPv6  N           The failSAFE IP service provides higher availability of IP addressesP           by removing the NIC as a single point of failure. failSAFE IP is clus-N           ter aware, so standby IP addresses can be configured within the sameT           node or across a cluster. Typical failures that failSAFE IP guards againstN           include 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- N           mission between two hosts (local or remote), the TCP/IP Services forN           OpenVMS product supports both TCP and UDP protocols. These protocolsO           form the bridge between the Application layer and the Internet 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.             ____________________N         [1] The Enhanced Gateway Routing Daemon (GATED) is based on GateD Uni-  >             cast Version 4.0.6, with advanced routing options.  ,                                            4           M           HP TCP/IP Services for OpenVMS Version 5.6             SPD 46.46.21     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).    #           Application Layer Support   O           The TCP/IP Services for OpenVMS product supports numerous Application 6           layer protocols that allow OpenVMS users to:  ,           o  Run software on remote systems.  B           o  Transfer data files between local and remote systems.  P           o  Share remote system resources such as disk storage space and print-O              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             New Features:   1           o  TELNET Upgrade with Kerberos Support   '           o  TELNET Server Device Limit   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)   ,                                            5           M           HP TCP/IP Services for OpenVMS Version 5.6             SPD 46.46.21     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 P           systems. The TCP/IP Services for OpenVMS software supports the RLOGIN,+           RSH, REXEC, and RMT/RCD commands.   O           In addition, the secure shell (SSH) command logs into a remote server M           and provides remote command execution using authentication and data 3           encryption to ensure a secure connection.   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              New Feature:  ;           o  FTP Performance Enhancements for VMS Plus Mode   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 andP              directories between hosts. FTP supports OpenVMS Extended File Spec-N              ifications (long file names, deep directories, and extended char-)              acter 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.   ,                                            6           M           HP TCP/IP Services for OpenVMS Version 5.6             SPD 46.46.21     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             New Feature:  /           o  IPv6 Support for LPD and TELNETSYM   Q           The TCP/IP Services for OpenVMS software provides network printing ser- N           vices through the line printer/line printer daemon (LPR/LPD) 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 DCLP              command PRINT, and UNIX client users enter the lpr command. LPD canO              be configured for clusterwide availability, providing load balanc- N              ing and automatic failover for LPD-controlled print queues on the              OpenVMS host.  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              New Features:   #           o  NFS Client TCP Support   -           o  NFS Server Support for Integrity   &           o  NFS Symbolic Link Support  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.  ,                                            7           M           HP TCP/IP Services for OpenVMS Version 5.6             SPD 46.46.21     M           TCP/IP Services provides support for NFS Version 2 and Version 3 in A           the NFS server. The NFS client is limited to Version 2.   O           The NFS client is supported on OpenVMS I64 and OpenVMS Alpha systems. D           The NFS server is supported on OpenVMS Alpha systems only.  !           NFS supports IPv4 only.   M           The main benefit of NFS Version 3 is increased maximum file size-up N           to 1 terabyte for an OpenVMS file system and up to 4 gigabytes for aO           container file system. Performance gains may result from the improve- O           ments to file-size processing and the enhanced write performance that Q           allows the NFS server to acknowledge a write operation before the files M           are actually written to disk. Afterward, the server's response to a I           commit message confirms 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.             Mail Services   &           o  Secure IMAP (SSL support)  %           o  Secure POP (SSL support)   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 M           TCP/IP Services for OpenVMS implementation of SMTP uses the OpenVMS O           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  ,                                            8           M           HP TCP/IP Services for OpenVMS Version 5.6             SPD 46.46.21     2           o  IMAP Mail server (Alpha systems only)  R           Note: Secure IMAP and Secure POP require the use of the HP SSL for Open-           VMS software.              Network Services             New Features:              o  BIND 9 Resolver  !           o  DNS/BIND V9.3 Server   &           o  NTP Security Update (SSL)  O           With the following TCP/IP Services for OpenVMS management components, O           network and system managers can provide consistent, reliable, and ef- D           ficient 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- R              aged by a management station on the network. SNMP supports IPv4 only.  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 theO              internet. The BIND 9 server is based on the Internet Software Con- O              sortium's (ISC) BIND 9.2.1 implementation. It includes dynamic up- O              dates and BIND server cluster failover, which allows multiple BIND O              master servers to share a common database, thus providing both re- N              dundancy and a failover mechanism when one of the servers becomes              unavailable.   N           The BIND server is based on the ICS's BIND 9.2.1 implementation, and!           supports IPv4 and IPv6.   ,                                            9           M           HP TCP/IP Services for OpenVMS Version 5.6             SPD 46.46.21     O           The BIND resolver is based on the BIND 8.1.2 implementation. The BIND N           resolver supports communication over IPv4 only, but it is capable of5           querying for IPv6 addresses (AAAA records).   P           The BIND server and the BIND resolver are available on OpenVMS I64 and            OpenVMS Alpha systems.  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 TCP/IP Services for OpenVMS imple- P              mentation of the UNIX internet daemon (inetd). The auxiliary serverO              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.6             SPD 46.46.21                Security             New Feature:  .           o  SSH Upgrade with Kerberos Support  Q           The TCP/IP Services for OpenVMS product includes the secure shell (SSH) N           client and server, which provide secure login, remote command execu-O           tion, and file transfer. TCP/IP Services for OpenVMS 5.6 includes SSH P           support for Kerberos, the popular network authentication protocol fromM           the Massachusetts Institute of Technology. SSH password authentica- <           tion method has been enhanced to support Kerberos.  %           Performance and Scalability   N           The TCP/IP kernel has been modified to provide increased performance5           on symmetric multiprocessing (SMP) systems.   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  N           The 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.  -                                            11            M           HP TCP/IP Services for OpenVMS Version 5.6             SPD 46.46.21     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.     +           UNIX Network Management Utilities   4           o  TCPDUMP Version 3.8.3 for IPv4 and IPv6  O           The TCP/IP Services for OpenVMS product provides UNIX networking man- M           agement utilities for system managers who are experienced in manag- M           ing 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.  -                                            12            M           HP TCP/IP Services for OpenVMS Version 5.6             SPD 46.46.21     %           Error Message Documentation   N           The TCP/IP Services for OpenVMS product provides online help for er-O           ror messages for TCP/IP facilities and components. The information is H           included as part of the OpenVMS Help Message utility (MSGHLP).  3           Application Programming Interfaces (APIs)   &           o  libpcap for IPv4 and IPv6  M           The 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.           -                                            13            M           HP TCP/IP Services for OpenVMS Version 5.6             SPD 46.46.21     <           PATHWORKS, Advanced Server, and DECnet over TCP/IP  R           The TCP/IP Services for OpenVMS product includes the PATHWORKS IP (PWIP)O           driver and the PWIP ancillary control process (PWIP_ACP) for improved 1           Advanced Server and TCP/IP integration.   N           The PWIP driver allows communication between OpenVMS systems runningN           either Advanced Server for OpenVMS or PATHWORKS, and TCP/IP ServicesM           software, as well as personal computers running PATHWORKS 32 client P           software. It also enables the DECnet-over-TCP/IP feature, which is in-N           cluded with the DECnet-Plus for OpenVMS software. (For more informa-?           tion, see the DECnet-Plus for OpenVMS documentation.)   (           INSTALLATION AND CONFIGURATION  M           System managers install the 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  M           The TCP/IP Services for OpenVMS product supports central processing '           units (CPUs) running OpenVMS.   S           TCP/IP Services for OpenVMS Version 5.6 is supported on Integrity Servers Q           and Alpha servers that are listed in the OpenVMS Version 8.2-1 SPD (SPD O           82.35.02) and in the OpenVMS Version 8.3 SPD (SPD 82.35.08). (For VAX O           systems, use Version 5.3 of the TCP/IP Services for OpenVMS product.)   P           For a complete list of hardware products, see the Software Product De-L           scription (SPD) for the specific OpenVMS operating system release.              -                                            14            M           HP TCP/IP Services for OpenVMS Version 5.6             SPD 46.46.21     &           Required Network Controllers  O           The TCP/IP Services for OpenVMS software supports all network devices 5           listed in the OpenVMS Operating System SPD.   O           The TCP/IP Services for OpenVMS software can share an Ethernet inter- Q           face with other HP networking products such as DECnet-Plus for OpenVMS.              Memory Requirements   S           The minimum amount of memory required for the TCP/IP Services for OpenVMS Q           product is the same as the requirement for OpenVMS Version 8.2 and Ver- ,           sion 8.2-1. Refer to SPD 82.35.01.  !           Disk Space Requirements   M           The approximate amount of space required on the system disk to sup- M           port the TCP/IP for OpenVMS software under the client or server li- N           cense is 150,000 blocks. Actual sizes may vary depending on the sys-?           tem environment, configuration, and software options.              CLUSTER SUPPORT   M           The TCP/IP Services for OpenVMS product is fully supported when in- J           stalled on any valid and licensed OpenVMS Cluster configuration.             SOFTWARE REQUIREMENTS   M           To qualify for a software support contract, the TCP/IP Services for O           OpenVMS Version 5.6 product requires one of the following OpenVMS op- "           erating system versions:  $           o  OpenVMS I64 Version 8.3  &           o  OpenVMS I64 Version 8.2-1  $           o  OpenVMS I64 Version 8.2  &           o  OpenVMS Alpha Version 8.3  (           o  OpenVMS Alpha Version 8.2-1  -                                            15            M           HP TCP/IP Services for OpenVMS Version 5.6             SPD 46.46.21     &           o  OpenVMS Alpha Version 8.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)             DISTRIBUTION MEDIA  M           Media and documentation for the TCP/IP Services for OpenVMS product C           are available on the CD-ROM Software Library for OpenVMS.   Q           o  To order the DVD for OpenVMS I64, use order number BA322AA (HP Open- M              VMS I64 Foundation Operating Environment (FOE)). The TCP/IP Ser- >              vices for OpenVMS product is included in the FOE.  P           o  To order the CD-ROM Software Library for OpenVMS for Alpha systems,*              use order number QA-03XAA-H8.             ORDERING INFORMATION  )           TCP/IP Services for OpenVMS I64   M           With OpenVMS I64 Version 8.2 and higher, the operating system soft- N           ware, layered product software (including TCP/IP Services), and doc-P           umentation are delivered together in one media kit. One license is re-N           quired for each active processor. For license options and order num-N           bers, refer to SPD 82.35.01. For additional information about HP Op-M           erating Environments for OpenVMS Industry Standard 64 for Integrity $           Servers, see SPD 82.34.02.  2           TCP/IP Services for OpenVMS Alpha Server  +              Software Licenses: QL-0LXA*-** 0              Software Documentation: QA-0LXAA-GZ3              Software Product Services: QT-0LXA*-**       -                                            16            M           HP TCP/IP Services for OpenVMS Version 5.6             SPD 46.46.21     2           TCP/IP Services for OpenVMS Alpha Client  +              Software Licenses: QL-0M2A*-** 0              Software Documentation: QA-0LXAA-GZ3              Software Product Services: QT-0M2A*-**   :           TCP/IP Services for OpenVMS Alpha Client Upgrade  *              Software License: QL-0PHA*-**0              Software Documentation: QA-0LXAA-GZ3              Software Product Services: QT-0PHA*-**   M           The asterisk (*) denotes variant fields. For additional information O           about available licenses, services, and media, refer to the appropri- P           ate price book. This ordering information was valid at the time of re-M           lease. Contact your HP representative for current ordering informa-            tion.              SOFTWARE LICENSING  M           This software is furnished under license only. For more information P           about HP licensing terms and policies, contact your HP representative.  -           License Management Facility Support   M           The HP TCP/IP Services for OpenVMS product supports the OpenVMS Li- *           cense Management Facility (LMF).  R           For information about the License Management Facility, see SPD 82.35.01,/           or consult the OpenVMS documentation.              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.          -                                            17     P      M           HP TCP/IP Services for OpenVMS Version 5.6             SPD 46.46.21s    #           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.  Q           Confidential 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- M           nical Data for Commercial Items are licensed to the U.S. Government 5           under vendor's standard commercial license.n  O           The information contained herein is subject to change without notice.iO           The only warranties for HP products and services are set forth in thewN           express warranty statements accompanying such products and services.O           Nothing herein should be construed as constituting an additional war-)R           ranty. HP shall not be liable for technical or editorial errors or omis-!           sions contained herein.   :            2005 Hewlett-Packard Development Company, L.P.  P           Microsoft and Windows are U.S. registered trademarks of Microsoft Cor-           poration.n  ;           UNIX is a registered trademark of The Open Group.e                            -                                            18            M           HP TCP/IP Services for OpenVMS Version 5.6             SPD 46.46.21                                                                                       -                                            19 