To me RFC1759 states quite clearly (inserting appropriate excerpts):
An interface is the communications port and associated protocols that
are responsible for the transport of data to the printer. A printer
has one or more interface sub-units. The interfaces are represented
by the Interfaces Group of MIB-II (RFC 1213).
3. Objects from other MIB Specifications
This section lists the objects from other IETF MIB specifications
that are mandatory for conformance to this Printer MIB specification.
3.1. System Group objects
All objects in the system group of MIB-II (RFC 1213) must be
3.3. Interface Group objects
All objects in the Interfaces Group of MIB-II (RFC 1213) shall be
I agree, the actual definition of the "system" is poorly articulated in
RFC1759. I will argue that the implication is that the Printer is the
system, however, I would probably have a difficult time substantiating
that (except the *name* of RFC1759 *is* the PRINTER MIB, not the NIC
MIB!). So System group of MIB-II stands a bit weak, but Interfaces
seems clearly defined, to me.
I guess my main concern in making the sweeping changes Bill suggests is
that an implementation that DOES treat the Printer as the system in terms
of both System and Interfaces groups of MIB-II would not end up looking
"broken" or non-compliant.
Harry Lewis - IBM Printing Systems.