# JTA SECTION 3 - INFORMATION TRANSFER STANDARDS

DATE REVISED: 22 AUGUST 1996

SECTION 3 INFORMATION TRANSFER STANDARDS

- 3.1.1 Purpose
- 3.1.2 Scope
- 3.1.3 Background
- 3.2 MANDATES
- 3.2.1 End System Standards
- 3.2.1.1 Host Standards
- 3.2.1.1.1 Application Support Services
- 3.2.1.1.2 Transport Services
- 3.2.1.2 Video Teleconferencing (VTC) Standards
- 3.2.1.3 Facsimile Standards
- 3.2.1.3.1 Analog Facsimile Standard
- 3.2.1.3.2 Digital Facsimile Standards
- 3.2.1.4 Secondary Imagery Dissemination Standards
- 3.2.2 Network Standards
- 3.2.2.1 Router Standards
- 3.2.2.1.1 Internet Protocol (IP)
- 3.2.2.1.2 IP Routing
- 3.2.2.2 Subnetworks
- 3.2.2.2.1 Local Area Network (LAN)
- 3.2.2.2.2 Point to Point Standards
- 3.2.2.2.3 Combat Net Radio Networking
- 3.2.2.2.4 Integrated Services Digital Network (ISDN)
- 3.2.2.2.5 Asynchronous Transfer Mode (ATM)
- 3.2.3 Transmission Media
- 3.2.3.1 Military Satellite Communications (MILSATCOM)
- 3.2.3.1.1 Ultra High Frequency (UHF) Satellite Terminal Standards
- 3.2.3.1.2 Super High Frequency (SHF) Satellite Terminal Standards
- 3.2.3.1.3 Extremely High Frequency (EHF) Satellite Payload and Terminal Standards
- 3.2.3.2 Radio Communications
- 3.2.3.2.1 High Frequency (HF)
- 3.2.3.2.2 Very High Frequency (VHF)
- 3.2.3.2.3 Ultra High Frequency (UHF)
- 3.2.3.2.4 Super High Frequency (SHF)
- 3.2.3.2.5 JTIDS/MIDS Transmission Media
- 3.2.3.3 SONET Transmission Facilities
- 3.3 EMERGING STANDARDS
- 3.3.1 Information Transfer Standards
- 3.3.2 End System Standards
- 3.3.2.1 Internet Standards
- 3.3.2.2 Video Teleconferencing (VTC) Standards
- 3.3.2.3 Global Positioning System (GPS)
- 3.3.3 Network Access Protocols
- 3.3.3.1 Network Access Protocols
- 3.3.3.2 Link 22 Transmission Standards
- 3.3.4 Video Teleconferencing (VTC) Standards
- 3.3.4 Military Satellite Communications (MILSATCOM)

# SECTION 3 INFORMATION TRANSFER STANDARDS

## 3.1 INTRODUCTION

### 3.1.1 Purpose

Information transfer standards and profiles are described in this section. These standards promote seamless communications and information transfer interoperability for DoD systems.

### 3.1.2 Scope

This section identifies the interface standards that are required for interoperability between and among Command, Control, Communications, Computers, and Intelligence (C4I) systems, supporting access for data, facsimile, video, imagery, and multimedia systems. Also identified are the standards for internetworking between different subnetworks. Transmission media standards for Synchronous Optical Network (SONET) and radio links are identified. Finally, emerging technologies that should be monitored, for future extension of information transfer capabilities, are identified. This section includes the Communications Services depicted in the TRM, Figure 2-1. Security standards are addressed in Section 6.2.3.

### 3.1.3 Background

The standards herein are drawn from widely accepted commercial standards when they meet DoD requirements. Where necessary for interoperability, profiles of commercial standards are used. Military standards are mandated only when suitable commercial standards are not available. For example, the Joint Technical Architecture (JTA) makes use of the open-systems architecture used by the Internet and the Defense Information Systems Network (DISN). These networks provide for communications interoperability between end systems that are on different communications subnetworks. System components are categorized here as hosts, subnetworks, and routers. Hosts are computers that generally execute application programs on behalf of users and share information with other hosts via networks. Networks may be relatively simple (e.g., point-to-point links) or have complex internal structures (e.g., network of packet switches). Routers interconnect two or more subnetworks and forward packets across subnetwork boundaries. Routers are distinct from hosts in that they are normally not the destination of data traffic.

## 3.2 MANDATES

This subsection identifies the mandatory standards, profiles, and practices for information transfer. Each mandated standard or practice is clearly identified on a separate line, and includes a formal reference that can be included within Requests for Proposals (RFP) or Statements of Work (SOW). Appendix B contains a table that summarizes the mandated standards from this section, as well as providing information on how to obtain the standards. The World Wide Web (WWW) version of Appendix B contains a link to the standard or to the organization that maintains the standard when one is available.

