1. Job Attribute and Event Monitoring Methods
PWG-C Meeting
April 3 -7, 2000
Tokyo

2. IPP Notification Over SNMP
Print protocol/Service neutral
Consistent set of job notification attributes
Extends functionality of legacy print protocol
Service-neutral - support for Scanner MIB, Fax MIB, etc.
SNMP event notification definitions (traps or inform)
‘jmDeviceBasicV2Event’ - IPP Printer basic event
12 required objects (plus 4 optional objects)
‘jmJobBasicV2Event’ - IPP Job basic event
11 required objects (plus optional vendor extensions)
‘jmJobCompletedV2Event’ - IPP Job completed event
14 required objects (plus 3 optional objects)
‘jmJobProgressV2Event’ - IPP Job progress event
18 required objects (plus 3 optional objects)

3. Managed Object Mapping-Printer Events
IPP Printer event attribute
version-number
status-code
request-id
attributes-charset
attributes-natural-language
printer-uri
printer-name
job-id
job-name
trigger-event
trigger-time
trigger-date-time
subscription-id
subscriber-user-name
subscriber-user-data
printer-state
printer-state-reasons
printer-is-accepting-jobs
Job Monitoring MIB object mapping
[no mapping - not useful]
[implicit in each generated trap]
[request-id in SNMP trap header]
[no mapping - strings are UTF-8]
[no mapping - no text bindings]
jmEventDeviceURI
jmEventDeviceName
jmEventJobIndex [and jmEventJobSetIndex]
jmEventJobName
jmEventTriggerEvent
[sysUpTime in SNMP trap bindings]
[hrSystemDate in Host Res MIB]
jmEventSubscriptionID
jmEventSubscriberUserName
jmEventSubscriberUserData
jmEventDeviceState
jmEventDeviceStateReasons
jmEventDeviceIsAcceptingJobs

4. Managed Object Mapping-Job Events
IPP Job event attribute
version-number
status-code
request-id
attributes-charset
attributes-natural-language
printer-uri
printer-name
job-id
job-name
trigger-event
trigger-time
trigger-date-time
subscription-id
subscriber-user-name
subscriber-user-data
job-state
job-state-reasons
Job Monitoring MIB object mapping
[no mapping - not useful]
[implicit in each generated trap]
[request-id in SNMP trap header]
[no mapping - strings are UTF-8]
[no mapping - no text bindings]
jmEventDeviceURI
jmEventDeviceName
jmEventJobIndex [and jmEventJobSetIndex]
jmEventJobName
jmEventTriggerEvent
[sysUpTime in SNMP trap bindings]
[hrSystemDate in Host Res MIB]
jmEventSubscriptionID
jmEventSubscriberUserName
jmEventSubscriberUserData
jmEventJobState
jmEventJobStateReasons

5. Managed Object Mapping-Job Events
IPP Job-completed event
job-k-octets
job-k-octets-processed
job-impressions
job-impressions-completed
job-media-sheets
job-media-sheets-completed
IPP Job-progress event
impressions-completed-current-copy
job-collation-type
sheet-completed-copy-number
sheet-completed-document-number
Job Monitoring MIB object mapping
jmEventJobKOctets
jmEventJobKOctetsProcessed
jmEventJobImpressions
jmEventJobImpressionsCompleted
jmEventJobMediaSheets
jmEventJobMediaSheetsCompleted
jmEventJobImpressionsCompletedCC
jmEventJobCollationType
jmEventJobSheetCompletedCopyNum
jmEventJobSheetCompletedDocNum

6. Rules for Encoding Notifications
SNMP traps MAY not fit the MTU size
To ensure SNMP traps fit in PDU
Truncate all strings specified for variable-bindings
reduced maximum sizes specified in OBJECT
MODULE-COMPLIANCE
Truncate selected string objects (in order) to the empty string
'jmEventSubscriberUserName'
'jmEventSubscriberUserData'
'jmEventDeviceURI'
'jmEventDeviceName'
'jmEventDeviceStateReasons'
'jmEventJobName'
'jmEventJobStateReasons'
Over some transports and/or media, the variable-bindings of these SNMP traps MAY not fit the MTU (maximum transmission unit) size. Conforming IPP Notification generators SHALL perform this procedure to ensure that all variable-bindings of these SNMP traps are always included in the generated SNMP trap packet:
1) Truncate all strings specified for variable-bindings to the reduced maximum sizes that are specified in their
corresponding OBJECT clauses in their MODULE-COMPLIANCE.
1a) If all variable-bindings now fit within the MTU, then exit this procedure and generate the SNMP trap.
2) Truncate the next one of the following string objects to the empty string (zero length in the ASN.1 BER encoding), in the order listed:
2a) If all variable-bindings now fit within the MTU, then exit this procedure and generate the SNMP trap.
2b) If all variable-bindings do NOT fit within the MTU, then repeat step (2) for next string object.
3) If all variable-bindings do NOT fit within the MTU, then -> logic error (variable-bindings MUST now fit).

7. Registration for IPP Notifications
Registration via IPP
'notify-recipient' = 'snmpnotify://hostname[.port]'
Registration via SNMP
RFC 2573
SNMP Notification MIB
SNMP Target MIB
SNMP Set-Request operations MAY be used to create appropriate rows in the SNMP Notification MIB defined in [RFC-2573] and MAY specify:
1) 'snmpNotifyTag'
- tag of this notification - see 'snmpTargetAddrTagList' below
2) 'snmpNotifyType'
- notification sent using either SNMP Trap (unacknowledged) or SNMP Inform-Request
3) 'snmpNotifyStorageType'
- row persistence of this registration
SNMP Set-Request operations MAY be used SNMP Target MIB defined in [RFC-2573] 1) 'snmpTargetAddrTDomain' and 'snmpTargetAddrTAddress'
- target transport protocol and address (equivalent to URI)
2) 'snmpTargetAddressTimeout' and 'snmpTargetAddrRetryCount'
- retry timeout and limit (for acknowledged notifications delivered using SNMP Inform-Request rather than SNMP Trap)
3) 'snmpTargetAddrTagList'
- tags of notifications to be sent to this target (client)
4) 'snmpTargetAddrParamsEntry'
- notification security and SNMP protocol version
5) 'snmpTargetAddrStorageType'

8. Relationship to Other MIBs
MIB-II (RFC 1213)
sysUpTime
Host Resources MIB (RFC 1514)
hrDeviceStatus
hrDevicePrinterStatus
Printer MIB (RFC 1759)
‘jmDeviceBasicV2Event’ - IPP Printer basic event
12 required objects (plus 4 optional objects)
Printer MIB (RFC 1759)
The 'jmDeviceBasicV2Event' trap defined in this document permits
optional binding of the 'hrDeviceStatus', 'hrDevicePrinterStatus',
and 'hrPrinterDetectedErrorState' objects from Host Resources MIB
[RFC-1514].
The appropriate value of 'hrDeviceIndex' to use in the Printer MIB
[RFC-1759] may be indicated by the instance suffix of the
'hrDeviceStatus' variable's OID.