Summary

  • RFC 1473 exposed separate configuration and operational tables for IP over PPP. An administrative open was an event sent to the IPCP state machine, not a promise that it would reach Opened.
  • Changing the compression preference affected the next link restart. Before option negotiation completed, returned compression and slot values were explicitly undefined; after Opened, they described negotiated parameters, not proof that an IP packet arrived.

Published in June 1993, RFC 1473 defined the PPP IP Group: a small set of managed objects for the IP Network Control Protocol. Its economy was deliberate. The authors selected variables essential to fault or configuration management, looked for current utility, limited the count and excluded values that could be derived elsewhere.

That restraint produced a sharper historical document than a crowded dashboard would have. It separated what an operator wanted, what the finite-state machine had achieved and what the wire might later carry.

An open command entered a machine

The writable configuration table contained two decisions. The first, pppIpConfigAdminStatus, expressed the immediate desired state of the IP network protocol. Setting it to open injected an administrative Open event into the IPCP finite-state machine; setting it to close injected Close.

The verb matters. An event is an input. The machine may still need an available lower layer, peer exchanges, acceptable options and time. A successful management write proves that a request reached the agent and was accepted according to that interface. It does not prove the next state, still less an operational service.

The later PPP specification, RFC 1661, kept those stages separate. Each network-layer protocol had its own Network Control Protocol, and each NCP could be opened or closed independently. IP could fail while another network protocol remained available over the same PPP link.

One setting waited for the next restart

The second writable object, pppIpConfigCompression, selected either no compression or Van Jacobson TCP/IP header compression as the mode the local node would attempt to negotiate. Its description included a temporal boundary that management software could easily erase: changing it would take effect when the link was next restarted.

The new value was therefore neither the current wire state nor a command to mutate the active session. It was a stored preference for the next opportunity. To show that it mattered, an audit needed the committed write, the identity of the later restart, the IPCP exchange and the resulting state.

RFC 1332 supplied the protocol behind that transition. IPCP negotiated an IP-Compression-Protocol option; the default was no compression. The option indicated the ability to receive compressed packets, and each end had to request it separately if compression was wanted in both directions.

A single checkbox could not truthfully summarize this. Local willingness to receive did not establish remote willingness. A stored preference did not establish that the link restarted. A restart did not establish that the peer accepted the option.

Before Opened, the numbers had no agreed meaning

RFC 1473's read-only table exposed pppIpOperStatus plus the compression protocol and maximum slot identifier for each direction. But the document placed a condition over the whole group of negotiated values: they were unavailable until PPP option negotiation completed, indicated by IPCP reaching Opened.

When status was not Opened, their contents were undefined. The RFC left the returned value to the implementation.

That is stronger than saying “possibly stale.” A stale value once described an older event. An undefined value may be zero, a leftover, a default or any implementation choice without making a claim about this negotiation. The management protocol can successfully return a well-typed integer while the specification withholds semantic authority from it.

After Opened, direction still mattered. The local-to-remote field described the method used while the local entity sent packets. The remote-to-local field described the opposite direction. Max-Slot-Id was meaningful only with Van Jacobson compression; otherwise it had to read zero. The same numeral therefore required both state and protocol context.

Opened was a threshold, not a receipt

RFC 1332 said that before IP packets could be communicated, PPP had to reach the Network-Layer Protocol phase and IPCP had to reach Opened. RFC 1661 later stated that after an NCP opened, PPP would carry the corresponding network-layer packets, while packets received before that state had to be discarded.

Opened was consequential. It changed which packets the protocol was permitted to carry. But it remained a state-machine fact. It did not name a packet, show a counter advancing, prove decompression succeeded, establish a route or record an application response.

RFC 1144 explained why header compression mattered on slow links: repeated TCP/IP header material could be represented compactly using connection state. That benefit also creates a later evidentiary chain. Negotiated permission is not a compressed packet; a compressed packet is not correct reconstruction; correct reconstruction is not useful delivery.

The MIB drew a line that automation should keep

RFC 1473 placed configuration in a separate table partly to support a separate management view. Its security discussion warned that PPP configuration and control could be risky and described protected or inaccessible views as safeguards. The companion RFC 1471 managed LCP, while RFC 1472 isolated authentication configuration. The family was not one all-knowing status object.

For a modern change system, the useful record is a chain: who requested compression; what the agent retained; which configuration generation applied to which restart; which direction proposed which option; what the peer acknowledged or rejected; when IPCP entered and left Opened; and what packet, error and application evidence followed.

Without that chain, a dashboard can turn three different absences into one reassuring value. A pending preference looks active. An undefined read looks measured. An Opened state looks like delivered traffic.

RFC 1473's enduring lesson is quieter. Manageability begins when the system knows which facts it does not yet have.

Sources