### 3.2.1 End System Standards

This subsection addresses standards for the following types of end systems: host, Video Teleconferencing (VTC), facsimile, and secondary imagery dissemination.

#### 3.2.1.1 Host Standards

Internet Architecture Board (IAB) Standard-3 is an umbrella standard that references other documents and corrects errors in some of the referenced documents. Standard-3 also adds additional discussion and guidance for implementors. The following standard is mandated:

- IAB Standard 3/RFC-1122/RFC-1123, Host Requirements, October 1989.

##### 3.2.1.1.1 Application Support Services

###### 3.2.1.1.1.1 Electronic Mail

The standard for electronic mail is the Defense Message System (DMS)'s X.400-based suite of military messaging standards as defined in Allied Communication Publication (ACP) 123 U.S. Supplement No. 1. The U.S. Supplement annexes contain standards profiles for the definition of the DMS "Business Class Messaging" (P772) capability and the Message Security Protocol (MSP). See Section 6 for security standards. Since X.400 is not an internet standard, see 3.2.1.1.2.2 for operation over Internet Protocol (IP) based networks. The following standard is mandated:

- ACP 123 U.S. Supplement No. 1, Common Messaging Strategy and Procedures, November 1995.

###### 3.2.1.1.1.2 Directory Services

X.500 and Domain Name System (DNS) provide complimentary directory services. The X.500 protocol provides individual and organizational directory services and is mandated for use with DMS. The DNS provides computer addressing services and is mandated for Internet Protocol (IP)-based services.

###### 3.2.1.1.1.2.1 X.500 Directory Services

International Telecommunications Union (ITU) X.500 provides directory services that may be used by users or host applications to locate other users and resources on the network. X.500 also provides security services used by DMS-compliant X.400 implementations. See section 6 for security standards. Since X.500 is not an internet standard, see 3.2.1.1.2.2 for operation over Internet Protocol (IP) based networks. The following standard is mandated:

- ITU-T X.500, The Directory - Overview of Concepts, Models, and Services - Data Communication Networks Directory, 1993.

###### 3.2.1.1.1.2.2 Domain Name System (DNS)

The DNS provides the service of translating between host names and IP addresses. DNS uses Transmission Control Protocol (TCP)/User Datagram Protocol (UDP) as a transport service when used in conjunction with other services. The following standard is mandated:

- IAB Standard 13/RFC-1034/RFC-1035, Domain Name System, November 1987.

###### 3.2.1.1.1.3 File Transfer

Basic file transfer shall be accomplished using File Transfer Protocol (FTP). FTP provides a reliable, file transfer service for text or binary files. FTP uses TCP as a transport service. The following standard is mandated:

- IAB Standard 9/RFC-959, File Transfer Protocol, October 1985, with the following FTP commands mandated for reception: Store unique (STOU) and Abort (ABOR).

###### 3.2.1.1.1.4 Remote Terminal

Basic remote terminal services shall be accomplished using Telecommunications Network (TELNET). TELNET provides a virtual terminal capability that allows a user to "log on" to a remote system as though the user's terminal was directly connected to the remote system. The following standard is mandated:

- IAB Standard 8/RFC-854/RFC-855, TELNET Protocol, May 1983.

###### 3.2.1.1.1.5 Network Management

Network management provides the capability to manage designated network(s). This includes the capability to control the network's topology, dynamically segment the network into multiple logical domains, maintain network routing tables, monitor the network load, and make routing adjustments to optimize throughput. Network management also provides the capability to review and publish network addresses of network objects; monitor the status of network objects; start, restart, reconfigure, or terminate network objects; and detect loss of network objects in order to support automated fault recovery. Hosts shall implement the Simple Network Management Protocol (SNMP) set of network management protocols. The following standards are mandated:

- IAB Standard 15/RFC-1157, Simple Network Management Protocol (SNMP), May 1990
- IAB Standard 16/RFC-1155/RFC-1212, Structure of Management Information, May 1990
- IAB Standard 17/RFC-1213, Management Information Base, March 1991.

###### 3.2.1.1.1.6 Network Time

Network Time Protocol (NTP) provides the mechanisms to synchronize time and coordinate time distribution in a large, diverse internet. The following standard is mandated:

- RFC-1305, Network Time Protocol (V3), April 9, 1992.

###### 3.2.1.1.1.7 Bootstrap Protocol (BOOTP)

BOOTP assigns an IP address to workstations with no IP address. The following standards are mandated:

- RFC-951, Bootstrap Protocol, September 1, 1985
- RFC-1533, DHCP Options and BOOTP Vendor Extensions, October 8, 1993
- RFC-1542, Clarifications and Extensions for the Bootstrap Protocol, October 27, 1993.

