Specifies the type of connection required for this address set. 'udp' implies: - UDP client - Northrop Grumman's proprietary data encapsulation format for message delimiting, using a SYN octet (16h) followed by 2 octets of user data length (big endian), followed by user data: SYN(1) len(2) user data(n) 'tcp' implies: - TCP client - Northrop Grumman's proprietary data encapsulation format for message delimiting, using a SYN octet (16h) followed by 2 octets of user data length (big endian), followed by user data: SYN(1) len(2) user data(n) 'system-1' implies: - UDP - each autif socket is mapped to a (specified) IA - each IA/socket carries an alias source IP address - port numbering: - host destination port = base = remote port - source port = base + TA (converted TA) - encapsulation format: ip header (dstip = autifRemAddress, srcip = autifAliasAddress) udp header (dstport = autifRemotePort, srcport = autifRemotePort + ta) alc data (no header, ends with EOMx) 'continental' implies: - UDP client - each autif socket is mapped to a (specified) IA - each IA/socket carries an alias source IP address - port numbering: - host destination port = base = remote port - source port = base + ta (converted TA) - encapsulation format: ip header (dstip = autifRemAddress, srcip = autifAliasAddress) udp header (dstport = autifRemotePort, srcport = autifRemotePort + ta) header (autifLNIA(2) ta) alc data (ends with EOMx) 'dlsw' implies: - TCP dlsw client(2065) + TCP dlsw listener(2065) - 1 or 2 TCP sockets supporting the flow of DLSw traffic with the defined peer (autifRemAddress). - autifAliasAddress defines this DLSw peer source ip address. - Uses RFC1795 defined message encapsulation format. - TIGER always initiates the connection 'listener' implies: - TCP listener - creates a socket with autifLocalPort defining the 'well known port' for the listener. - A conditional accept is done on all incoming connect requests to verify the remote address. If autifRemAddress is defined as: 0.0.0.0 - a call from any source address is accepted, 'non-zero' - only a call from the specified address is accepted. - Northrop Grumman's proprietary data encapsulation format for message delimiting, using a SYN octet (16h) followed by 2 octets of user data length (big endian), followed by user data: SYN(1) len(2) user data(n). 'matip' implies: - TCP Client/Server depending upon the Mode of the MATIP module - MATIP header contains 4 bytes. The first is version field and is used as as MATIP sync. The 2nd is ignored by AUTIF. The 3rd and 4th is the length of this TCP message. 'ofep-sabre' implies: - TCP Client process for SABRE OFEP Encapsulation/Protocol. - the Load Balancer header is 3 long (a version field and a 2 byte length) - the OFEP header is 4 bytes long (a version field, 2 byte length and a control field. 'ofep-sabre-listener' implies: - TCP Listener process for SABRE OFEP Encapsulation/Protocol - used ONLY for testing purposes. - the Load Balancer header is 3 long (a version field and a 2 byte length) - the OFEP header is 4 bytes long (a version field, 2 byte length and a control field.