"Type of network service (CLNS/CONS/RFC1006)?" If you want to use Connectionless Network Service (CLNS), enter CLNS. If you want to use Connection Oriented Network Service (CONS), enter CONS. If you want to use RFC1006, enter RFC1006. o CLNS NETWORK SERVICE There are two forms of the CLNS network service. Both forms support only one class of transport protocol: class 4. 1. CLNS with Internet/ES-IS Any transport connection can use CLNS with Internet/ES- IS. The communicating end systems may be on the same subnetwork, or on different subnetworks. This network service is provided by the implementation of the ES-IS (end system to intermediate system) Internet routing protocols, which route packets from the end system to an intermediate system on the same subnetwork. The intermediate system will ensure that packets reach their final destination. Two end systems that implement ES-IS on the same subnetwork may communicate without an intervening intermediate system. 2. CLNS with Null Internet A transport connection may use CLNS with Null Internet only when the two end systems are on the same 802.3 LAN. This network service is provided by the inactive subset of the Internet protocol. No intermediate system is involved in the network connection. o CONS NETWORK SERVICE A transport connection can use CONS when the underlying network connection is an X.25 connection. This type of network service is provided by the X.25 software in the DECnet-Plus for OpenVMS product. CONS supports transport connections using any class of transport protocol (that is, class 0, class 2, or class 4). The underlying X.25 network connection can be: - A connection between two systems attached to an X.25 Packet Switching Data Network (PSDN), either directly or via an X.25 gateway - A point-to-point connection using the LAPB protocol as the data link protocol - A direct connection between two systems on the same IEEE 802.3 LAN, using the LLC2 protocol In each of these cases the two end systems are on the same subnetwork. o RFC1006 NETWORK SERVICE The network service type RFC1006 tells the OSI transport to run over the TCP/IP protocol stack. The network service type is specified in an OSI Transport template. When using DECnet applications over RFC1006 the OSI transport template osit$rfc1006 is used for the inbound connection. For outbound connections, the default template is used.