###### 3.2.1.1.1.8 Dynamic Host Configuration Protocol (DHCP)

DHCP provides an extension of BOOTP to support the passing of configuration information to Internet hosts. DHCP consists of two parts, a protocol for delivering host-specific configuration parameters from a DHCP server to a host, and a mechanism for automatically allocating IP addresses to hosts. The following standard is mandated:

- RFC-1541, Dynamic Host Configuration Protocol, October 27, 1993.

###### 3.2.1.1.1.9 World Wide Web (WWW) Services

###### 3.2.1.1.1.9.1 Hypertext Transfer Protocol (HTTP)

HTTP is used for search and retrieval within the WWW. HTTP uses TCP as a transport service. The following standard is mandated:

- RFC-1945, Hypertext Transfer Protocol -- HTTP/1.0, May 17, 1996.

###### 3.2.1.1.1.9.2 Uniform Resource Locator (URL)

A URL specifies the location of and access methods for resources on an internet. The following standards are mandated:

- RFC-1738, Uniform Resource Locators, December 20, 1994
- RFC-1808, Relative Uniform Resource Locators, June 14, 1995.

###### 3.2.1.1.1.10 Connectionless Data Transfer

Variable Message Format (VMF) messages shall use a connectionless application layer. The following standard is mandated:

- MIL-STD-2045-47001, Connectionless Data Transfer Application Layer Standard, July 27, 1995.

##### 3.2.1.1.2 Transport Services

The transport services provide host-to-host communications capability for application support services. The following sections define the requirements for this service.

###### 3.2.1.1.2.1 Transmission Control Protocol (TCP)/User Datagram Protocol (UDP) over Internet Protocol (IP)

###### 3.2.1.1.2.1.1 Transmission Control Protocol (TCP)

TCP provides a reliable connection-oriented transport service. The following standard is mandated:

- IAB Standard 7/RFC-793, Transmission Control Protocol, September 1981. In addition, TCP shall implement the PUSH flag and the Nagle Algorithm, as defined in IAB Standard 3.

###### 3.2.1.1.2.1.2 User Datagram Protocol (UDP)

UDP provides an unacknowledged, connectionless, datagram transport service. The following standard is mandated:

- IAB Standard 6/RFC-768, User Datagram Protocol, August 1980.

###### 3.2.1.1.2.1.3 Internet Protocol (IP)

IP is a basic connectionless datagram service. All protocols within the IP suite use the IP datagram as the basic data transport mechanism. Two other protocols are considered integral parts of IP: the Internet Control Message Protocol (ICMP) and the Internet Group Management Protocol (IGMP). ICMP is used to provide error reporting, flow control, and route redirection. IGMP provides multicast extensions for hosts to report their group membership to multicast routers. The following standard is mandated:

- IAB Standard 5/RFC-791/RFC-950/RFC-919/RFC-922/RFC-792/RFC-1112, Internet Protocol, September 1981. In addition, all implementations of IP must pass received Type-of-Service (TOS) values up to the transport layer. Furthermore, for hosts that transmit or receive multiaddressed datagrams over Combat Net Radio (CNR), the multiaddressed IP option field must be used. This is a military-unique option that is defined in MIL-STD-2045-14502-1A.

###### 3.2.1.1.2.2 Open Systems Interconnection (OSI)/Internet Interworking Protocol

This protocol provides the interworking between Transport Protocol Class 0 (TP0) and TCP transport service necessary for OSI applications to operate over IP-based networks. The following standard is mandated:

- IAB Standard 35/RFC 1006, ISO Transport Service on top of the TCP, May 1978.

#### 3.2.1.2 Video Teleconferencing (VTC) Standards

VTC terminals operating at data rates of 56-1920 kbps shall comply with the Industry Profile for Video Teleconferencing, VTC001. The purpose of the profile is to provide interoperability between VTC terminal equipment, both in point-to-point and multipoint configurations. This profile is based on the ITU-T H.320 and T.120 series of recommendations. VTC terminals operating at low bit rates (9.6-28.8 kbps) shall comply with ITU-T H.324. The following standards are mandated:

- VTC001, Industry Profile for Video Teleconferencing, Revision 1, April 25, 1995
- ITU-T H.324, Terminal for Low Bit Rate Multimedia Communications, March 19, 1996.

#### 3.2.1.3 Facsimile Standards

##### 3.2.1.3.1 Analog Facsimile Standard

Facsimile requirements for analog output shall comply with ITU-T Group 3 specifications. The following standards are mandated:

- TIA/EIA-465-A, Group 3 Facsimile Apparatus for Document Transmission, March 21, 1995
- TIA/EIA-466, Procedures for Document Facsimile Transmission, May 1981.

