draft-ietf-ipp-not-over-snmp-01.txt   draft-ietf-ipp-not-over-snmp-02.txt 
Internet Printing Protocol Working Group Tom Hastings Internet Printing Protocol Working Group Tom Hastings
INTERNET DRAFT Xerox INTERNET DRAFT Xerox
Expires 1 June 2000 Ira McDonald Expires 19 September 2000 Ira McDonald
High North High North
1 December 1999 19 March 2000
Internet Printing Protocol/1.1: Notifications over SNMP Internet Printing Protocol (IPP):
<draft-ietf-ipp-not-over-snmp-01.txt> Notifications over SNMP via Job Monitoring MIB
<draft-ietf-ipp-not-over-snmp-02.txt>
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. Internet-Drafts are working all provisions of Section 10 of RFC2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
skipping to change at page 1, line 38 skipping to change at page 1, line 40
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract Abstract
This document is a submission to the Internet Printing Protocol This document is a submission to the Internet Printing Protocol
Working Group of the Internet Engineering Task Force (IETF). Working Group of the Internet Engineering Task Force (IETF).
Comments should be submitted to the ipp@pwg.org mailing list. Comments should be submitted to the ipp@pwg.org mailing list.
This document proposes a mapping of IPP notifications over SNMP, This document proposes a mapping of IPP notifications over SNMP via
using new Printer Event and Job Event traps (to be added to the PWG new device and job traps extensions defined for the Job Monitoring
Job Monitoring MIB [PWG-JOB]). This mapping may be used to deliver MIB [RFC-2707]. This mapping may be used to deliver printer
printer notifications for any printer (not just IPP-capable ones) and notifications for any printer (not just IPP-capable ones) and also
also job notifications for any job (not just ones submitted via IPP). job notifications for any job (not just ones submitted via IPP).
This document proposes: (2) SNMP traps; and (7) SNMP leaf objects This document proposes: (4) SNMP traps; and (24) SNMP leaf objects
(for use in trap bindings). (for use in various trap bindings).
Table of Contents Table of Contents
1. Introduction ............................................... 3 1. Introduction ............................................... 4
1.1. Terminology for Conformance ............................ 3 1.1. Terminology for Conformance ............................ 4
2. SNMP Network Management Framework .......................... 3 2. SNMP Network Management Framework .......................... 4
3. Managed Object Mapping ..................................... 3 3. Managed Object Mapping ..................................... 5
3.1. SNMP Mapping for IPP Printer Events .................... 3 3.1. SNMP Mapping for IPP Printer Events .................... 5
3.2. SNMP Mapping for IPP Job Events ........................ 4 3.2. SNMP Mapping for IPP Job Events ........................ 5
3.3. Rules for Encoding Notifications ....................... 4 3.3. Rules for Encoding Notifications ....................... 6
3.4. Registration for IPP Notifications ..................... 5 3.4. Registration for IPP Notifications ..................... 7
3.4.1. Registration via IPP ............................... 5 3.4.1. Registration via IPP ............................... 7
3.4.2. Registration via SNMP .............................. 5 3.4.2. Registration via SNMP .............................. 7
3.5. Relationship to other MIBs ............................. 6 3.5. Relationship to other MIBs ............................. 8
3.5.1. IETF Host Resources MIB (RFC 1514) ................. 6 3.5.1. MIB-II (RFC 1213) .................................. 8
3.5.2. IETF Printer MIB (RFC 1759) ........................ 6 3.5.2. Host Resources MIB (RFC 1514) ...................... 8
3.5.3. Printer MIB v2 (work-in-progress) .................. 7 3.5.3. Printer MIB (RFC 1759) ............................. 8
4. Managed Object Definitions ................................. 8 4. Managed Object Definitions ................................. 9
4.1. Printer Event Trap ..................................... 8 4.1. Device Basic Event Trap ................................ 9
4.1.1. jmPrinterEventV2Event (notification) ............... 8 4.1.1. jmDeviceBasicV2Event (notification) ................ 9
4.2. Job Event Trap ......................................... 9 4.2. Job Basic Event Trap ................................... 10
4.2.1. jmJobEventV2Event (notification) ................... 9 4.2.1. jmJobBasicV2Event (notification) ................... 11
4.3. Event Objects .......................................... 10 4.3. Job Completed Event Trap ............................... 11
4.3.1. jmEventTriggerEvent (object) ....................... 11 4.3.1. jmJobCompletedV2Event (notification) ............... 12
4.3.2. jmEventSubscriptionID (object) ..................... 11 4.4. Job Progress Event Trap ................................ 13
4.3.3. jmEventSubscriberUserName (object) ................. 11 4.4.1. jmJobProgressV2Event (notification) ................ 13
4.3.4. jmEventSubscriberUserData (object) ................. 12 4.5. Event Binding Group .................................... 14
4.3.5. jmEventPrinterState (object) ....................... 12 4.5.1. jmEventTriggerEvent (object) ....................... 14
4.3.6. jmEventPrinterStateReasons (object) ................ 13 4.5.2. jmEventSubscriptionID (object) ..................... 15
4.3.7. jmEventPrinterIsAcceptingJobs (object) ............. 13 4.5.3. jmEventSubscriberUserName (object) ................. 15
5. IANA Considerations ........................................ 14 4.5.4. jmEventSubscriberUserData (object) ................. 16
6. Internationalization Considerations ........................ 14 4.5.5. jmEventDeviceURI (object) .......................... 16
7. Security Considerations .................................... 14 4.5.6. jmEventDeviceName (object) ......................... 17
8. References ................................................. 15 4.5.7. jmEventDeviceState (object) ........................ 17
9. Change Log ................................................. 15 4.5.8. jmEventDeviceStateReasons (object) ................. 17
10. Intellectual Property Notice .............................. 16 4.5.9. jmEventDeviceIsAcceptingJobs (object) .............. 18
11. Authors' Addresses ........................................ 16 4.5.10. jmEventJobSetIndex (object) ....................... 18
12. Full Copyright Statement .................................. 17 4.5.11. jmEventJobIndex (object) .......................... 19
4.5.12. jmEventJobName (object) ........................... 19
4.5.13. jmEventJobState (object) .......................... 19
4.5.14. jmEventJobStateReasons (object) ................... 20
4.5.15. jmEventJobKOctets (object) ........................ 20
4.5.16. jmEventJobKOctetsProcessed (object) ............... 21
4.5.17. jmEventJobImpressions (object) .................... 21
4.5.18. jmEventJobImpressionsCompleted (object) ........... 21
4.5.19. jmEventJobMediaSheets (object) .................... 22
4.5.20. jmEventJobMediaSheetsCompleted (object) ........... 22
4.5.21. jmEventJobImpressionsCompletedCC (object) ......... 22
4.5.22. jmEventJobCollationType (object) .................. 23
4.5.23. jmEventJobSheetCompletedCopyNum (object) .......... 23
4.5.24. jmEventJobSheetCompletedDocNum (object) ........... 23
5. IANA Considerations ........................................ 25
6. Internationalization Considerations ........................ 25
7. Security Considerations .................................... 25
8. References ................................................. 26
9. Change Log ................................................. 27
10. Intellectual Property Notice .............................. 29
11. Authors' Addresses ........................................ 29
12. Full Copyright Statement .................................. 30
1. Introduction 1. Introduction
The IPP protocol [IPP-PRO] supports passive monitoring of IPP Printer The IPP protocol [IPP-PRO] supports passive monitoring of IPP Printer
and Job objects, via client polling of IPP object attributes using and Job objects, via client polling of IPP object attributes using
the 'Get-Printer-Attributes' and 'Get-Job-Attributes' operations. the 'Get-Printer-Attributes' and 'Get-Job-Attributes' operations.
This IPP Notifications over SNMP mapping supports dynamic monitoring This IPP Notifications over SNMP mapping supports dynamic monitoring
of IPP Printer and Job objects, via server generation of SNMP traps. of IPP Printer and Job objects, via server generation of SNMP traps.
1.1. Terminology for Conformance 1.1. Terminology for Conformance
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted per [RFC-2119]. document are to be interpreted per [RFC-2119].
2. SNMP Network Management Framework 2. SNMP Network Management Framework
See: Section 1 'Introduction' and section 2 'Management Information'
of IETF Coexistence between SNMPv1 and SNMPv2 [RFC-1908].
See: Section 1.1 'SNMPv1', section 1.2 'SNMPv2', and section 1.3 See: Section 1.1 'SNMPv1', section 1.2 'SNMPv2', and section 1.3
'SNMPv3' of IETF Coexistence between SNMP Versions [V3-COEX]. 'SNMPv3' of [RFC-2576].
3. Managed Object Mapping 3. Managed Object Mapping
3.1. SNMP Mapping for IPP Printer Events 3.1. SNMP Mapping for IPP Printer Events
IPP Printer event attribute Printer/Job MIB object mapping IPP Printer event attribute Job Monitoring MIB object mapping
--------------------------- ------------------------------ --------------------------- ---------------------------------
version-number [no mapping - not useful] version-number [no mapping - not useful]
status-code [implicit in generated trap] status-code [implicit in each generated trap]
request-id [request-id in SNMP trap header] request-id [request-id in SNMP trap header]
attributes-charset [no mapping - strings are UTF-8] attributes-charset [no mapping - strings are UTF-8]
attributes-natural-language [no mapping - no text bindings] attributes-natural-language [no mapping - no text bindings]
printer-uri [prtChannelInformation in PMv2] printer-uri jmEventDeviceURI
printer-name [prtGeneralPrinterName in PMv2] printer-name jmEventDeviceName
job-id jmJobIndex in OID instance suffix job-id jmEventJobIndex
job-name jobName [and jmEventJobSetIndex]
job-name jmEventJobName
trigger-event jmEventTriggerEvent trigger-event jmEventTriggerEvent
trigger-time [time-stamp in SNMP trap header] trigger-time [sysUpTime in SNMP trap bindings]
trigger-date-time hrSystemDate in Host Res MIB trigger-date-time [hrSystemDate in Host Res MIB]
subscription-id jmEventSubscriptionID subscription-id jmEventSubscriptionID
subscriber-user-name jmEventSubscriberUserName subscriber-user-name jmEventSubscriberUserName
subscriber-user-data jmEventSubscriberUserData subscriber-user-data jmEventSubscriberUserData
printer-state jmEventEventPrinterState printer-state jmEventDeviceState
hrDeviceStatus in Host Res MIB printer-state-reasons jmEventDeviceStateReasons
hrPrinterStatus in Host Res MIB printer-is-accepting-jobs jmEventDeviceIsAcceptingJobs
printer-state-reasons jmEventPrinterStateReasons
hrPrinterDetectedErrorState
in Host Res MIB
printer-is-accepting-jobs jmEventPrinterIsAcceptingJobs
3.2. SNMP Mapping for IPP Job Events 3.2. SNMP Mapping for IPP Job Events
IPP Job event attribute Printer/Job MIB object mapping IPP Job event attribute Job Monitoring MIB object mapping
----------------------- ------------------------------ ----------------------- ---------------------------------
version-number [no mapping - not useful] version-number [no mapping - not useful]
status-code [implicit in generated trap] status-code [implicit in each generated trap]
request-id [request-id in SNMP trap header] request-id [request-id in SNMP trap header]
attributes-charset [no mapping - strings are UTF-8] attributes-charset [no mapping - strings are UTF-8]
attributes-natural-language [no mapping - no text bindings] attributes-natural-language [no mapping - no text bindings]
printer-uri [prtChannelInformation in PMv2] printer-uri jmEventDeviceURI
printer-name [prtGeneralPrinterName in PMv2] printer-name jmEventDeviceName
job-id jmJobIndex in OID instance suffix job-id jmEventJobIndex
job-name jobName [and jmEventJobSetIndex]
job-name jmEventJobName
trigger-event jmEventTriggerEvent trigger-event jmEventTriggerEvent
trigger-time [time-stamp in SNMP trap header] trigger-time [sysUpTime in SNMP trap bindings]
trigger-date-time hrSystemDate in Host Res MIB trigger-date-time [hrSystemDate in Host Res MIB]
subscription-id jmEventSubscriptionID subscription-id jmEventSubscriptionID
subscriber-user-name jmEventSubscriberUserName subscriber-user-name jmEventSubscriberUserName
subscriber-user-data jmEventSubscriberUserData subscriber-user-data jmEventSubscriberUserData
job-state jmJobState job-state jmEventJobState
job-state-reasons jmJobStateReasons1 job-state-reasons jmEventJobStateReasons
jmJobStateReasons2
jmJobStateReasons3
jmJobStateReasons4
[job-completed|state-changed|purged - extra bindings] [job-completed - extra bindings]
job-k-octets-processed jmJobKOctetsProcessed job-k-octets jmEventJobKOctets
job-impressions-completed jmJobImpressionsCompleted job-k-octets-processed jmEventJobKOctetsProcessed
job-media-sheets-completed sheetsCompleted job-impressions jmEventJobImpressions
job-impressions-completed jmEventJobImpressionsCompleted
job-media-sheets jmEventJobMediaSheets
job-media-sheets-completed jmEventJobMediaSheetsCompleted
[job-progress - extra bindings] [job-progress - extra bindings]
job-collation-type jobCollationType impressions-completed-current-copy jmEventJobImpressionsCompletedCC
sheet-completed-copy-number sheetCompletedCopyNumber job-collation-type jmEventJobCollationType
sheet-completed-document-number sheetCompletedDocumentNumber sheet-completed-copy-number jmEventJobSheetCompletedCopyNum
impressions-interpreted impressionsInterpreted sheet-completed-document-number jmEventJobSheetCompletedDocNum
impressions-completed-current-copy impressionsCompletedCurrentCopy
3.3. Rules for Encoding Notifications 3.3. Rules for Encoding Notifications
Over some transports and/or media, the variable-bindings of these Over some transports and/or media, the variable-bindings of these
SNMP traps MAY not fit the MTU (maximum transmission unit) size. SNMP traps MAY not fit the MTU (maximum transmission unit) size.
Conforming IPP Notification generators SHALL perform this procedure Conforming IPP Notification generators SHALL perform this procedure
to ensure that all variable-bindings of these SNMP traps are always to ensure that all variable-bindings of these SNMP traps are always
included in the generated SNMP trap packet: included in the generated SNMP trap packet:
1) Truncate all strings specified for variable-bindings 1) Truncate all strings specified for variable-bindings
to the reduced maximum sizes that are specified in their to the reduced maximum sizes that are specified in their
corresponding OBJECT clauses in their MODULE-COMPLIANCE. corresponding OBJECT clauses in their MODULE-COMPLIANCE.
1a) If all variable-bindings now fit within the MTU, 1a) If all variable-bindings now fit within the MTU,
then exit this procedure and generate the SNMP trap. then exit this procedure and generate the SNMP trap.
2) Truncate the next one of the following string objects to 2) Truncate the next one of the following string objects to
skipping to change at page 5, line 17 skipping to change at page 7, line 20
included in the generated SNMP trap packet: included in the generated SNMP trap packet:
1) Truncate all strings specified for variable-bindings 1) Truncate all strings specified for variable-bindings
to the reduced maximum sizes that are specified in their to the reduced maximum sizes that are specified in their
corresponding OBJECT clauses in their MODULE-COMPLIANCE. corresponding OBJECT clauses in their MODULE-COMPLIANCE.
1a) If all variable-bindings now fit within the MTU, 1a) If all variable-bindings now fit within the MTU,
then exit this procedure and generate the SNMP trap. then exit this procedure and generate the SNMP trap.
2) Truncate the next one of the following string objects to 2) Truncate the next one of the following string objects to
the empty string (zero length in the ASN.1 BER encoding), the empty string (zero length in the ASN.1 BER encoding),
in the order listed: in the order listed:
- 'prtChannelInformation' (from Printer MIB v2 [PRT-MIB2])
- 'prtGeneralPrinterName' (from Printer MIB v2 [PRT-MIB2])
- 'jmEventSubscriberUserName' - 'jmEventSubscriberUserName'
- 'jmEventSubscriberUserData' - 'jmEventSubscriberUserData'
- 'jmAttributeValue...jobName.1' - 'jmEventDeviceURI'
- 'jmEventPrinterStateReasons' - 'jmEventDeviceName'
- 'jmEventPrinterState' - 'jmEventDeviceStateReasons'
- 'jmEventJobName'
- 'jmEventJobStateReasons'
2a) If all variable-bindings now fit within the MTU, 2a) If all variable-bindings now fit within the MTU,
then exit this procedure and generate the SNMP trap. then exit this procedure and generate the SNMP trap.
2b) If all variable-bindings do NOT fit within the MTU, 2b) If all variable-bindings do NOT fit within the MTU,
then repeat step (2) for next string object. then repeat step (2) for next string object.
3) If all variable-bindings do NOT fit within the MTU, 3) If all variable-bindings do NOT fit within the MTU,
then -> logic error (variable-bindings MUST now fit). then -> logic error (variable-bindings MUST now fit).
3.4. Registration for IPP Notifications 3.4. Registration for IPP Notifications
IPP Clients may register for IPP Notifications delivered via SNMP by IPP Clients may register for IPP Notifications delivered via SNMP by
either of the following methods: either of the following methods:
3.4.1. Registration via IPP 3.4.1. Registration via IPP
IPP Create-Subscription and Job creation (Create-Job, Print-Job, IPP Create-Subscription and Job creation (Create-Job, Print-Job,
Print-URI) operations MAY be used to create per-Printer or per-Job Print-URI) operations MAY be used to create per-Printer or per-Job
IPP Subscription objects and MAY specify IPP Subscription objects and MAY specify
'notify-recipient' = 'ipp-snmp://hostname[.port]' 'notify-recipient' = 'snmpnotify://hostname[.port]'
3.4.2. Registration via SNMP 3.4.2. Registration via SNMP
SNMP Set-Request operations MAY be used to create appropriate rows in SNMP Set-Request operations MAY be used to create appropriate rows in
the SNMP Notification MIB defined in [RFC-2573] and MAY specify: the SNMP Notification MIB defined in [RFC-2573] and MAY specify:
1) 'snmpNotifyTag' 1) 'snmpNotifyTag'
- tag of this notification - see 'snmpTargetAddrTagList' below - tag of this notification - see 'snmpTargetAddrTagList' below
- example "jmPrinterEventV2Event" or "jmJobEventV2Event" - example "jmDeviceBasicV2Event" or "jmJobBasicV2Event"
2) 'snmpNotifyType' 2) 'snmpNotifyType'
- notification sent using either SNMP Trap (unacknowledged) - notification sent using either SNMP Trap (unacknowledged)
or SNMP Inform-Request (acknowledged) or SNMP Inform-Request (acknowledged)
3) 'snmpNotifyStorageType' 3) 'snmpNotifyStorageType'
- row persistence of this registration - row persistence of this registration
SNMP Set-Request operations MAY be used to create appropriate rows in SNMP Set-Request operations MAY be used to create appropriate rows in
the SNMP Target MIB defined in [RFC-2573] and MAY specify: the SNMP Target MIB defined in [RFC-2573] and MAY specify:
1) 'snmpTargetAddrTDomain' and 'snmpTargetAddrTAddress' 1) 'snmpTargetAddrTDomain' and 'snmpTargetAddrTAddress'
- target transport protocol and address (equivalent to URI) - target transport protocol and address (equivalent to URI)
2) 'snmpTargetAddressTimeout' and 'snmpTargetAddrRetryCount' 2) 'snmpTargetAddressTimeout' and 'snmpTargetAddrRetryCount'
- retry timeout and limit (for acknowledged notifications - retry timeout and limit (for acknowledged notifications
delivered using SNMP Inform-Request rather than SNMP Trap) delivered using SNMP Inform-Request rather than SNMP Trap)
3) 'snmpTargetAddrTagList' 3) 'snmpTargetAddrTagList'
- tags of notifications to be sent to this target (client) - tags of notifications to be sent to this target (client)
- example value "jmPrinterEventV2Event jmJobEventV2Event" - example "jmDeviceBasicV2Event" or "jmJobBasicV2Event"
4) 'snmpTargetAddrParamsEntry' 4) 'snmpTargetAddrParamsEntry'
- notification security and SNMP protocol version - notification security and SNMP protocol version
5) 'snmpTargetAddrStorageType' 5) 'snmpTargetAddrStorageType'
- row persistence of this registration - row persistence of this registration
3.5. Relationship to other MIBs 3.5. Relationship to other MIBs
3.5.1. IETF Host Resources MIB (RFC 1514) 3.5.1. MIB-II (RFC 1213)
The 'jmPrinterEventV2Event' trap defined in this document includes a All SNMPv1 trap messages include 'time-stamp' which is the value of
'hrDeviceStatus' object for a device of type 'hrDevicePrinter'. The the 'sysUpTime' object from MIB-II [RFC-1213].
'jmPrinterEventV2Event' trap defined in this document includes four
objects from the IETF HR MIB [RFC-1514] in the variable-bindings:
- 'hrDeviceStatus' --> IPP 'printer-state' All SNMPv2 trap bindings include the 'sysUpTime' object from MIB-II
- 'hrPrinterStatus' --> IPP 'printer-state' [RFC-1213].
- 'hrPrinterDetectedErrorState' --> IPP 'printer-state-reasons'
- 'hrSystemDate' --> IPP 'printer-current-time'
3.5.2. IETF Printer MIB (RFC 1759) 3.5.2. Host Resources MIB (RFC 1514)
The 'jmPrinterEventV2Event' trap defined in this document includes a The 'jmDeviceBasicV2Event' trap defined in this document permits
'hrDeviceStatus' object for a device of type 'hrDevicePrinter'. The optional binding of the 'hrDeviceStatus', 'hrDevicePrinterStatus',
appropriate 'hrDeviceIndex' to use in the companion IETF Printer MIB and 'hrPrinterDetectedErrorState' objects from Host Resources MIB
[RFC-1759] is indicated by the instance suffix of the variable's OID. [RFC-1514].
3.5.3. Printer MIB v2 (work-in-progress) 3.5.3. Printer MIB (RFC 1759)
The 'jmPrinterEventV2Event' trap defined in this document includes The 'jmDeviceBasicV2Event' trap defined in this document permits
two objects from the (work-in-progress) Printer MIB v2 [PRT-MIB2] in optional binding of the 'hrDeviceStatus', 'hrDevicePrinterStatus',
the variable-bindings: and 'hrPrinterDetectedErrorState' objects from Host Resources MIB
[RFC-1514].
- 'prtGeneralPrinterName' --> IPP 'printer-name' The appropriate value of 'hrDeviceIndex' to use in the Printer MIB
- 'prtChannelInformation' --> IPP 'printer-uri' [RFC-1759] may be indicated by the instance suffix of the
'hrDeviceStatus' variable's OID.
4. Managed Object Definitions 4. Managed Object Definitions
4.1. Printer Event Trap 4.1. Device Basic Event Trap
-- Printer Event Group (Cond Mandatory) -- Device Basic Event Group (Cond Mandatory)
-- --
-- Implementation of this group is conditionally mandatory; -- Implementation of this group is conditionally mandatory;
-- mandatory for systems which send this Printer event via SNMP. -- mandatory for systems which send this Device event via SNMP.
jmPrinterEventV1Enterprise OBJECT-IDENTITY jmDeviceBasicV1Enterprise OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the enterprise-specific OID in an SNMPv1 trap "The value of the enterprise-specific OID in an SNMPv1 trap
for a 'basic-printer-event' sent by this managed system." for a Device basic event' sent by this managed system."
::= { jobmonMIBNotifications 1 } ::= { jobmonMIBNotifications 1 }
jmPrinterEventV2EventPrefix jmDeviceBasicV2EventPrefix
OBJECT IDENTIFIER ::= { jmPrinterEventV1Enterprise 0 } OBJECT IDENTIFIER ::= { jmDeviceBasicV1Enterprise 0 }
jmPrinterEventV2Event NOTIFICATION-TYPE jmDeviceBasicV2Event NOTIFICATION-TYPE
OBJECTS { OBJECTS {
jmEventTriggerEvent, jmEventTriggerEvent,
jmEventSubscriptionID, jmEventSubscriptionID,
jmEventSubscriberUserName, jmEventSubscriberUserName,
jmEventSubscriberUserData, jmEventSubscriberUserData,
hrDeviceStatus, jmEventDeviceURI,
hrPrinterStatus, jmEventDeviceName,
hrPrinterDetectedErrorState jmEventJobSetIndex,
jmEventJobIndex,
jmEventJobName,
jmEventDeviceState,
jmEventDeviceStateReasons,
jmEventDeviceIsAcceptingJobs
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This SMIv2 trap corresponds to an IPP 'basic-printer-event'. "This SMIv2 trap corresponds to an IPP Printer basic event.
This trap is sent when requested by a prior subscription for This trap is sent when requested by a prior subscription.
the included printer-level 'jmEventTriggerEvent'. The event type is specified in 'jmEventTriggerEvent'.
Additional variable-bindings SHALL be appended to this trap Event types reported via 'jmDeviceBasicV2Event' include:
for all printer-level events: - 'printer-restarted'
- Systems that support 'jobName' SHALL add - 'printer-shutdown'
'jmAttributeValue...jobName.1' (if job-level subscription) - 'printer-state-changed'
- Systems that support 'hrSystemDate' defined in - 'printer-media-changed'
the IETF Host Resources MIB (RFC 1514) SHALL add - 'printer-config-changed'
'hrSystemDate' (corresponds to IPP 'printer-current-time') - 'printer-queue-changed'
- 'printer-no-longer-full'
- 'printer-almost-idle'
- 'device-restarted'
- 'device-shutdown'
- 'device-state-changed'
- 'device-media-changed'
- 'device-config-changed'
- 'device-queue-changed'
- 'device-no-longer-full'
- 'device-almost-idle'
- and (optionally) vendor extension event types
Additional variable-bindings SHOULD be appended to this trap Additional variable-bindings SHOULD be appended to this trap
for all printer-level events: for all device-level events:
- Systems that support the model of printer states defined - Systems with the Host Resources MIB [RFC-1514] SHOULD add
in the (work-in-progress) IPP Model and Semantics [IPP-MOD] 'hrSystemDate'
SHOULD add (compare to IPP 'printer-current-time') and
'jmEventPrinterState' (corresponds to IPP 'printer-state'), 'hrDeviceStatus'
'jmEventPrinterStateReasons' (corresponds to IPP (compare to IPP 'printer-state')
'printer-state-reasons'), and
'jmEventPrinterIsAcceptingJobs' (corresponds to IPP
'printer-is-accepting-jobs')
- Systems that support 'prtChannelInformation' defined in
the (work-in-progress) Printer MIB v2 [PRT-MIB2] SHOULD add
'prtChannelInformation' (corresponds to IPP 'printer-uri')
- Systems that support 'prtGeneralPrinterName' defined in
the (work-in-progress) Printer MIB v2 [PRT-MIB2] SHOULD add
'prtGeneralPrinterName' (compare to IPP 'printer-name')
Systems MAY add other variable-bindings from any MIB." Additional variable-bindings MAY be appended to this trap
::= { jmPrinterEventV2EventPrefix 1 } for all printer-specific events:
- Systems with the Host Resources MIB [RFC-1514] MAY add
'hrPrinterStatus'
(compare to IPP 'printer-state') and
'hrPrinterDetectedErrorState'
(compare to IPP 'printer-state-reasons')
4.2. Job Event Trap Systems MAY add other variable-bindings from any MIB.
-- Job Event Group (Cond Mandatory) See: Section 5.2 'notify-events' of [IPP-NOT];
Section 7 'Notification Content' in [IPP-NOT]."
::= { jmDeviceBasicV2EventPrefix 1 }
4.2. Job Basic Event Trap
-- Job Basic Event Group (Cond Mandatory)
-- --
-- Implementation of this group is conditionally mandatory; -- Implementation of this group is conditionally mandatory;
-- mandatory for systems which send this Job event via SNMP. -- mandatory for systems which send this Job event via SNMP.
jmJobEventV1Enterprise OBJECT-IDENTITY jmJobBasicV1Enterprise OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the enterprise-specific OID in an SNMPv1 trap "The value of the enterprise-specific OID in an SNMPv1 trap
for a 'basic-job-event' sent by this managed system." for a Job basic event sent by this managed system."
::= { jobmonMIBNotifications 2 } ::= { jobmonMIBNotifications 2 }
jmJobEventV2EventPrefix jmJobBasicV2EventPrefix
OBJECT IDENTIFIER ::= { jmJobEventV1Enterprise 0 } OBJECT IDENTIFIER ::= { jmJobBasicV1Enterprise 0 }
jmJobEventV2Event NOTIFICATION-TYPE jmJobBasicV2Event NOTIFICATION-TYPE
OBJECTS { OBJECTS {
jmEventTriggerEvent, jmEventTriggerEvent,
jmEventSubscriptionID, jmEventSubscriptionID,
jmEventSubscriberUserName, jmEventSubscriberUserName,
jmEventSubscriberUserData, jmEventSubscriberUserData,
jmJobState, jmEventDeviceURI,
jmJobStateReasons1 jmEventDeviceName,
jmEventJobSetIndex,
jmEventJobIndex,
jmEventJobName,
jmEventJobState,
jmEventJobStateReasons
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This SMIv2 trap corresponds to an IPP 'basic-job-event'. "This SMIv2 trap corresponds to an IPP Job basic event.
This trap is sent when requested by a prior subscription for This trap is sent when requested by a prior subscription.
the included job-level 'jmEventTriggerEvent'. The event type is specified in 'jmEventTriggerEvent'.
Additional variable-bindings SHALL be appended to this trap Event types reported via 'jmJobBasicV2Event' include:
for all job-level events: - 'job-created'
- Systems that support 'jobName' SHALL add - 'job-state-changed'
'jmAttributeValue...jobName.1' - 'job-config-changed'
- Systems that support 'jobStateReasonsN' SHALL add - 'job-purged'
'jmAttributeValue...jobStateReasonsN.1' - and (optionally) vendor extension event types
- Systems that support 'hrSystemDate' defined in
the IETF Host Resources MIB (RFC 1514) SHALL add Systems MAY add other variable-bindings from any MIB.
'hrSystemDate' (corresponds to IPP 'printer-current-time')
See: Section 5.2 'notify-events' of [IPP-NOT];
Section 7 'Notification Content' in [IPP-NOT]."
::= { jmJobBasicV2EventPrefix 1 }
4.3. Job Completed Event Trap
-- Job Completed Event Group (Cond Mandatory)
--
-- Implementation of this group is conditionally mandatory;
-- mandatory for systems which send this Job event via SNMP.
jmJobCompletedV1Enterprise OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The value of the enterprise-specific OID in an SNMPv1 trap
for a Job completed event sent by this managed system."
::= { jobmonMIBNotifications 3 }
jmJobCompletedV2EventPrefix
OBJECT IDENTIFIER ::= { jmJobCompletedV1Enterprise 0 }
jmJobCompletedV2Event NOTIFICATION-TYPE
OBJECTS {
jmEventTriggerEvent,
jmEventSubscriptionID,
jmEventSubscriberUserName,
jmEventSubscriberUserData,
jmEventDeviceURI,
jmEventDeviceName,
jmEventJobSetIndex,
jmEventJobIndex,
jmEventJobName,
jmEventJobState,
jmEventJobStateReasons,
jmEventJobKOctetsProcessed,
jmEventJobImpressionsCompleted,
jmEventJobMediaSheetsCompleted
}
STATUS current
DESCRIPTION
"This SMIv2 trap corresponds to an IPP 'job-completed' event.
This trap is sent when requested by a prior subscription.
The event type is specified in 'jmEventTriggerEvent'.
Event types reported via 'jmJobCompletedV2Event' include:
- 'job-completed'
- and (optionally) vendor extension event types
Additional variable-bindings SHOULD be appended to this trap Additional variable-bindings SHOULD be appended to this trap
for all job-level events: for all 'job-completed' events:
- Systems that support 'prtChannelInformation' defined in - Systems which support this job information SHOULD add
the (work-in-progress) Printer MIB v2 [PRT-MIB2] SHOULD add 'jmEventJobKOctets'
'prtChannelInformation' (corresponds to IPP 'printer-uri') (compare to IPP 'job-k-octets' job size attribute
- Systems that support 'prtGeneralPrinterName' defined in and to Job Mon MIB 'jobKOctetsTransferred' attribute)
the (work-in-progress) Printer MIB v2 [PRT-MIB2] SHOULD add 'jmEventJobImpressions'
'prtGeneralPrinterName' (corresponds to IPP 'printer-name') (compare to IPP 'job-impressions' job size attribute)
'jmEventJobMediaSheets'
(compare to IPP 'job-media-sheets' job size attribute
and to Job Mon MIB 'sheetsRequested' attribute)
Additional variable-bindings SHALL be appended to this trap Systems MAY add other variable-bindings from any MIB.
for 'jobCompleted', 'jobStateChanged', or 'jobPurged':
- Systems SHALL add
'jmJobKOctetsProcessed'
'jmJobImpressionsCompleted'
- Systems that support 'sheetsCompleted' SHALL add
'jmAttributeValue...sheetsCompleted.1'
Additional variable-bindings SHALL be appended to this trap See: Section 5.2 'notify-events' of [IPP-NOT];
for 'jobProgress': Section 7 'Notification Content' in [IPP-NOT]."
- Systems that support the respective attributes SHALL add ::= { jmJobCompletedV2EventPrefix 1 }
'jmAttributeValue...jobCollationType.1' 4.4. Job Progress Event Trap
'jmAttributeValue...sheetCompletedCopyNumber.1'
'jmAttributeValue...sheetCompletedDocumentNumber.1'
'jmAttributeValue...impressionsInterpreted.1'
'jmAttributeValue...impressionsCompletedCurrentCopy.1'
Systems MAY add other variable-bindings from any MIB." -- Job Progress Event Group (Cond Mandatory)
::= { jmJobEventV2EventPrefix 1 } --
-- Implementation of this group is conditionally mandatory;
-- mandatory for systems which send this Job event via SNMP.
4.3. Event Objects jmJobProgressV1Enterprise OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The value of the enterprise-specific OID in an SNMPv1 trap
for a Job progress event sent by this managed system."
::= { jobmonMIBNotifications 4 }
-- Event Group (Cond Mandatory) jmJobProgressV2EventPrefix
OBJECT IDENTIFIER ::= { jmJobProgressV1Enterprise 0 }
jmJobProgressV2Event NOTIFICATION-TYPE
OBJECTS {
jmEventTriggerEvent,
jmEventSubscriptionID,
jmEventSubscriberUserName,
jmEventSubscriberUserData,
jmEventDeviceURI,
jmEventDeviceName,
jmEventJobSetIndex,
jmEventJobIndex,
jmEventJobName,
jmEventJobState,
jmEventJobStateReasons,
jmEventJobKOctetsProcessed,
jmEventJobImpressionsCompleted,
jmEventJobMediaSheetsCompleted,
jmEventJobImpressionsCompletedCC,
jmEventJobCollationType,
jmEventJobSheetCompletedCopyNum,
jmEventJobSheetCompletedDocNum
}
STATUS current
DESCRIPTION
"This SMIv2 trap corresponds to an IPP 'job-progress' event.
This trap is sent when requested by a prior subscription.
The event type is specified in 'jmEventTriggerEvent'.
Event types reported via 'jmJobProgressV2Event' include:
- 'job-progress'
- and (optionally) vendor extension event types
Additional variable-bindings SHOULD be appended to this trap
for all 'job-progress' events:
- Systems which support this job information SHOULD add
'jmEventJobKOctets'
(compare to IPP 'job-k-octets' job size attribute
and to Job Mon MIB 'jobKOctetsTransferred' attribute)
'jmEventJobImpressions'
(compare to IPP 'job-impressions' job size attribute)
'jmEventJobMediaSheets'
(compare to IPP 'job-media-sheets' job size attribute
and to Job Mon MIB 'sheetsRequested' attribute)
Systems MAY add other variable-bindings from any MIB.
See: Section 5.2 'notify-events' of [IPP-NOT];
Section 7 'Notification Content' in [IPP-NOT]."
::= { jmJobProgressV2EventPrefix 1 }
4.5. Event Binding Group
-- Event Binding Group (Cond Mandatory)
-- --
-- Implementation of this group is conditionally mandatory; -- Implementation of this group is conditionally mandatory;
-- mandatory for systems which send Printer or Job events via SNMP. -- mandatory for systems which send Device or Job events via SNMP.
--
-- Note: All of the objects in this group are defined ONLY for the
-- purpose of providing instantaneous bindings for SNMP traps - it's
-- NEVER suitable for an SNMP Manager to Get these objects directly.
jmEventBinding OBJECT IDENTIFIER ::= { jobmonMIBObjects 5 }
jmEvent OBJECT IDENTIFIER ::= { jobmonMIBObjects 5 }
jmEventTriggerEvent OBJECT-TYPE jmEventTriggerEvent OBJECT-TYPE
SYNTAX JmUTF8StringTC (SIZE (0..63)) -- 255 in [IPP-MOD] SYNTAX JmUTF8StringTC (SIZE (0..63)) -- 255 in [IPP-MOD]
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The trigger event type associated with this event. "The trigger event type associated with this event.
Standard Printer event types defined in [IPP-NOT] are:
- 'printer-restarted'
- 'printer-shutdown'
- 'printer-state-changed'
- 'printer-media-changed'
- 'printer-config-changed'
- 'printer-queue-changed'
- 'printer-no-longer-full'
- 'printer-almost-idle'
Standard Device event types generalized from [IPP-NOT] are:
- 'device-restarted'
- 'device-shutdown'
- 'device-state-changed'
- 'device-media-changed'
- 'device-config-changed'
- 'device-queue-changed'
- 'device-no-longer-full'
- 'device-almost-idle'
Standard Job event types defined in [IPP-NOT] are:
- 'job-created'
- 'job-completed'
- 'job-state-changed'
- 'job-config-changed'
- 'job-purged'
- 'job-progress'
Conformance: The natural language for keywords Conformance: The natural language for keywords
in trigger event type SHALL always be US English. in trigger event type SHALL always be US English.
Conformance: This trigger event type SHALL be valid. Conformance: This trigger event type SHALL be valid
and reported in ALL Job Monitoring MIB notifications.
See: Section 5.2 'notify-events' and See: Section 5.2 'notify-events' and
Section 7 'Notification Content' in [IPP-NOT]." Section 7 'Notification Content' in [IPP-NOT]."
-- DEFVAL intentionally omitted - reported value SHALL be valid -- DEFVAL intentionally omitted - reported value SHALL be valid
::= { jmEvent 1 } ::= { jmEventBinding 1 }
jmEventSubscriptionID OBJECT-TYPE jmEventSubscriptionID OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The subscription identifier associated with this event "The subscription identifier associated with this event
or zero (if none). or zero (if none).
Conformance: This subscription identifier SHALL be valid Conformance: This subscription identifier SHALL be valid
and non-zero, if available on this managed system. and reported, if available on this managed system.
See: Section 5.8 'subscription-id' and See: Section 5.8 'subscription-id' and
Section 7 'Notification Content' in [IPP-NOT]." Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { 0 } -- no subscription ID DEFVAL { 0 } -- no subscription ID
::= { jmEvent 2 } ::= { jmEventBinding 2 }
jmEventSubscriberUserName OBJECT-TYPE jmEventSubscriberUserName OBJECT-TYPE
SYNTAX JmUTF8StringTC (SIZE (0..63)) -- 1023 in [IPP-MOD] SYNTAX JmUTF8StringTC (SIZE (0..63)) -- 1023 in [IPP-MOD]
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The subscriber user name associated with this event "The subscriber user name associated with this event
or the empty string (if none). or the empty string (if none).
Note: The natural language appropriate for text-to-speech Note: The natural language appropriate for text-to-speech
of subscriber user name is orthogonal to the localized text of subscriber user name is orthogonal to the localized text
context in IPP 'attributes-natural-language'. The subscriber context in IPP 'attributes-natural-language'. The subscriber
user name MAY include an in-line 'language tag' using Plane user name MAY include an in-line 'language tag' using Plane
14 'language tag' characters approved for ISO 10646/Unicode. 14 'language tag' characters approved for ISO 10646/Unicode.
Conformance: This subscriber user name SHALL be valid Conformance: This subscriber user name SHALL be valid
and conserved, if available on this managed system. and reported, if available on this managed system.
See: 'Language Tagging in Unicode Plain Text', RFC 2482 See: 'Language Tagging in Unicode Plain Text', RFC 2482
(January 1999); (January 1999);
'Plane 14 Characters for Language Tags', Unicode 'Plane 14 Characters for Language Tags', Unicode
Technical Report #7 (January 1999); Technical Report #7 (January 1999);
Section 4.3.6 'job-originating-user-name' and Section 4.3.6 'job-originating-user-name' and
Section 4.4.2 'uri-authentication-supported' Section 4.4.2 'uri-authentication-supported'
(usage of 'requesting-user-name') in [IPP-MOD]; (usage of 'requesting-user-name') in [IPP-MOD];
Section 5.11 'subscriber-user-name' and Section 5.11 'subscriber-user-name' and
Section 7 'Notification Content' in [IPP-NOT]." Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { ''H } -- no subscriber user name DEFVAL { ''H } -- no subscriber user name
::= { jmEvent 3 } ::= { jmEventBinding 3 }
jmEventSubscriberUserData OBJECT-TYPE jmEventSubscriberUserData OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..63)) -- 63 in [IPP-NOT] SYNTAX OCTET STRING (SIZE (0..63)) -- 63 in [IPP-NOT]
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The subscriber user data associated with this event "The subscriber user data associated with this event
or the empty string (if none). or the empty string (if none).
Conformance: This subscriber user data SHALL be valid Conformance: This subscriber user data SHALL be valid
and conserved, if available on this managed system. and reported, if available on this managed system.
See: Section 5.4 'subscriber-user-data' and See: Section 5.4 'subscriber-user-data' and
Section 7 'Notification Content' in [IPP-NOT]." Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { ''H } -- no subscriber user data DEFVAL { ''H } -- no subscriber user data
::= { jmEvent 4 } ::= { jmEventBinding 4 }
jmEventPrinterState OBJECT-TYPE jmEventDeviceURI OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..31)) -- 255 in [IPP-MOD] SYNTAX OCTET STRING (SIZE (0..255)) -- 1023 in [IPP-MOD]
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The printer state associated with this event "The device URI associated with this event
or the empty string (if none). or the empty string (if none).
Note: This object uses the keywords from the [IPP-MOD] Conformance: This device URI SHALL be valid
enumerated type 'printer-state', to avoid adding a new and reported, if available on this managed system.
textual convention to the PWG Job Monitoring MIB [PWG-JOB].
Conformance: The natural language for keywords See: Section 4.3.3 'job-printer-uri' in [IPP-MOD];
in printer state SHALL always be US English. Section 4.4.1 'printer-uri-supported' in [IPP-MOD];
Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { ''H } -- no device URI
::= { jmEventBinding 5 }
Conformance: This printer state SHALL be valid jmEventDeviceName OBJECT-TYPE
and non-empty, if available on this managed system. SYNTAX OCTET STRING (SIZE (0..127)) -- 127 in [IPP-MOD]
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The device name associated with this event
or the empty string (if none).
Conformance: This device name SHALL be valid
and reported, if available on this managed system.
See: Section 4.4.4 'printer-name' in [IPP-MOD];
Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { ''H } -- no device name
::= { jmEventBinding 6 }
jmEventDeviceState OBJECT-TYPE
SYNTAX INTEGER { -- enum in [IPP-MOD]
unknown(2), -- unknown device state
idle(3),
processing(4),
stopped(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The device state associated with this event
or 'unknown'.
Note: This object uses the keywords from the [IPP-MOD]
enumerated type 'printer-state' for coherence.
Conformance: This device state SHALL be valid
and reported, if available on this managed system.
See: Section 4.4.11 'printer-state' in [IPP-MOD]; See: Section 4.4.11 'printer-state' in [IPP-MOD];
Section 7 'Notification Content' in [IPP-NOT]." Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { ''H } -- no printer state DEFVAL { unknown } -- unknown device state
::= { jmEvent 5 } ::= { jmEventBinding 7 }
jmEventPrinterStateReasons OBJECT-TYPE
jmEventDeviceStateReasons OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..255)) -- 255*n in [IPP-MOD] SYNTAX OCTET STRING (SIZE (0..255)) -- 255*n in [IPP-MOD]
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The printer state reasons associated with this event "The device state reasons associated with this event
(as a comma-separated list) or the empty string (if none). (as a comma-separated list) or the empty string (if none).
Conformance: The natural language for keywords Conformance: The natural language for keywords
in printer state reasons SHALL always be US English. in device state reasons SHALL always be US English.
Conformance: These printer state reasons SHALL be valid Conformance: These device state reasons SHALL be valid
and conserved, if available on this managed system. and reported, if available on this managed system.
See: Section 4.4.12 'printer-state-reasons' in [IPP-MOD]; See: Section 4.4.12 'printer-state-reasons' in [IPP-MOD];
Section 7 'Notification Content' in [IPP-NOT]." Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { ''H } -- no printer state reasons DEFVAL { ''H } -- no device state reasons
::= { jmEvent 6 } ::= { jmEventBinding 8 }
jmEventPrinterIsAcceptingJobs OBJECT-TYPE jmEventDeviceIsAcceptingJobs OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The printer substate associated with this event "The device substate associated with this event
or 'true' (if unknown). or 'true' (if unknown).
Conformance: This printer substate SHALL be valid Conformance: This device substate SHALL be valid
and conserved, if available on this managed system. and reported, if available on this managed system.
See: Section 4.4.23 'printer-is-accepting-jobs' See: Section 4.4.23 'printer-is-accepting-jobs'
in [IPP-MOD]; in [IPP-MOD];
Section 7 'Notification Content' in [IPP-NOT]." Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { true } -- printer is accepting jobs DEFVAL { true } -- device is accepting jobs
::= { jmEvent 7 } ::= { jmEventBinding 9 }
jmEventJobSetIndex OBJECT-TYPE
SYNTAX Integer32 (0..32767)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The job set index associated with this event
or zero (if none).
Conformance: This job set index SHALL be valid
and reported, if available on this managed system.
See: 'jmGeneralJobSetIndex' object in [RFC-2707];
Section 4.3.2 'job-id' in [IPP-MOD];
Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { 0 } -- no job set index
::= { jmEventBinding 10 }
jmEventJobIndex OBJECT-TYPE
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The job index associated with this event
or zero (if none).
Conformance: This job index SHALL be valid
and reported, if available on this managed system.
See: 'jmJobIndex' object in [RFC-2707];
Section 4.3.2 'job-id' in [IPP-MOD];
Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { 0 } -- no job index
::= { jmEventBinding 11 }
jmEventJobName OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..255)) -- 255 in [IPP-MOD]
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The job name associated with this event
or the empty string (if none).
Conformance: This job name SHALL be valid
and reported, if available on this managed system.
See: 'jobName' attribute in [RFC-2707];
Section 4.3.5 'job-name' in [IPP-MOD];
Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { ''H } -- no job name
::= { jmEventBinding 12 }
jmEventJobState OBJECT-TYPE
SYNTAX INTEGER { -- enum in [IPP-MOD]
unknown(2), -- unknown job state
pending(3),
pendingHeld(4),
processing(5),
processingStopped(6),
canceled(7),
aborted(8),
completed(9)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The job state associated with this event
or 'unknown'.
Note: This object uses the keywords from the [IPP-MOD]
enumerated type 'job-state' for coherence.
Conformance: This job state SHALL be valid
and reported, if available on this managed system.
See: 'jmJobState' object in [RFC-2707];
Section 4.3.7 'job-state' in [IPP-MOD];
Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { unknown } -- unknown job state
::= { jmEventBinding 13 }
jmEventJobStateReasons OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..255)) -- 255*n in [IPP-MOD]
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The job state reasons associated with this event
(as a comma-separated list) or the empty string (if none).
Conformance: The natural language for keywords
in job state reasons SHALL always be US English.
Conformance: These job state reasons SHALL be valid
and reported, if available on this managed system.
See: 'jmJobStateReasons1' object in [RFC-2707];
'jobStateReasons2', 'jobStateReasons3', and
'jobStateReasons4' attributes in [RFC-2707];
Section 4.3.8 'job-state-reasons' in [IPP-MOD];
Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { ''H } -- no job state reasons
::= { jmEventBinding 14 }
jmEventJobKOctets OBJECT-TYPE
SYNTAX Integer32 (-2..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The job size in K octets associated with this event
or zero (if none) or '-2' (if unknown).
Conformance: This job size SHALL be valid
and reported, if available on this managed system.
See: 'jobKOctetsTransferred' attribute in [RFC-2707];
Section 4.3.17.1 'job-k-octets' in [IPP-MOD];
Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { -2 } -- unknown job size
::= { jmEventBinding 15 }
jmEventJobKOctetsProcessed OBJECT-TYPE
SYNTAX Integer32 (-2..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The job progress in K octets associated with this event
or zero (if none) or '-2' (if unknown).
Conformance: This job progress SHALL be valid
and reported, if available on this managed system.
See: 'jmJobKOctetsProcessed' object in [RFC-2707];
Section 4.3.18.1 'job-k-octets-processed'
in [IPP-MOD];
Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { -2 } -- unknown job progress
::= { jmEventBinding 16 }
jmEventJobImpressions OBJECT-TYPE
SYNTAX Integer32 (-2..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The job size in impressions associated with this event
or zero (if none) or '-2' (if unknown).
Conformance: This job size SHALL be valid
and reported, if available on this managed system.
See: Section 4.3.17.2 'job-impressions' in [IPP-MOD];
Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { -2 } -- unknown job size
::= { jmEventBinding 17 }
jmEventJobImpressionsCompleted OBJECT-TYPE
SYNTAX Integer32 (-2..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The job progress in impressions associated with this event
or zero (if none) or '-2' (if unknown).
Conformance: This job progress SHALL be valid
and reported, if available on this managed system.
See: 'jmJobImpressionsCompleted' object in [RFC-2707];
Section 4.3.18.2 'job-impressions-completed'
in [IPP-MOD];
Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { -2 } -- unknown job progress
::= { jmEventBinding 18 }
jmEventJobMediaSheets OBJECT-TYPE
SYNTAX Integer32 (-2..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The job size in media sheets associated with this event
or zero (if none) or '-2' (if unknown).
Conformance: This job size SHALL be valid
and reported, if available on this managed system.
See: 'sheetsRequested' attribute in [RFC-2707];
Section 4.3.17.3 'job-media-sheets' in [IPP-MOD];
Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { -2 } -- unknown job size
::= { jmEventBinding 19 }
jmEventJobMediaSheetsCompleted OBJECT-TYPE
SYNTAX Integer32 (-2..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The job progress in media sheets associated with this event
or zero (if none) or '-2' (if unknown).
Conformance: This job progress SHALL be valid
and reported, if available on this managed system.
See: 'sheetsCompleted' attribute in [RFC-2707];
Section 4.3.18.3 'job-media-sheets-completed'
in [IPP-MOD];
Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { -2 } -- unknown job progress
::= { jmEventBinding 20 }
jmEventJobImpressionsCompletedCC OBJECT-TYPE
SYNTAX Integer32 (-2..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The job progress in impressions completed
on the current copy associated with this event
or zero (if none) or '-2' (if unknown).
Conformance: This job progress SHALL be valid
and reported, if available on this managed system.
See: 'jmJobImpressionsCompleted' object in [RFC-2707];
'impressions-completed-current-copy' in [IPP-PROG];
Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { unknown } -- unknown job progress
::= { jmEventBinding 21 }
jmEventJobCollationType OBJECT-TYPE
SYNTAX JmJobCollationTypeTC
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The job collation type associated with this event
or 'unknown' (if unknown).
Conformance: This job collation type be valid
and reported, if available on this managed system.
See: 'jobCollationType' attribute in [RFC-2707];
'job-collation-type' in [IPP-PROG];
Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { unknown } -- unknown job collation type
::= { jmEventBinding 22 }
jmEventJobSheetCompletedCopyNum OBJECT-TYPE
SYNTAX Integer32 (-2..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The job progress number of the copy currently being
stacked for the document associated with this event
or zero (if none) or '-2' (if unknown).
Conformance: This job progress SHALL be valid
and reported, if available on this managed system.
See: 'sheetCompletedCopyNumber' attribute
in [RFC-2707];
'sheet-completed-copy-number' in [IPP-PROG];
Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { -2 } -- unknown copy number
::= { jmEventBinding 23 }
jmEventJobSheetCompletedDocNum OBJECT-TYPE
SYNTAX Integer32 (-2..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The job progress number of the document currently being
stacked associated with this event
or zero (if none) or '-2' (if unknown).
Conformance: This job progress SHALL be valid
and reported, if available on this managed system.
See: 'sheetCompletedDocumentNumber' attribute
in [RFC-2707];
'sheet-completed-document-number' in [IPP-PROG];
Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { -2 } -- unknown document number
::= { jmEventBinding 24 }
5. IANA Considerations 5. IANA Considerations
None - no enumerated textual conventions are defined in this None.
document.
6. Internationalization Considerations 6. Internationalization Considerations
The 'jmEventTriggerEvent', 'jmEventPrinterState', and The 'jmEventTriggerEvent', 'jmEventDeviceState', and
'jmEventPrinterStateReasons' text objects defined in this document 'jmEventDeviceStateReasons' text objects defined in this document are
are of type 'JmUTF8StringTC' (UTF-8 stream-encoded ISO 10646/Unicode of type 'JmUTF8StringTC' (UTF-8 stream-encoded ISO 10646/Unicode
text) defined in the PWG Job Monitoring MIB [PWG-JOB]. The natural text) defined in the Job Monitoring MIB [RFC-2707]. The natural
language of these objects is US English. language of these objects is US English.
The 'jmEventSubscriberUserName' text object defined in this document The 'jmEventSubscriberUserName' text object defined in this document
is of type 'JmUTF8StringTC' (UTF-8 stream-encoded ISO 10646/Unicode is of type 'JmUTF8StringTC' (UTF-8 stream-encoded ISO 10646/Unicode
text) defined in the PWG Job Monitoring MIB [PWG-JOB]. The natural text) defined in the Job Monitoring MIB [RFC-2707]. The natural
language of this object is inherently ambiguous (as it usually language of this object is inherently ambiguous (as it usually
contains some transform of a personal name). contains some transform of a personal name).
7. Security Considerations 7. Security Considerations
This IPP Notifications over SNMP mapping defines only 'read-only' This IPP Notifications over SNMP mapping defines only 'read-only'
objects. It is suitable for use with any version of SNMP, as no objects. It is suitable for use with any version of SNMP, as no
update security is required (because no configuration updates are update security is required (because no configuration updates are
supported). supported).
No sensitive information is available via IPP Notifications over No sensitive information is available via IPP Notifications over
SNMP. SNMP.
8. References 8. References
To be supplied. [IPP-MOD] R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell.
IPP/1.1 Model and Semantics, <draft-ietf-ipp-model-v11-06.txt>
(work-in-progress), March 2000.
[IPP-NOT] S. Isaacson, J. Martin, R. deBry, T. Hastings, M. Shepherd,
R. Bergman. IPP Event Notification Specification,
<draft-ietf-ipp-not-spec-02.txt> (work-in-progress), March 2000.
[IPP-PROG] T. Hastings, R. Bergman, H. Lewis. Proposed Job Progress
Attributes for IPP, <draft-ietf-ipp-job-prog.txt> (work-in-progress),
February 2000.
[RFC-1213] K. McCloghrie, M. Rose. MIB-II, RFC 1213, March 1991.
[RFC-1514] P. Grillo, S. Waldbusser. Host Resources MIB, RFC 1514,
September 1993.
[RFC-1759] R. Smith, F. Wright, T. Hastings, S. Zilles,
J. Gyllenskog. Printer MIB, RFC 1759, March 1995.
[RFC-2573] D. Levi, P. Meyer, B. Stewart. SNMP Applications, RFC
2573, April 1999.
[RFC-2576] R. Frye, D. Levi, S. Routhier, B. Wijnen. Coexistence
between Version 1, Version 2, and Version 3 of the Internet-standard
Network Management Framework, RFC 2576, March 2000.
[RFC-2707] R. Bergman, T. Hastings, S. Isaacson, H. Lewis. Job
Monitoring MIB v1.0, RFC 2707, November 1999
9. Change Log 9. Change Log
Changes in reverse chronological order (most recent first). Changes in reverse chronological order (most recent first).
<draft-ietf-ipp-not-over-snmp-02.txt> - 19 March 2000
1) Renamed Printer Event notification group to Device Basic Event
and 'jmPrinterEventV2Event' notification to
'jmDeviceBasicV2Event', to better align with IPP and to support
non-printing jobs.
2) Revised 'jmDeviceBasicV2Event' notification to remove
'hrDeviceStatus', 'hrPrinterStatus',
'hrPrinterDetectedErrorState' from mandatory trap bindings
because they were redundant, per request of Ron Bergman.
3) Renamed Job Event notification group to Job Basic Event and
'jmJobEventV2Event' notification to 'jmJobBasicV2Event', to
better align with IPP and to support variant job events.
4) Defined new Job Completed Event notification group and defined
new Job Progress Event notification group, to better align with
IPP and to support variant job events.
5) Renamed Event object group to Event Binding,
'jmEventPrinterState' to 'jmEventDeviceState',
'jmEventPrinterStateReasons' to 'jmEventDeviceStateReasons',
'jmEventPrinterIsAcceptingJobs' to
'jmEventDeviceIsAcceptingJobs', to support non-printing jobs.
6) Revised Event Binding object group, adding explicit objects
'jmEventDeviceURI', 'jmEventDeviceName', 'jmEventJobSetIndex',
'jmEventJobIndex', 'jmEventJobName', 'jmEventJobState',
'jmEventJobStateReasons', 'jmEventJobKOctets',
'jmEventJobKOctetsProcessed', 'jmEventJobImpressions',
'jmEventJobImpressionsCompleted', 'jmEventJobMediaSheets',
'jmEventJobMediaSheetsCompleted',
'jmEventJobImpressionsCompletedCC', 'jmEventJobCollationType',
'jmEventJobSheetCompletedCopyNum',
'jmEventJobSheetCompletedDocNum', per request of Ron Bergman.
7) Revised SYNTAX of 'jmEventTriggerEvent' object from from
'JmUTF8StringTC' (string) to IPP-aligned enumeration, per request
of Ron Bergman.
8) Removed all references to Printer MIB v2, as they were of limited
value, per request of Ron Bergman.
9) Revised 'SNMP Mapping for IPP Printer Events' section for renamed
event binding objects, per request of Ron Bergman.
10) Revised 'Rules for Encoding Notifications' section to truncate
additional string bindings, per request of Ron Bergman.
11) Revised 'Registration via IPP' section, to change scheme name
from 'ipp-snmp:' to 'snmpnotify:', per request of Ron Bergman.
<draft-ietf-ipp-not-over-snmp-01.txt> - 1 December 1999 <draft-ietf-ipp-not-over-snmp-01.txt> - 1 December 1999
1) Deleted 'JmTriggerEventTC' textual convention (see below). 1) Deleted 'JmTriggerEventTC' textual convention (see below).
2) Revised SYNTAX of 'jmEventTriggerEvent' object from 2) Revised SYNTAX of 'jmEventTriggerEvent' object from
'JmTriggerEventTC' (enumeration) to 'JmUTF8StringTC' (string), to 'JmTriggerEventTC' (enumeration) to 'JmUTF8StringTC' (string), to
support use of IPP standard keywords. support use of IPP standard keywords.
3) Added 'jmEventPrinterState', 'jmEventPrinterStateReasons', and 3) Added 'jmEventPrinterState', 'jmEventPrinterStateReasons', and
'jmEventPrinterIsAcceptingJobs' objects for consistency w/ 'jmEventPrinterIsAcceptingJobs' objects for consistency w/
[IPP-NOT] and to reduce ambiguity about printer states inherent [IPP-NOT] and to reduce ambiguity about printer states inherent
in RFC 1759. in RFC 1759.
4) Revised DESCRIPTION of 'jmPrinterEventV2Event' notification to 4) Revised DESCRIPTION of 'jmPrinterEventV2Event' notification to
add SHOULD (recommendation) for 'jmEventPrinterState', add SHOULD (recommendation) for 'jmEventPrinterState',
'jmEventPrinterStateReasons', and 'jmEventPrinterIsAcceptingJobs' 'jmEventPrinterStateReasons', and 'jmEventPrinterIsAcceptingJobs'
skipping to change at page 17, line 7 skipping to change at page 31, line 7
Ira McDonald Ira McDonald
High North Inc High North Inc
221 Ridge Ave 221 Ridge Ave
Grand Marais, MI 49839 Grand Marais, MI 49839
Phone: +1 906-494-2434 or +1 906-494-2697 Phone: +1 906-494-2434 or +1 906-494-2697
Email: imcdonald@sharplabs.com Email: imcdonald@sharplabs.com
12. Full Copyright Statement 12. Full Copyright Statement
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/