[ PROTOCOLS:OSDIR-8-88.TXT ]                           [ AM, 4/90 ]


                    ASSISTANT SECRETARY OF DEFENSE

                       WASINGTON, DC 20301-3040



						August 26, 1988

MEMORANDUM FOR SECRETARIES OF THE MILITARY DEPARTMENTS
	       CHAIRMAN, JOINT CHIEFS OF STAFF
	       DIRECTORS OF THE DEFENSE AGENCIES

SUBJECT:  Conformance Testing of Military Standard Data
	  Communications Protocol Implementations

	This memorandum establishes a conformance testing policy to be used
for the acquisition of future implementations of military standard data com-
munications protocols by the Military Services and Defense Agencies.  This
policy mandates that specific tests be conducted for each software version
and/or hardware type.  Testing provides a means of determining conformance
to standards and is intended to significantly increase the probability of
interoperation in a multi-vendor environment.  This policy specifically
applies to MIL-STDs 1777, 1778, 1780, 1781 and 1782.  Implementations of
these protocols must be tested by a National Bureau of Standards (NBS)
accredited laboratory prior to first operational use on any DoD network.

	The conformance testing requirement is mandatory for all contracts
executed after 1 June 1989.  A Qualified Products list will be established
and maintained by the Defense Communications Agency.  For a product to be
placed on the Qualified Products List, acceptable test results must be 
presented to DCA from an accredited laboratory which is independent of the 
manufacturer.  The modification of a Qualified Product will require retesting
by an accredited laboratory prior to operational use.

	A waiver of this requirement may be granted in instances where it can
be clearly demonstrated that there are significant performance or cost advant-
ages to be gained, or when the overall interests of the Department of 
Defense are best served by granting a waiver.  Consideration will be given
to waiving this testing requirement in cases of modifications to existing
contracts or add-ons to existing programs.  In instances where testing of
products interferes with established DoD security requirements, consideration
will be given to an alternative testing environment.  Requests for waiver
from this testing requirement should be forwarded to Defense Communications
Agency, Code B100, Washington, DC  20305-2000.

	Although conformance testing is mandatory only for future acquisitions,
it is recommended that existing implementations of the MIL-STD protocols be
tested to determine instances of nonconformance to the standards.  In the
event that such testing identifies nonconformance, the appropriate procure-
ment office can determine where modifications may be prudently pursued.

	With the adoption of the Open Systems Interconnection (OSI) protocols
as co-standards to the above cited MIL-STD protocols, conformance of vendor
implementations to protocol standards becomes paramount if proposed solutions
such as dual DoD/OSI protocol hosts and dual DoD/OSI applications layer
gateways are to effectively allow interchange between the two protocol suites.
The establishment of DoD policy requiring conformance testing for DoD 
protocol implementations is a positive step towards a successful transition
to the OSI protocol suite.  OSI protocol suite implementations will also be
required to successfully complete conformance testing once OSI conformance
test capabilities are fully developed and implemented.  NBS is addressing
this issue and will be establishing a conformance testing policy as a 
Federal Information Processing Standard (FIPS).  The NBS policy will apply 
to the OSI protocols covered by the U.S. Government Open Systems Intercon-
nection Profile (GOSIP).  The DoD and OSI protocol suite conformance test
capabilities will provide the Military Services and Defense Agencies with
important assurances of product conformance to specifications.

					Gordon A. Smith