##### 3.2.1.3.2 Digital Facsimile Standard

Digital facsimile terminals operating in tactical, high Bit Error Rate (BER) environments shall implement digital facsimile equipment standards for Type I and/or Type II mode. Also, facsimile transmissions requiring encryption, or interoperability with NATO countries, shall use the digital facsimile standard. The following standard is mandated:

- MIL-STD 188-161D, Interoperability and Performance Standards for Digital Facsimile Equipment, January 10, 1995.

#### 3.2.1.4 Secondary Imagery Dissemination Standards

The Tactical Communications Protocol 2 (TACO2) is the communications component of the National Imagery Transmission Standard (NITFS) suite of standards used to disseminate secondary imagery. TACO2 shall be used over point-to-point tactical data links in high BER disadvantaged communications environments. TACO2 is used to transfer secondary imagery and related products where JTA transfer protocols in section 3.2.1.1.2 fail. TACO2 only applies to users having simplex and half duplex links as their only means of communications. MIL-HDBK-1300A, NITFS, provides guidance to implement various Technical Interface Specifications (TIS) to connect the TACO2 host to specific cryptographic equipment. The following standard is mandated:

- MIL-STD-2045-44500, National Imagery Transmission Format Standard (NITFS) Tactical Communications Protocol 2 (TACO2), June 18, 1993.

### 3.2.2 Network Standards

#### 3.2.2.1 Router Standards

Routers are used to interconnect various subnetworks and end systems. Protocols necessary to provide this service are specified below. RFC-1812 is an umbrella standard that references other documents and corrects errors in some of the reference documents. In addition, some of the standards that were mandated for hosts in Section 3.2.1.1 also apply to routers. The following standards are mandated:

- RFC-1812, Requirements for IP Version 4 Routers, June 22, 1995
- IAB Standard 6/RFC-768, User Datagram Protocol, August 1980
- IAB Standard 7/RFC-793, Transmission Control Protocol, September 1981
- IAB Standard 8/RFC-854/RFC-855, TELNET Protocol, May 1983
- IAB Standard 13/RFC-1034/RFC-1035, Domain Name System, November 1987
- IAB Standard 15/RFC-1157, Simple Network Management Protocol, May 1990
- IAB Standard 16//RFC-1155/RFC-1212, Structure of Management Information, May 1990
- IAB Standard 17/RFC-1213, Management Information Base, March 1991
- RFC-951, Bootstrap Protocol, September 1, 1985
- RFC-1533, DHCP Options and BOOTP Vendor Extensions, October 8, 1993

- RFC-1541, DHCP, October 27, 1993
- RFC-1542, Clarifications and Extensions for the Bootstrap Protocol, October 27, 1993
- IAB Standard 33/RFC-1350, Trivial FTP (TFTP), July 1992, to be used for initialization only.

Security requirements are addressed in Section 6.

##### 3.2.2.1.1 Internet Protocol (IP)

IP is a basic connectionless datagram service. All protocols within the IP suite use the IP datagram as the basic data transport mechanism. IP was designed to interconnect heterogeneous networks and operates over a wide variety of networks. Two other protocols are considered integral parts of IP, the Internet Control Message Protocol (ICMP) and the Internet Group Management Protocol (IGMP). ICMP is used to provide error reporting, flow control, and route redirection. IGMP provides multicast extensions for hosts to report their group membership to multicast routers. The following standard is mandated:

- IAB Standard 5/RFC-791/RFC-950/RFC-919/RFC-922/RFC-792/RFC-1112, Internet Protocol, September 1981.

In addition, all implementations of IP routers that transmit or receive multiaddressed datagrams over Combat Net Radio (CNR), must use the multiaddressed IP option field. This is a military unique option that is defined in MIL-STD-2045-14502-1A.

##### 3.2.2.1.2 IP Routing

Routers exchange connectivity information with other routers to determine network connectivity and adapt to changes in the network. This enables routers to determine, on a dynamic basis, where to send IP packets.

###### 3.2.2.1.2.1 Interior Routers

Routes within an autonomous system are considered local routes that are administered and advertised locally by means of an interior gateway protocol. Routers shall use the Open Shortest Path First (OSPF) V2 protocol for unicast interior gateway routing and Multicast OSPF (MOSPF) for multicast interior gateway routing. The following standards are mandated:

- RFC-1583, Open Shortest Path First Routing Version 2, March 23, 1994, for unicast routing
- RFC-1584, Multicast Extensions to OSPF, March 24, 1994, for multicast routing.

###### 3.2.2.1.2.2. Exterior Routers

