Summary

  • RFC 1988 recorded an automatic HP covenant covering a named patent family for qualifying IETF standards-track MIB implementations; no application, signature or written licence was required.
  • The covenant excluded proprietary MIB modules, depended on a defined Internet-standard network-management use, and permanently terminated for a party after the retaliation trigger described in the RFC.

The most consequential sentence in RFC 1988 was not a technical instruction. It was an instruction about transaction cost. Hewlett-Packard said its covenant would become effective automatically. An implementor did not have to request a licence, sign a document or wait for a bilateral negotiation before relying on the published grant for a qualifying implementation. Written confirmation was available on request, but confirmation documented the covenant; it did not activate it.

That mechanism was unusually portable for a patent notice. Yet “automatic” was a description of how the right began, not a promise that the right followed any use of the technology. The same document that removed the front-door negotiation also drew a narrow corridor around the result.

Four conditions, not one broad permission

The first boundary was the patent family. RFC 1988 named US patents 5,293,635 and 5,421,024, together with stated continuations, divisions, continuations-in-part and non-US counterparts. It did not announce a general licence to HP's portfolio. The text expressly left licences under other HP patents to HP's then-current terms, conditions and rates.

The second boundary was the type of document being implemented. The covenant applied to implementations of IETF standards-track Management Information Base modules containing HP's contributed search-address technology or derivatives. The standards-track condition mattered. A module did not enter the corridor merely because it looked similar or used the same engineering idea.

The third boundary was use. The covered implementation had to use the contribution in implementing the Internet-standard network-management framework. This is a separate proposition from the identity of the patent and from the status of the MIB module. A patent number, a standards-track label and a permitted operating context were three distinct facts.

The fourth boundary was explicit exclusion: proprietary MIB modules were outside the covenant. The RFC therefore reduced friction in the common standards layer without making the technology portable into every private extension. The public route was automatic; the private branch was not.

The grant contained its own cut-off

RFC 1988 also included a retaliation clause. The covenant permanently terminated for a party if that party or its subsidiary asserted a patent under its control against HP or an HP subsidiary for the implementation or operation of a system using the search-address technology. The document places termination on the date of assertion.

That wording changed the control surface. HP did not retain a general right to revoke the covenant whenever it wished. Instead, the published benefit carried a stated trigger tied to the beneficiary's own patent conduct. A party could enter the standards corridor automatically, but a qualifying assertion could destroy its benefit permanently.

The distinction matters because it is easy to compress the record into two inaccurate slogans. “HP opened the patents” is too broad: the covenant was limited by patent family, module status, use and exclusion. “Implementors still had to negotiate” is also wrong for the qualifying grant: no written licence was required. The operational history lies between those claims.

Where the notice travelled

Later standards-track documents show the notice moving with the technical contribution. RFC 2108, a 1997 Proposed Standard revising the IEEE 802.3 repeater MIB, added address-search and topology-mapping capabilities. Its address-tracking section said the definitions were based on HP-patented technology, stated that HP had granted rights to implementors of that MIB, and cited RFC 1988 and the two patents.

RFC 2266, a 1998 Proposed Standard for IEEE 802.12 repeater devices, likewise included address-tracking definitions and cited the covenant and patent numbers. Compared with the earlier RFC 1516 repeater MIB, RFC 2108 presented address search and topology mapping as new capabilities.

These references are useful evidence, but only at document level. They show that standards-track MIB specifications carried the patent notice and pointed implementors to the automatic covenant. They do not establish that a vendor shipped the feature, that an operator deployed it, that a dispute was avoided, or that any patent claim was valid or infringed.

What the RFC can and cannot prove

RFC 1988 is an Informational document and says it specifies no Internet standard. It is primary evidence of a published covenant and the terms recorded there. It is not a court judgment, a patent-status report, a deployment survey or a worldwide freedom-to-operate opinion. Its security considerations do not analyse security issues.

That evidentiary discipline is especially important now. The article does not infer current patent term, ownership, enforceability or jurisdictional effect from a 1996 publication. Nor does it classify an unnamed product's MIB as standards-track or proprietary. Those questions require evidence beyond this source packet.

Lu Heng's “Minimum Initial Specification” lens helps explain the design choice without turning it into legal doctrine. A reusable covenant made one permission legible at the shared layer, reducing repeated coordination. “Running-Code Primacy” supplies the counterweight: publication is not implementation, and a standards-track reference is not adoption. The covenant could clear a documented permission path; only systems in operation could show that anyone travelled it.

RFC 1988's durable lesson is therefore neither that patents disappeared nor that standards work was trapped behind private negotiation. It is that a public automatic grant can lower friction while retaining sharp portability and retaliation boundaries. Automatic was a method of entry. It was never a synonym for unconditional.

Sources