Summary

  • RFC 1039, published in January 1988, reprints a 2 July 1987 Defense Department memorandum. It made OSI message handling and file transfer, with their GOSIP foundations, experimental co-standards alongside comparable DoD protocols.
  • The memorandum assigned DCA an application-level interoperation plan and dated trial targets. A full promotion depended on formal GOSIP approval as a Federal Information Processing Standard; a sole mandatory OSI suite was planned for two years after that event, with legacy interoperation continuing through installed systems’ expected lives.

The word experimental is easy to skim past until a procurement officer has to sign something. In RFC 1039, the Defense Department put OSI message handling and file transfer on the same standards shelf as comparable DoD protocols. An agency could specify the newcomers in addition to the old suite, in its place, or as an optional alternative where the DoD applicability rules applied. This was real buying authority, issued with a trial badge.

The document appeared as an RFC in January 1988, but its engine is a memorandum dated 2 July 1987. It says the Government OSI Profile of 22 April had enough detail to acquire interoperable vendor implementations. That judgment changed the department’s March 1982 host-to-host protocol policy. The four comparable DoD standards are named by number: MIL-STDs 1777, 1778, 1780 and 1781. A standard can enter a purchasing catalog long before operators have learned every way it can disappoint them.

The memo spelled out the reason for probation. Operational experience with OSI was limited, as were the operational, testing and security arrangements defined in GOSIP. Services choosing it were told to evaluate those conditions and expect complications. That instruction had a practical owner: a buyer selecting a new stack had to carry its integration burden, rather than assuming that a standards label did the testing.

Promotion had a timetable, but the clock had a start button. Once GOSIP was formally approved as a Federal Information Processing Standard, OSI was intended to become a full co-standard. Two years after that, the plan made OSI the sole mandatory interoperable protocol suite. Even then, interoperation with DoD protocols was to continue for the expected life of systems using them. The paper imagined a new default with a long-running doorway back to existing machines. It did not include a completion report for either milestone.

The doorway was assigned to engineers, not rhetoric. The Defense Communications Agency, as DoD executive agent for protocol standards, was asked for an interoperation and transition plan by November 1987. Experimental application-level interoperation for message handling and file transfer was targeted for March 1988, followed by limited operational capability in January 1989. Those dates are tasks in the memorandum. A gateway between two application services still needs behavior, tests and somebody to operate it when one side speaks differently.

The organizational wiring is as revealing as the protocol wiring. DCA was to join the Corporation for Open Systems as the department’s representative; individual Services and agencies were told not to join directly, though they could participate as DCA’s agents. DCA also coordinated work in user, implementer, standards and NATO groups. The National Security Agency was assigned to align its Secure Data Network Systems work with GOSIP’s future security extensions. Early adopters were to share what their implementations actually did. The trial would collect evidence before a later directive filled in final details.

There is a comic image in a department giving a new protocol suite a probationary badge, a promotion plan and several committee meetings. The serious feature is the distribution of responsibility. Procurement permission came first. Application bridges, test environments, security work and legacy support all needed named owners. RFC 1039 captured a moment when the preferred future had been written down and the machines still had to be persuaded to go there.