Exterior gateway protocols are used to specify routes between autonomous systems. Routers shall use the Border Gateway Protocol 4 (BGP-4) for exterior gateway routing. BGP-4 uses TCP as a transport service. The following standards are mandated:

- RFC-1771, Border Gateway Protocol 4, March 21, 1995
- RFC-1772, Application of BGP-4 In the Internet, March 21, 1995.

#### 3.2.2.2 Subnetworks

##### 3.2.2.2.1 Local Area Network (LAN) Access

While no specific LAN technology is mandated, the following is required for interoperability in a joint environment. This requires provision for a LAN interconnection. Ethernet, the common implementation of Carrier Sense Multiple Access with Collision Detection (CSMA/CD), is the most common LAN technology in use with TCP/IP. The hosts use a CSMA/CD scheme to control access to the transmission medium. The following standards are mandated as the minimum LAN requirements for operation in a joint task force:

- ISO/IEC 8802-3:1993, Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications, 10BaseT Medium-Access Unit (MAU)
- IAB-Standard 41/RFC-894, Standard for the Transmission of IP Datagrams Over Ethernet Networks, April 1984
- IAB Standard 37/RFC-826, An Ethernet Address Resolution Protocol, November 1982.

##### 3.2.2.2.2 Point to Point Standards

For full duplex, synchronous or asynchronous, point-to-point communication, the following standards are mandated:

- IAB Standard 51/RFC-1661/RFC-1662, Point-to-Point Protocol (PPP), July 1994
- RFC-1332, PPP Internet Protocol Control Protocol (IPCP), May 26, 1992
- RFC-1333, PPP Link Quality Monitoring, May 26, 1992
- RFC-1334, PPP Authentication Protocols, October 20, 1992
- RFC-1570, PPP Link Control Protocol (LCP) Extensions, January 11, 1994.

The serial line interface shall comply with one of the following mandated standards:

- EIA 232E, Interface Between Data Terminal Equipment and Data Circuit Terminating Equipment Employing Serial Binary Data Interchange, July 1991
- EIA 449, General Purpose 37-Position and 9-Position Interface for Data Terminal Equipment and Data Circuit Terminating Equipment Employing Serial Binary Data Interchange, February 1980. (This calls out EIA 422B and 423B.)
- EIA 530A, High Speed 25-Position Interface for Data Terminal Equipment and Data Circuit Terminating Equipment, June 1992, Including Alternate 26-Position Connector, 1992 (This calls out EIA 422B and 423B.).

##### 3.2.2.2.3 Combat Net Radio (CNR) Networking

CNRs are a family of radios that allow voice or data communications for mobile users. These radios provide a half-duplex, broadcast transmission media with potentially high BERs. The method by which IP packets are encapsulated and transmitted is specified in MIL-STD-188-220A. With the exception of High Frequency (HF) networks, MIL-STD-188-220A shall be used as the standard communications net access protocol for CNR networks. The following standard is mandated:

- MIL-STD-188-220A, Interoperability Standard for Digital Message Transfer Device (DMTD) Subsystems, July 27, 1995.

##### 3.2.2.2.4 Integrated Services Digital Network (ISDN)

ISDN is an international standard used to support integrated voice and data over standard twisted-pair wire. ISDN defines a Basic Rate Interface (BRI) and Primary Rate Interface (PRI) to provide digital access to ISDN networks. These interfaces support both circuit-switched and packet-switched services. The following standards are mandated:

For BRI physical layer,

- ANSI T1.601, Telecommunications - Integrated Services Digital Network (ISDN) - Basic Access Interface for Use on Metallic loops for Application on the Network Side of the NT (Layer 1 Specification), 1992.

For PRI physical layer,

- ANSI T1.408, Telecommunications - Integrated Services Digital Network (ISDN) - Primary Rate - Customer Installation Metallic Interfaces (Layer 1 Specification), 1990.

For BRI and PRI data link layer,

- ITU-T Q.921, ISDN User-Network Interface - Data Link Layer Specification - Digital Subscriber Signaling System No. 1, 1993.

For signaling at the user-network interface,

- ITU-T Q.931, ISDN User-Network Interface Layer 3 Specification for basic Call Control - Digital Subscriber Signaling System No. 1(DSS 1), Network Layer, User-Network Management, 1989.

For addressing,

- ITU-T E.164, Numbering Plan for the ISDN Era, 1991
- DCAC 370-175-13, Defense Switched Network System Interface Criteria, section titled Worldwide Numbering and Dialing Plan (WNDP), September 1993.

For transmitting IP packets when using ISDN packet-switched services,

- RFC-1356, Multiprotocol Interconnect on X.25 and ISDN in the Packet Mode, August 6, 1992.

For transmitting IP packets using Point-to-Point Protocol (PPP) over ISDN,

