Summary

  • The National Bureau of Standards circulated a proposed computer-based message format as RFC 806 in 1981 and issued FIPS Publication 98 on 27 January 1983. RFC 841 reproduced the federal standard for the ARPA research community. Its opening explicitly confined the RFC's standards role: the federal rule did not become an ARPA Internet standard by appearing in the series.
  • FIPS 98 standardized the message format at interfaces between covered federal message systems, while leaving internal storage, presentation and transfer protocols to each system. It set a 12-month trigger for new in-house development and a 24-month trigger for covered orders, with defined exemptions and a waiver decision by the Secretary of Commerce.

Picture a thick binder shuttling between two rooms. In the federal procurement office, it arrives with a calendar, a purchase order and someone authorized to say yes or no to a waiver. In the Internet research library, the same pages sit under an RFC number so engineers can read them. A busy librarian can shelve a rule; she cannot award a federal contract. The National Bureau of Standards gave its message-format specification precisely this double life. A proposed version reached readers as RFC 806 in September 1981. The issued FIPS Publication 98 appeared on 27 January 1983 and was circulated as RFC 841.

The note at the front of RFC 841 is unusually blunt. The RFC distribution made the document easily accessible to the ARPA research community. The document did not thereby specify a standard for the ARPA Internet. That sentence sorted two kinds of authority that an archive number can otherwise blur. The federal government could set conditions for covered purchases and in-house development. The RFC series could circulate the text. A copy on the second shelf did not carry the first desk's procurement jurisdiction into every networked mail program.

What did Washington actually standardize? Not every part of a mail service. FIPS 98 dealt with a message's interchange format at the interface between computer-based message systems, or CBMS. A message could pass from a system with one internal representation to another with a different one: the sender would convert to the shared format on departure, and the recipient would convert back on arrival. The standard specified fields and the data elements a receiving system had to locate and process. It left each system free to choose its internal storage, user-facing presentation and services.

The message-transfer system was asked to carry the formatted message transparently; the transport envelope and control information sat outside this particular format specification.

That narrow interface mattered because the systems were unlike one another. The document treated a sender or recipient as a person, an organizational role or a software process. It expected messages to wait while another system was unavailable. It allowed vendor-defined extensions within its structure, rather than pretending every future office requirement would fit a fixed list. The government wanted the information arriving at the border to be intelligible. It did not need every office to buy the same screen, disk layout or internal workflow. A common exchange form can be modest even when the binder describing it is enormous.

The federal clock was less modest. FIPS 98 applied to federal departments and agencies acquiring or using CBMS in networked systems. A standalone system outside interconnection had a different status; networks established strictly for computer-science or communications research were exempt. When a new node entered an existing network, older nodes could be retrofitted or use a translator. For covered equipment and services ordered after 24 months, the standard set a conformance requirement. New in-house CBMS development begun after 12 months faced its own trigger.

Heads of agencies could seek a waiver for demonstrable cost or performance advantage, but the Secretary of Commerce had the approval authority. The pages told agencies to wait for approval before deviating. Those dates, exceptions and decision rights lived in the federal publication, not in the act of numbering it as an RFC.

The design is more interesting than a simple contest between a central rule and local freedom. The central government could make a purchase contingent on a shared border format, while each machine kept its own interior. The research community could inspect and discuss that format without becoming the federal waiver office. RFC 841 drew both boundaries in black ink: where a message must look alike, and where an institution's authority stops.

There is a quiet joke in the final arrangement. The rule was published in one of the Internet's most visible technical archives, but the binding part still depended on who was buying what, when, under which federal conditions. A standard can cross a network as information far more easily than its mandate can cross an institutional border. The binder made the trip. The stamp stayed home.