CSP to DMS Addressing Component (CDAC)

The CDAC is a component of the Communications Support Processor (CSP) that facilitates messaging compatibility between the Defense Message System (DMS), AUTODIN, and the CSP backside systems. The CDAC was initially designed to support DSSCS and GENSER communications within the intelligence community, but the technology has been extended to support military operations and combat-support-unit domains as well. CDAC supports the conversion of both ACP 123 and ACP 120 format.

The current version of the CSP CDAC was developed for SUN Sparc or Ultra platforms running Solaris V2.6. The CDAC can be installed either as a co-resident process (with the Secure Messaging and Routing Terminal (SMART) application) on Solaris 2.6, 7, or 8 or on a separate server (in conjunction with a CSP system) as a stand-alone on Solaris 8.  Regardless of whether it is a co-resident process or it is installed on a separate server, the CDAC is plugged into CSP's powerful security message and format validation applications, message storage and recall functions, status displays, and security auditing features. Now that AUTODIN service has been terminated at many sites, the CSP still provides legacy systems with a messaging capability to DMS. The CSP, through the CDAC, provides this capability, even though the legacy systems are connected via standard network or serial protocols. 

Drawing of the CSP through CDAC

 

 

 

 

 

 

 

The CDAC converts AUTODIN- and DMS-formatted messages to the format required by the recipient system. For an AUTODIN-to-DMS transaction, the CDAC performs format conversion from AUTODIN DOI-103 and JANAP 128 formats to the DMS ACP 120 and 123 format. Because CSP already provides destination conversion from DOI-103M to DOI-103, and ACP-127 to JANAP 128, CDAC mapping for DOI-103M and ACP 127 to ACP 123 or ACP 120 is not necessary. When a DMS-to-AUTODIN transaction is required, X.400 messages are converted from ACP 123/120 to an intermediate, normalized template. The use of the normalized template significantly reduces the complexity of the conversion task. CSP already performs format conversion of messages to JANAP 128, DOI-103, ACP 127 and DOI-103M. Therefore, ACP 123/ACP 120 mapping to all AUTODIN formats is not necessary. Currently, text attachments to DMS messages are encapsulated into the messages processed through the CDAC and passed into the legacy network via CSP.  Binary attachments can be added via a configured option.

The CSP assures that the message is properly addressed for routing to the recipient. The CDAC will satisfy this requirement by converting addresses to the appropriate DMS or AUTODIN address. Directory System Agent (DSA) "lookups" are performed to:

The CSP can deliver a message to multiple destinations. The CSP Automatic Routing application will identify messages that require delivery to a DMS location. The message PLA(s) and Office Symbol(s) are "tagged" so that the CDAC will know which addresses in the "TO" and "INFO" lines of the message require DMS processing. The CDAC uses the "tagged" PLA and Office Symbol to determine the X.400 address via the assigned DMS DSA. Those messages that meet the routing criteria for DMS delivery are queued to the CDAC for transmission.

CDAC fully supports functional address symbol (FAS) codes/office symbols on messages originating from both AUTODIN and DMS. Processing of FAS codes takes place via information obtained from the PLA tree in the DMS DSA. Each PLA entry points to an associated organization that has sub-tree entries for FAS codes. Each FAS code entry contains the DMS X.400 address and public key certificate for that PLA and FAS code. In an AUTODIN-to-DMS transaction, CDAC uses this information to address and encrypt the resulting DMS X.400 message. The DMS-to-AUTODIN transaction is less complicated. The DMS message is addressed and encrypted for a specific CDAC (available from the DMS user's local DSA), with the PLA and FAS code included as a domain defined attribute (DDA). CDAC uses the DDA as the recipient's address for the resulting AUTODIN message.

Address problems that require resolution are sent to the CSP service clerk. This eliminates the overhead of maintaining separate CSP and CDAC service positions.

Message security, integrity, and accountability on the communication link between the CSP and the CDAC are ensured by using the Defense Intelligence Agency (DIA) full duplex message protocol (FDMP) and encryption using triple-data encryption standard (3DES).

Message security protocol (MSP) plays a key role in fulfilling the security requirements of the DCID. MSP offers proof of origin and protects the integrity of the messages using the Fortezza card and MSP software. MSP is used together with the Fortezza card to establish message security between AUTODIN and DMS components. Security services provided by MSP are:

By design, the CDAC may operate on a separate host that is remote from the CSP, or on the same host with SMART. Regardless of whether the CDAC is co-resident or located on a remote host, full-duplex communications are maintained using TCP/IP/FDMP between the CSP/SMART and CDAC. The CSP message interface (CMI) software is used to transmit and receive messages between the CSP and the CDAC. The use of CMI ensures that message integrity, security, and privacy are preserved on the communication link. The CSP utilizes its own FIFO queues between the CDAC and the CSP.

As many as five CDAC lines, each assigned to a separate Fortezza card, can be established for a single CDAC destination. Message-delivery responsibility is passed to DMS only when the message is processed and delivered to the MTA. Audit trail, status information, and operator notices are transmitted to the CSP for display and storage.

The communications between the CDAC and the DMS environment follow the X.400 standards. The CDAC utilizes a DMS compliant MTA (P1 protocol). A vendor product, Messaging Direct, provides the MTA and MTA access libraries.

The CDAC combined with CSP or SMART offers the classified messaging community a way to transition to the DMS architecture while commercial DMS products are being certified, integrated, and implemented.

Hardware/operating systems/software

Message format conversion

Communications protocols