- RFC-1618, PPP over ISDN, May 13, 1994.

The citation of applicable ANSI standards for ISDN does not assure C4I interoperability in regions outside North America where standards for these services differ. The JTA recognizes that this is a critical area affecting interoperability but does not recommend specific solutions in this version.

##### 3.2.2.2.5 Asynchronous Transfer Mode (ATM)

ATM is a high-speed switching technology that takes advantage of low BER transmission facilities to accommodate intelligent multiplexing of voice, data, video, imagery, and composite inputs over high-speed trunks. The network access protocols to connect user equipment to ATM switches are defined in the ATM Forum's User-Network Interface (UNI) Specification.

The protocol layers consist of an ATM Adaptation Layer (AAL), the ATM layer, and a physical layer. The role of AAL is to divide the variable-length data units into 48-octet units to pass to the ATM layer. AAL1 shall be used to support constant bit rate service, which is sensitive to cell delay, but not cell loss. AAL5 shall be used to support variable bit rate service. The following standards are mandated:

- ATM Forum's UNI Specification V 3.1, User-Network Interface, September 1994
- ANSI T1.630 ATM Adaptation Layer for Constant Bit Rate Services Functionality and Specification, 1993
- ANSI T1.635 ATM Adaptation Layer Type 5 Common Part Functions and Specifications, 1994, which adopts ITU-T I.363, section 6
- RFC-1577, Classical IP and Address Resolution Protocol (ARP) over ATM, January 20, 1994.

### 3.2.3 Transmission Media

#### 3.2.3.1 Military Satellite Communications (MILSATCOM)

MILSATCOM systems include those systems owned or leased and operated by the DoD and those commercial SATCOM services used by the DoD. The basic elements of satellite communications consists of a space segment, control segment, and a terminal segment (air, ship, ground, etc.). An implementation of a typical satellite link will require the use of satellite terminals, user communications extension, and the use of military or commercial satellite resources.

##### 3.2.3.1.1 Ultra High Frequency (UHF) Satellite Terminal Standards

###### 3.2.3.1.1.1 5- and 25-kHz Service

For 5-kHz or 25-kHz single channel access service supporting the transmission of either voice or data, the following standard is mandated:

- MIL-STD-188-181, Interoperability Standard for Dedicated 5-kHz and 25-kHz UHF Satellite Communications, 18 September 1992.

###### 3.2.3.1.1.2 5-kHz Demand Assigned Multiple Access (DAMA) Service

For 5-kHz DAMA service, supporting the transmission of data at 75 - 2400 bps and digitized voice at 2400 bps, the following standard is mandated:

- MIL-STD-188-182, Interoperability Standard for 5 kHz UHF DAMA Terminal Waveform, 18 September 1992.

###### 3.2.3.1.1.3 25-kHz Time Division Multiple Access (TDMA)/Demand Assigned Multiple Access (DAMA) Service

For 25-kHz TDMA/DAMA service, supporting the transmission of voice 2400, 4800, or 16000 bps and data at rates of 75 - 16000 bps, the following standard is mandated:

- MIL-STD-188-183, Interoperability Standard for 25 kHz UHF/TDMA/DAMA Terminal Waveform, 18 September 1992.

###### 3.2.3.1.1.4 Data Control Waveform

For interoperable waveform for data controllers used to operate over single access 5 kHz and 25 kHz UHF SATCOM channels, the following standard (a robust link protocol that can transfer error free data efficiently and effectively over channels that have high error rates) is mandated:

- MIL-STD-188-184, Interoperability and Performance Standard for the Data Control Waveform, 20 August 1993.

##### 3.2.3.1.2 Super High Frequency (SHF) Satellite Terminal Standards

###### 3.2.3.1.2.1 Earth Terminals

For minimum mandatory Radio Frequency (RF) and Intermediate Frequency (IF) requirements to ensure interoperability of SATCOM earth terminals operating over C, X, and Ku- band channels, the following standard is mandated:

- MIL-STD-188-164, Interoperability and Performance Standards for C-Band, X-Band, and Ku-Band SHF Satellite Communications Earth Terminals, 13 January 1995.

###### 3.2.3.1.2.2 Phase Shift Keying (PSK) Modems

For minimum mandatory requirements to ensure interoperability of PSK modems operating in Frequency Division Multiple Access mode, the following standard is mandated:

- MIL-STD-188-165, Interoperability and Performance Standards for SHF Satellite Communications PSK Modems (Frequency Division Multiple Access (FDMA) Operations), January 13, 1995.

##### 3.2.3.1.3 Extremely High Frequency (EHF) Satellite Payload and Terminal Standards

###### 3.2.3.1.3.1 Low Data Rate (LDR)

