Summary

  • RFC 1216 says it proposes a new standard paradigm for the IAB standardization track. The RFC Editor catalogue instead marks it Informational and Independent, while the IETF Datatracker says it is not IETF-endorsed and has no formal standing in the standards process.
  • The memo, dated 1 April 1991, constructs Ultra Low Speed networking by reversing the language of gigabit performance, network economics and protocol progress. Its figures and mechanisms are claims inside the document, not deployment evidence.
  • An RFC number proves that a document entered the archive. It does not by itself prove standards approval, implementation, adoption, interoperability or economic effect.

Read the status twice

The first surprise in RFC 1216 arrives before Ultra Low Speed networking does. Under “Status of this Memo”, the text says that it proposes a new standard paradigm for the Internet Activities Board standardization track.

Read only that sentence and the institutional story appears settled. There is a proposal, a standardization track and a named body. The vocabulary resembles authority.

Now read the catalogue. The RFC Editor record classifies the document as Informational, dates it to 1 April 1991 and places it in the Independent Stream. The IETF Datatracker record is blunter: the RFC was published through the Independent Submission stream, is not endorsed by the IETF and has no formal standing in the IETF standards process.

Both records need to survive intact. The sentence belongs to the content of the archived memo. The catalogue supplies the status of that document. Replacing the sentence with the catalogue would alter the primary source. Replacing the catalogue with the sentence would let the source certify its own institutional authority.

This distinction matters far beyond an April 1 RFC. A proposal can describe itself as a standard. A vendor paper can call a format open. A policy memorandum can call a practice mandatory. Those statements are evidence of what the author asserted. They are not the same record as approval by the body that controls the relevant status.

Ultra Low Speed was an inversion machine

RFC 1216 begins close enough to ordinary engineering language to invite a serious reading. It discusses the historical trade-off among processor capacity, memory and communications bandwidth. It then cites projected per-decade cost declines: 99 per cent for a bit of storage and a MIP of processing, but 90 per cent for a bit per second of communication.

The memo compounds that nine-point difference into a crisis. Processing power would create demand for bandwidth without paying for it; the Internet community would be bankrupted unless a paradigm shifted. The cure is to stop racing upward and operate around .01 uGbps: Ultra Low Speed, or ULS.

The internal logic grows tidier as its premises grow less useful. A gigabit optical link, the memo says, could multiplex vast numbers of tiny ULS circuits. An individual circuit might cost less than three cents per month. Ten terahertz of fibre bandwidth could accommodate roughly a trillion users. Those figures tell us how the argument is staged. This evidence packet does not turn them into observed costs, capacity measurements or forecasts that later came true.

Application fit receives the same reversal. Low-priority facsimiles might tolerate three-hour delivery. Glacier tracking, the U.S. postal service and research contracting appear on the list. In an “extremely-low-speed” regime, the text adds gravity-wave detectors, the Italian postal service and the congressional budget process.

The joke does analytical work. Performance claims always depend on a task, a clock and a party bearing the delay. By choosing applications whose time scales are stretched, bureaucratic or both, RFC 1216 makes “slow enough” sound like optimization. It exposes how easily a specification can win an argument after it chooses the metric on which it is judged.

That is not evidence that delay is harmless. A three-hour fax may be adequate for one sender and catastrophic for another. A cheap logical circuit may consume expensive operational attention. Multiplexing capacity does not establish demand, support cost, reliability or willingness to pay. The memo's economic statements remain propositions inside a deliberately inverted case.

Old protocols became a feature

The technical section reverses a familiar slogan: if gigabit networks require new protocols, ULS must require old ones. The imagined engineering programme retreats into decayed magnetic dump tapes, paper tape, recycled card decks, germanium and relays. The alternating-bit protocol becomes a leading contender.

Even a proverb is made to carry protocol meaning. If bad news travels fast, the memo reasons, a slow network should favour good news. Bills and notices would be delayed; some mailing lists would gain productivity. The inference is linguistically neat and operationally empty. A proverb supplies neither a scheduler nor a classification function.

Efficiency itself then becomes a defect. Slow start, fewer errors and small one-bit sequence numbers risk “creeping efficiency”, pushing the design away from the desired operating point. The proposed remedies are Forward Error Insertion, negative window scaling, new protocol layers and multiple presentation layers.

Each item imitates the grammar of an engineering work plan: problem, mechanism, research need, proposed remedy. None of that grammar proves that a mechanism was implemented or tested. A named technique is still a named technique. A section called “Technical Feasibility” is still a section heading. The conclusion — the road to ULS is long, slow and easy — closes the inversion without creating an operational record.

Security is bounded just as sharply. The memo says security issues are not discussed. That sentence cannot support authentication, integrity, confidentiality, safety or resistance to abuse. It only records an omission.

The archive contains more than standards

The category error became important enough to receive its own later RFC. RFC 1796, Not All RFCs Are Standards, explains that the RFC series publishes Internet standards documents and other material. It calls publication-as-recognition a widespread misconception and warns that an informational document may look like an official protocol specification.

That 1995 explanation should not be projected backward as the exact rulebook that handled RFC 1216 in 1991. It is valuable for a narrower reason: it states the reading discipline the archive requires. Document identity and standards status are different fields.

RFC 2026, published in 1996, makes the separation more explicit. RFCs range from research concepts to status memos as well as Internet Standards. A specification adopted as an Internet Standard receives an additional STD label while keeping its RFC number. Informational and Experimental specifications remain outside the Standards Track.

Again, the later text clarifies the taxonomy; it does not prove the details of an earlier editorial decision. Its durable lesson is that “RFC” identifies a document in a series. “Internet Standard” records a different institutional result.

The modern framework in RFC 8729 adds the stream dimension. The RFC Series preserves general research and engineering contributions as well as standards documents. Each stream has its own approval process. Only the IETF stream can approve Standards-Track or Best Current Practice RFCs; the Independent Submission stream exists for work outside the other streams.

This does not make Independent material disposable. The single archive is valuable precisely because it can preserve proposals, experience, arguments and experiments without pretending that they share one approval status. Uniform numbering makes documents retrievable. Status and stream keep retrieval from becoming endorsement.

The RFC number proved publication, not adoption

RFC 1216 therefore supports a short sequence of claims, each with its own evidence.

The primary text proves that the memo used standardization language and proposed ULS. The RFC Editor record proves its archival identity, date, status and stream. The Datatracker records the absence of IETF endorsement and formal standards standing. None of those records shows that code was written, equipment was built, an operator deployed ULS, two implementations interoperated, customers adopted it or its economics were measured.

The absence of implementation evidence in this packet also has a limit. It cannot prove that nobody, anywhere, ever experimented with slow links or an idea inspired by the memo. “Not established here” is not “impossible” and not “never happened”.

This is where historical writing often overreaches. A proposal is upgraded into a programme because it has a number. A programme is upgraded into deployment because a later document cites it. Deployment is upgraded into success because a feature survived. Each upgrade needs a new record: repository or release evidence, implementation notes, conformance tests, operator configuration, traffic observation, adoption data and outcome measurement.

RFC 1216 provides none of those later records. It provides something more modest and unexpectedly durable: a clean demonstration that the voice inside a document is not the authority over the document's status.

Sources