Summary

  • RFC 1243 put AppleTalk ports, routes, zones, service registrations and counters into one SNMP management model, but it also required managers to read origin and state fields before treating a returned value as current operational evidence.
  • RFC 1742 later changed several read/write boundaries and added source, default and current distinctions, showing that a MIB access label was a revisable allocation of responsibility rather than proof of a successful network change.

In a quiet management station, two numbers may look identical. One was entered by an operator. Another was inferred from traffic on the network. A third was guessed by a device trying to start. RFC 1243 refused to let those histories collapse into one value.

Published in July 1991, RFC 1243 defined managed objects for AppleTalk networks using SNMP. Its groups followed the protocol stack and its supporting machinery: LocalTalk link access, address resolution, ports, datagram delivery, routing, AppleTalk-over-IP encapsulation, zones, service naming and echo tests. If a group applied to an implementation, the agent was expected to implement the whole group.

The most revealing group was ATPort. An AppleTalk port was a logical connection over which packets could travel. Its row contained a type, a network range, a network address, a status, a zone and a link to a physical interface. Several of those values were marked read-write. But beside them sat two read-only origin fields, atportNetConfig and atportZoneConfig.

Each origin field had four states. configured meant explicit configuration. garnered meant the value had been assumed after inspecting the network. guessed meant a random configuration. unconfigured meant there was no configuration to report. The categories made a simple operational point: the value alone was not enough. A network number learned from surrounding activity carried a different custody trail from one deliberately entered by an administrator, even when the bytes happened to match.

Status supplied another missing dimension. atportStatus could be operational, unconfigured, off or invalid. Setting it to invalid disassociated the mapping, yet the RFC left physical removal of the row to the implementation. A manager therefore had to be prepared to receive table entries that were no longer in use. The row's continued visibility did not make it live.

That rule recurred. An RTMP route had a range, next hop, network type, port, hop count and state. Most of those route fields were read-write in RFC 1243. Its state could be good, suspect, going bad or bad. Marking the row bad could invalidate it without guaranteeing that it disappeared from the table. KIP, the AppleTalk-over-IP routing group, separately distinguished configured, learned and invalid entries, and carried another flag for whether information would be shared with other routers. The route value, its origin, its local state and its propagation treatment were separate facts.

The zone and service tables had the same interpretive burden. ZIP mapped reachable network ranges to zone names. NBP described services registered on the entity by object name, service type and zone. Their visible fields were writable, and their state fields could invalidate an entry. Again, a returned row might be retained after it ceased to be usable. An inventory assembled by listing rows without examining their state would confuse memory with operation.

Even the counters stayed local. The ATEcho group counted requests received and replies sent. Those totals could show that an agent had processed certain events. They did not correlate a particular request with a particular reply, name the peer, establish the path or prove that a user's test succeeded. RFC 1243 itself said security issues were not discussed.

The replacement moved the boundary

January 1995 brought RFC 1742, AppleTalk MIB II, which obsoleted RFC 1243. It did more than append objects. It revised who could write what.

The old atportNetConfig and atportZoneConfig origin/status fields changed from read-only to read-write. At the same time, the RTMP range, next hop, type, port and hop-count fields changed from read-write to read-only. ZIP's zone name and network-range fields also became read-only. The second MIB did not treat mutability as a timeless quality of “a route” or “a zone.” It redrew the interface between management input and protocol-maintained state.

The new model also added evidence about source and divergence. atportNetFrom and atportZoneFrom recorded where network and zone information came from. The former zone object became atportZoneDefault, and the port gained a separate atportCurrentZone. A default could now be named without pretending it was the current observed result. NBP descriptions suggested that an agent re-register a service when its name, type or zone changed, which made the required downstream action visible without turning a write into proof that registration completed.

Implementation experience also changed the measurement surface. RFC 1742 added AARP lookup and hit counters, RTMP route deletion and overflow counters, NBP registration failures and per-port traffic. It deprecated LLAP counters that duplicated MIB-II interface counters. Adding one measure and retiring another was a decision about denominator, scope and duplicate evidence—not evidence that every agent or collector migrated on publication day.

Read side by side, the RFCs preserve an unusually useful historical correction. A MIB is not a photograph of a network. It is a versioned contract for naming state, accepting some inputs and reporting some observations. To reconstruct the operational sequence, an operator would still need the exact MIB version and object instance, the value and its source state, the row status, the authenticated request and response, the agent's persistence behavior, protocol observations and the later service effect.

Neither RFC supplies that operational ledger. What they supply is the reason it is necessary.

Sources

Evidence limits

These RFCs establish object definitions, access labels, enumerated states, successor status and documented changes. They do not establish a named implementation, administrator, authorized write, live route, current zone, successful registration, packet delivery, deployment share or user outcome.