For waveform, signal processing, and protocol requirements for acquisition, access control, and communications for low data rate (75 - 2400 bps) EHF satellite data links, the following standard is mandated:

- MIL-STD-1582, EHF LDR Uplinks and Downlinks, December 10, 1992.

###### 3.2.3.1.3.2 Medium Data Rate (MDR)

For waveform, signal processing, and protocol requirements for acquisition, access control, and communications for medium data rate (4.8 kbps - 1.544 Mbits/s) EHF satellite data links, the following standard is mandated:

- MIL-STD-188-136, EHF MDR Uplinks and Downlinks, August 26, 1995.

#### 3.2.3.2 Radio Communications

##### 3.2.3.2.1 High Frequency (HF)

###### 3.2.3.2.1.1 Automated Link Establishment (ALE)

For both ALE and radio subsystem requirements operating in the HF bands, the following standard is mandated:

- MIL-STD-188-141A, Medium and High Frequency Radio Equipment Standard, September 10, 1993.

###### 3.2.3.2.1.2 Anti-jamming Capability

For anti-jamming capabilities for HF radio equipment, the following standard is mandated:

- MIL-STD-188-148, Interoperability Standard Anti-Jam Communications (2-30 Mhz), April 13, 1992.

###### 3.2.3.2.1.3 Data Modems

For HF data modem interfaces, the following standard is mandated:

- MIL-STD-188-110A, Data Modems, Interoperability and Performance Standards, September 30, 1991.

###### 3.2.3.2.2 Very High Frequency (VHF)

For radio subsystem requirements operating in the VHF frequency bands, the following standard is mandated:

- MIL-STD-188-242, Tactical Single Channel (VHF) Radio Equipment, June 20, 1985.

###### 3.2.3.2.3 Ultra High Frequency (UHF)

For radio subsystem requirements operating in the UHF frequency bands, the following standard is mandated:

- MIL-STD-188-243, Tactical Single Channel (UHF) Radio Communications, March 15, 1989.

###### 3.2.3.2.4 Super High Frequency (SHF)

For radio subsystem requirements operating in the SHF frequency bands, the following standard is mandated:

- MIL-STD-188-145, Digital Line-of-Sight (LOS) Microwave Radio Equipment, July 28, 1992.

##### 3.2.3.2.5 JTIDS/MIDS Transmission Media

For communicating with the JTIDS/MIDS radios the following standards are mandated:

- JTIDS System Segment Specification (Class 2 Terminal)-
- STANAG 4175, Edition 1, 29 August 1991 - Technical Characteristics of the Multifunctional Information Distribution System (MIDS)

#### 3.2.3.3 Synchronous Optical Network (SONET) Transmission Facilities

The Synchronous Optical Network (SONET) is a telecommunications transmission standard for use over fiber-optic cable. SONET is the North American subset of the ITU standardized interfaces, and includes a hierarchical multiple structure, optical parameters, and service mapping. The following standards are mandated:

- ANSI T1.105, Telecommunications - Synchronous Optical Network (SONET) - Basic Description Including Multiplex Structure, Rates, and Formats (ATIS) (Revision and Consolidation of ANSI T1.105-1991 and ANSI T1.105A-1991), 1995
- ANSI T1.107 Digital Hierarchy - Formats Specifications, 1995
- ANSI T1.117, Digital Hierarchy - Optical Interface Specifications (SONET) (Single Mode - Short Reach), 1991.

The citation of applicable ANSI standards for SONET does not assure C4I interoperability in regions outside North America where standards for these services differ. The JTA recognizes that this is a critical area affecting interoperability but does not recommend specific solutions in this version.

## 3.3 EMERGING STANDARDS

The standards listed in this subsection are expected to be elevated to mandatory status when implementations of the standards mature.

### 3.3.1 Information Transfer Standards

Commercial communications standards and products will evolve over time. The JTA must evolve, as well, to benefit from these standards and products. The purpose of this section is to provide notice of those standards that are not yet a part of the JTA, but are expected to be adopted in the near future.

### 3.3.2 End System Standards

#### 3.3.2.1 Internet Standards

IP Next Generation/Version 6 (IPv6). IPv6 is being designed to provide better internetworking capabilities than are currently available within IP (Version 4). IPv6 will include support for:

1. Expanded addressing and routing capabilities
2. A simplified header format
3. Extension headers and options
4. Authentication and privacy
5. Autoconfiguration
6. Simple and flexible transition to IPv6
7. Increased quality of service capabilities.

IP Version 6 is described in RFC-1883, IPv6 Specification, RFC-1884, IPv6 Addressing Architecture: RFC-1885, ICMPv6 for IPv6, and RFC-1886, DNS Extensions to support IPv6.

