XEROX WorkCentre 7755/7765/7775 Information Assurance Disclosure Paper
35
Ver. 1.01, April 2010
Page
35 of 40
6.2.
Appendix B – Supported MIB Objects
NOTES :
(1)
The number of objects shown per MIB group represents the number of objects defined by the IETF
standard for that MIB group. It does not represent the instantiation of the MIB group which may
contain many more objects.
(2)
Some MIB objects defined within Input and Output groups of the Printer MIB (
RFC 1759
) have a
MAX-ACCESS of RW. However, the Printer MIBv2 defines a MIB-ACCESS of RO for these MIB objects
within the Input and Output groups and all machines assessed support RO access. Therefore, RO
access to these MIB objects is considered IETF compliant.
(3)
It is assumed that mandatory IETF string-related MIB objects shall contain meaningful data; not
blank strings
(4)
The "
(C)
" notation indicates that the previously stated item is a true caveat condition. The "
(I)
"
notation indicates that the previous stated item should be regarded as information only.
(5)
MIB objects that CANNOT be populated with meaningful data (e.g. a machine may not have paper
level sensors, hence, can only support "0" or "-3 for more than 1 sheet" for prtInputCurrentLevel) will
be considered a caveat, denoted as "(C)".
(6)
The Printer MIB requires a few groups from RFC 1213 and RFC 1514 to be supported. Therefore, this
assessment will indicate that these groups are "supported" as long as the basic MIB structures have
been implemented.
Support Definitions
Term
Definition
"supported"
all MIB objects exists and are populated w/ meaningful data that is consistent w/ the
hardware installed within the machine.
"supported w/ caveats"
all MIB objects exists, however, 2 major bugs or less may exists w/ some of the objects that
were not fixed
"not supported"
MIB objects do not exist/implementation was not planned
"not fully supported"
MIB objects exists, HOWEVER, are NOT populated w/ meaningful data OR provide only default
values OR contain 3 or more major bugs
"optional, *"
optional group that is NOT required by the RFC, however, an implementation may exist; some
MIB objects may not be populated w/ meaningful data
SNMP version / Network Transport support
WorkCentre
SNMPv1 (RFC 1157)
supported
SNMPv2P (RFCs 140x)
not supported
SNMPv2C (RFCs 190x)
supported
SNMPv3 (RFCs 1902, 2572, 2574)
supported
SNMP over UDP (IP)
supported
SNMP over IPX (Netware)
supported
SNMP over NETBEUI (Microsoft Networking)
not supported (implemented but never delivered)