Mobile Host Protocol (MHP). The primary aim of MHP is to provide information reachability for the mobile host. The intent is that a mobile host should not have to perform any special actions because of host migration. A mobile IP protocol is currently available as an Internet draft, entitled IP Mobility Support.

### 3.3.2.2 Video Teleconferencing (VTC) Standards

There are two emerging VTC standards that support communications over different networks. ITU H.321 and ITU H.323 are draft recommendations that support VTC over ATM and Ethernet networks, respectively.

#### 3.3.2.3 Global Positioning System (GPS)

GPS User Equipment must employ Precise Position Service (PPS) user equipment incorporating both Selective Availability and Anti-Spoofing features to support combat operations. The GPS guidelines that are documented in ASD Command, Control, Communications, and Intelligence (C3I) Memorandum "Development, Procurement, and Employment of DoD Global Position System, User Equipment," dated 31 April 1992 must be followed. Specific standards are being researched at this time.

### 3.3.3 Network Standards

#### 3.3.3.1 Network Access Protocols

Wireless LAN. The IEEE 802.11 Committee is developing standards for wireless services across three transmission media: spread-spectrum radio; narrowband radio; and infrared energy. Wireless technology is useful in environments requiring mobility of the users or flexible network establishment and reconfiguration.

Fast Ethernet. For high speed requirements, 100 Mbits/s ethernet technology may be implemented in accordance with IEEE 802.3u. This standard supports auto-negotiation of the media speed, making it possible for dual-speed ethernet interfaces to run at either 10 or 100 Mbits/s automatically.

ATM-related Standards. The ATM Forum is developing Private Network-Network Interface (PN-NI) routing and signaling standards to support large, dynamic, multivendor ATM networks. PN-NI routing will automatically disseminate network topology and resource information to switches in the network, enabling quality-of-service sensitive routing. Using this information, PN-NI signaling will allow calls to traverse large, dynamic networks in a scalable fashion. LANs, such as Ethernet, can be emulated over ATM networks using ATM LAN Emulation, Version 1.0. This permits ATM networks to be deployed without disruption of end-system network protocols and applications.

Personal Communications Services (PCS). PCS will support both terminal mobility and personal mobility. Personal mobility allows users of telecommunication services to gain access to these services from any convenient terminal with which they choose to associate themselves. To support personal mobility, the network must be able to distinguish between terminal and personal identifiers; to keep track of current user-terminal associations, user locations, services authorized to the user, and service capabilities of the terminals. Personal mobility may be provided by either wireline or wireless terminals. Terminal mobility is based on wireless access to the public switched telephone networks (PSTN). Wireless access standards will govern the protocols and procedures for establishing connections among mobile terminals and between them and fixed terminals of a switched network (or mobile terminals of a different cellular system). IS-41, the current standard within the United States, provides this capability and is compatible with the existing signaling and numbering schemes used in the PSTN.

Mobile Cellular. Mobile cellular radio can be regarded as an early form of "personal communications service." It allows subscribers to place and receive telephone calls over the PSTN wherever cellular service is provided. Two methods for digital access have emerged, TDMA, and Code Division Multiple Access (CDMA). In North America the standards for TDMA and CDMA are IS-54 and IS-95. Both of these standards use IS-41 as the standard signaling protocol.

Future Public Land Mobile Telecommunications Systems (FPLMTS) standards. The ITU is now working on a third-generation standard for FPLMTS. The aim of this effort is to achieve better compatibility among the various cellular systems such that, by the beginning of the next century, universal global access supporting terminal mobility becomes a reality. The document now emerging from this effort shall be used as guidance for implementing global terminal mobility.

#### 3.3.3.2 Link 22 Transmission Standards

Link 22 Transmission media will be used to exchange Link 22 messages. Link 22 messages, comprised of F-Series formats, will be used for the exchange of maritime operational data between tactical data systems using line of sight (UHF) and beyond line of sight (HF) bands. The standard for Link 22 waveform is under development.

### 3.3.4 Military Satellite Communications (MILSATCOM)

Work is continuing on standards for MILSATCOM beyond the standards identified in section 3.2.3.1. The draft standards are:

1. MIL-STD-188-166 (Interface Standard, Interoperability and Performance of Non-Electronic Protective Measures (EPM) for SHF SATCOM Link Control Protocols and Messaging Standards)
2. MIL-STD-188-167 (Interface Standard, Message Format for SHF SATCOM Demand Assignment)
3. MIL-STD-188-168 (Interface Standard, Interoperability and Performance Standards for SHF Satellite Communications Mulitplexers and Demultiplexers)
4. MIL-STD-188-185 (Interface Standard, Interoperability of UHF MILSATCOM DAMA Control System).

Go to Section 4.