draft-ietf-ipp-not-over-snmp-02.txt   draft-ietf-ipp-not-over-snmp-03.txt 
Internet Printing Protocol Working Group Tom Hastings Internet Printing Protocol Working Group Tom Hastings
INTERNET DRAFT Xerox INTERNET DRAFT Xerox
Expires 19 September 2000 Ira McDonald Expires 6 January 2001 Ira McDonald
High North High North
19 March 2000 6 July 2000
Internet Printing Protocol (IPP): Internet Printing Protocol (IPP):
Notifications over SNMP via Job Monitoring MIB Notifications over SNMP via Job Monitoring MIB Traps
<draft-ietf-ipp-not-over-snmp-02.txt> <draft-ietf-ipp-not-over-snmp-03.txt>
Copyright (C) The Internet Society (2000). 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.
skipping to change at page 1, line 41 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 via This document proposes a mapping of IPP notifications over SNMP via
new device and job traps extensions defined for the Job Monitoring new service and job trap extensions defined for the Job Monitoring
MIB [RFC-2707]. This mapping may be used to deliver printer MIB [RFC-2707]. This mapping may be used to deliver printer
notifications for any printer (not just IPP-capable ones) and also notifications for any printer (not just IPP-capable ones) and 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: (4) SNMP traps; and (24) SNMP leaf objects This document proposes (4) new object groups and (4) new SNMP traps
(for use in various trap bindings). for addition to the Job Monitoring MIB [RFC 2707]. A working copy of
this proposal integrated into the original Job Monitoring MIB ASN.1
is at:
ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/jmp-trap-000706.mib
Table of Contents Table of Contents
1. Introduction ............................................... 4 1. Introduction ............................................... 3
1.1. Terminology for Conformance ............................ 4 1.1. Terminology for Conformance ............................ 3
2. SNMP Network Management Framework .......................... 4 2. SNMP Network Management Framework .......................... 3
3. Managed Object Mapping ..................................... 5 3. Managed Object Mapping ..................................... 4
3.1. SNMP Mapping for IPP Printer Events .................... 5 3.1. SNMP Mapping for IPP Notifications ..................... 4
3.2. SNMP Mapping for IPP Job Events ........................ 5 3.1.1. SNMP Mapping for IPP Printer Events ................ 4
3.3. Rules for Encoding Notifications ....................... 6 3.1.2. SNMP Mapping for IPP Job Events .................... 5
3.4. Registration for IPP Notifications ..................... 7 3.2. Subscription for IPP Notifications ..................... 6
3.4.1. Registration via IPP ............................... 7 3.2.1. Subscription via IPP ............................... 6
3.4.2. Registration via SNMP .............................. 7 3.2.2. Subscription via SNMP .............................. 6
3.5. Relationship to other MIBs ............................. 8 3.3. Relationship to other MIBs ............................. 7
3.5.1. MIB-II (RFC 1213) .................................. 8 3.3.1. MIB-II (RFC 1213) .................................. 7
3.5.2. Host Resources MIB (RFC 1514) ...................... 8 3.3.2. Host Resources MIB (RFC 2790) ...................... 7
3.5.3. Printer MIB (RFC 1759) ............................. 8 3.3.3. Printer MIB (RFC 1759) ............................. 7
4. Managed Object Definitions ................................. 9 4. Managed Object Definitions ................................. 8
4.1. Device Basic Event Trap ................................ 9 4.1. Notification Definitions ............................... 8
4.1.1. jmDeviceBasicV2Event (notification) ................ 9 4.1.1. Service Basic Event - Trap ......................... 8
4.2. Job Basic Event Trap ................................... 10 4.1.2. Job Basic Event - Trap ............................. 9
4.2.1. jmJobBasicV2Event (notification) ................... 11 4.1.3. Job Completed Event - Trap ......................... 11
4.3. Job Completed Event Trap ............................... 11 4.1.4. Job Progress Event - Trap .......................... 12
4.3.1. jmJobCompletedV2Event (notification) ............... 12 4.2. Object Definitions ..................................... 13
4.4. Job Progress Event Trap ................................ 13 4.2.1. Service Group - Objects ............................ 13
4.4.1. jmJobProgressV2Event (notification) ................ 13 4.2.2. Service Event Group - Objects ...................... 16
4.5. Event Binding Group .................................... 14 4.2.3. Job Event Group - Objects .......................... 19
4.5.1. jmEventTriggerEvent (object) ....................... 14 4.2.4. Job Progress Group - Objects ....................... 22
4.5.2. jmEventSubscriptionID (object) ..................... 15 5. IANA Considerations ........................................ 24
4.5.3. jmEventSubscriberUserName (object) ................. 15 6. Internationalization Considerations ........................ 24
4.5.4. jmEventSubscriberUserData (object) ................. 16 7. Security Considerations .................................... 24
4.5.5. jmEventDeviceURI (object) .......................... 16 8. References ................................................. 25
4.5.6. jmEventDeviceName (object) ......................... 17 9. Change Log ................................................. 26
4.5.7. jmEventDeviceState (object) ........................ 17
4.5.8. jmEventDeviceStateReasons (object) ................. 17
4.5.9. jmEventDeviceIsAcceptingJobs (object) .............. 18
4.5.10. jmEventJobSetIndex (object) ....................... 18
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 10. Intellectual Property Notice .............................. 29
11. Authors' Addresses ........................................ 29 11. Authors' Addresses ........................................ 29
12. Full Copyright Statement .................................. 30 12. Full Copyright Statement .................................. 30
1. Introduction 1. Introduction
This document is a submission to the Internet Printing Protocol
Working Group of the Internet Engineering Task Force (IETF).
Comments should be submitted to the ipp@pwg.org mailing list.
This document proposes a mapping of IPP notifications over SNMP via
new service and job trap extensions defined for the Job Monitoring
MIB [RFC-2707]. This mapping may be used to deliver printer
notifications for any printer (not just IPP-capable ones) and also
job notifications for any job (not just ones submitted via IPP).
This document proposes (4) new object groups and (4) new SNMP traps
for addition to the Job Monitoring MIB [RFC 2707]. A working copy of
this proposal integrated into the original Job Monitoring MIB ASN.1
is at:
ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/jmp-trap-000706.mib
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 document proposes support for dynamic monitoring of IPP Printer
of IPP Printer and Job objects, via server generation of SNMP traps. and Job objects via SNMP traps generated by the service provider
(server or device).
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.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 [RFC-2576]. '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 Notifications
3.1.1. SNMP Mapping for IPP Printer Events
IPP Printer event attribute Job Monitoring 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 each generated trap] status-code [implicit in each generated trap]
request-id [request-id in SNMP trap header] notify-sequence-number [request-id in SNMP trap header]
attributes-charset [no mapping - strings are UTF-8] notify-charset [no mapping - strings are UTF-8]
attributes-natural-language [no mapping - no text bindings] notify-natural-language [no mapping - no text bindings]
printer-uri jmEventDeviceURI subscription-id [no mapping]
printer-name jmEventDeviceName notify-subscribed-event jmServiceEventNotifyEvent
job-id jmEventJobIndex notify-printer-uri jmServiceURI
[and jmEventJobSetIndex] printer-up-time [sysUpTime in SNMP trap bindings]
job-name jmEventJobName printer-current-time [hrSystemDate in Host Res MIB]
trigger-event jmEventTriggerEvent notify-user-data [no mapping]
trigger-time [sysUpTime in SNMP trap bindings] notify-text [no mapping]
trigger-date-time [hrSystemDate in Host Res MIB] printer-state jmServiceState
subscription-id jmEventSubscriptionID printer-state-reasons jmServiceStateReasons
subscriber-user-name jmEventSubscriberUserName printer-is-accepting-jobs [jmServiceStateReasons keyword]
subscriber-user-data jmEventSubscriberUserData 3.1.2. SNMP Mapping for IPP Job Events
printer-state jmEventDeviceState
printer-state-reasons jmEventDeviceStateReasons
printer-is-accepting-jobs jmEventDeviceIsAcceptingJobs
3.2. SNMP Mapping for IPP Job Events
IPP Job event attribute Job Monitoring 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 each generated trap] status-code [implicit in each generated trap]
request-id [request-id in SNMP trap header] notify-sequence-number [request-id in SNMP trap header]
attributes-charset [no mapping - strings are UTF-8] notify-charset [no mapping - strings are UTF-8]
attributes-natural-language [no mapping - no text bindings] notify-natural-language [no mapping - no text bindings]
printer-uri jmEventDeviceURI subscription-id [no mapping]
printer-name jmEventDeviceName notify-subscribed-event jmJobEventNotifyEvent
job-id jmEventJobIndex notify-printer-uri jmServiceURI
[and jmEventJobSetIndex] job-id [via jmJobState OID instance]
job-name jmEventJobName printer-up-time [sysUpTime in SNMP trap bindings]
trigger-event jmEventTriggerEvent printer-current-time [hrSystemDate in Host Res MIB]
trigger-time [sysUpTime in SNMP trap bindings] notify-user-data [no mapping]
trigger-date-time [hrSystemDate in Host Res MIB] notify-text [no mapping]
subscription-id jmEventSubscriptionID job-state jmJobState
subscriber-user-name jmEventSubscriberUserName job-state-reasons jmJobEventJobStateReasons
subscriber-user-data jmEventSubscriberUserData [jmJobStateReasons1 plus zero or]
job-state jmEventJobState [more jobStateReasonsN in a strin
job-state-reasons jmEventJobStateReasons
[job-completed - extra bindings] [job-completed and job-purged - extra bindings]
job-k-octets jmEventJobKOctets job-k-octets-processed jmJobKOctetsProcessed
job-k-octets-processed jmEventJobKOctetsProcessed job-impressions-completed jmJobImpressionsCompleted
job-impressions jmEventJobImpressions
job-impressions-completed jmEventJobImpressionsCompleted
job-media-sheets jmEventJobMediaSheets
job-media-sheets-completed jmEventJobMediaSheetsCompleted
[job-progress - extra bindings] [job-progress - extra bindings]
impressions-completed-current-copy jmEventJobImpressionsCompletedCC job-k-octets jmJobKOctetsPerCopyRequested
job-collation-type jmEventJobCollationType job-impressions jmJobImpressionsPerCopyRequested
sheet-completed-copy-number jmEventJobSheetCompletedCopyNum job-copies jmProgressJobCopiesRequested
sheet-completed-document-number jmEventJobSheetCompletedDocNum job-collation-type jmProgressJobCollationType
3.3. Rules for Encoding Notifications job-media-sheets-completed jmProgressMediaSheetsCompleted
sheet-completed-copy-number jmProgressSheetCompletedCopyNum
sheet-completed-document-number jmProgressSheetCompletedDocNum
3.2. Subscription for IPP Notifications
Over some transports and/or media, the variable-bindings of these IPP Clients MAY subscribe for IPP Notifications delivered via SNMP by
SNMP traps MAY not fit the MTU (maximum transmission unit) size. either of the following two standard methods:
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 3.2.1. Subscription via IPP
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:
- 'jmEventSubscriberUserName'
- 'jmEventSubscriberUserData'
- 'jmEventDeviceURI'
- 'jmEventDeviceName'
- 'jmEventDeviceStateReasons'
- 'jmEventJobName'
- 'jmEventJobStateReasons'
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).
3.4. Registration for IPP Notifications IPP Job creation (Create-Job, Print-Job, Print-URI) and
Create-Subscription operations MAY be used to create per-Printer or
per-Job IPP Subscription objects and MAY specify
IPP Clients may register for IPP Notifications delivered via SNMP by "notify-recipient-uri" = 'snmpnotify://hostname[.port]'
either of the following methods:
3.4.1. Registration via IPP "notify-events" = <events of interest, e.g., 'job-completed'>
IPP Create-Subscription and Job creation (Create-Job, Print-Job, 3.2.2. Subscription via SNMP
Print-URI) operations MAY be used to create per-Printer or per-Job
IPP Subscription objects and MAY specify
'notify-recipient' = 'snmpnotify://hostname[.port]' The SNMP Notification MIB and SNMP Target MIB (both in [RFC-2573])
3.4.2. Registration via SNMP MAY be used to create SNMP subscriptions.
SNMP Set-Request operations MAY be used to create appropriate rows in To create a subscription via SNMP, the IPP Client MAY use an SNMP
the SNMP Notification MIB defined in [RFC-2573] and MAY specify: Set-Request operation to create an appropriate row in the SNMP
Notification MIB with the following variable-bindings:
1) 'snmpNotifyTag' 1) 'snmpNotifyTag'
- tag of this notification - see 'snmpTargetAddrTagList' below - tag of this notification - see 'snmpTargetAddrTagList' below
- example "jmDeviceBasicV2Event" or "jmJobBasicV2Event"
2) 'snmpNotifyType' 2) 'snmpNotifyType'
- notification sent using either SNMP Trap (unacknowledged) - deliver via SNMP Trap (unacknowledged) or Inform (acknowledged)
or SNMP Inform-Request (acknowledged)
3) 'snmpNotifyStorageType' 3) 'snmpNotifyStorageType'
- row persistence of this registration - persistence (volatile, nonVolatile, permanent, readOnly)
SNMP Set-Request operations MAY be used to create appropriate rows in Note: The SNMP Notification MIB uses persistence instead of the
the SNMP Target MIB defined in [RFC-2573] and MAY specify: lease duration supported in IPP Subscription objects.
To complete a subscription via SNMP, the IPP Client MAY use an SNMP
Set-Request operation to create an appropriate row in the SNMP Target
MIB with the following variable-bindings:
1) 'snmpTargetAddrTDomain' and 'snmpTargetAddrTAddress' 1) 'snmpTargetAddrTDomain' and 'snmpTargetAddrTAddress'
- target transport protocol and address (equivalent to URI) - notification target (client) transport protocol and address
(corresponds to IPP 'notify-recipient-uri')
2) 'snmpTargetAddressTimeout' and 'snmpTargetAddrRetryCount' 2) 'snmpTargetAddressTimeout' and 'snmpTargetAddrRetryCount'
- retry timeout and limit (for acknowledged notifications - retry timeout and limit (for acknowledged SNMP Inform only)
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 "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 - persistence (volatile, nonVolatile, permanent, readOnly)
3.5. Relationship to other MIBs Note: The SNMP Target MIB uses persistence instead of the lease
duration supported in IPP Subscription objects.
3.5.1. MIB-II (RFC 1213) 3.3. Relationship to other MIBs
3.3.1. MIB-II (RFC 1213)
All SNMPv1 trap messages include 'time-stamp' which is the value of All SNMPv1 trap messages include 'time-stamp' which is the value of
the 'sysUpTime' object from MIB-II [RFC-1213]. the 'sysUpTime' object from MIB-II [RFC-1213].
All SNMPv2 trap bindings include the 'sysUpTime' object from MIB-II All SNMPv2 trap bindings include the 'sysUpTime' object from MIB-II
[RFC-1213]. [RFC-1213].
3.5.2. Host Resources MIB (RFC 1514) 3.3.2. Host Resources MIB (RFC 2790)
The 'jmDeviceBasicV2Event' trap defined in this document permits
optional binding of the 'hrDeviceStatus', 'hrDevicePrinterStatus',
and 'hrPrinterDetectedErrorState' objects from Host Resources MIB
[RFC-1514].
3.5.3. Printer MIB (RFC 1759) The 'jmServiceTable' defined in this document MAY have a sparse
mapping to the 'hrDeviceTable' (same indices) in Host Resources MIB
[RFC-2790].
The 'jmDeviceBasicV2Event' trap defined in this document permits 3.3.3. Printer MIB (RFC 1759)
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 The 'jmServiceTable' defined in this document MAY have a sparse
[RFC-1759] may be indicated by the instance suffix of the mapping to the 'hrDeviceTable' (same indices) in Host Resources MIB
'hrDeviceStatus' variable's OID. [RFC-2790], thus offering access to the Printer MIB via a
'hrDeviceIndex' value.
4. Managed Object Definitions 4. Managed Object Definitions
4.1. Device Basic Event Trap 4.1. Notification Definitions
-- Device Basic Event Group (Cond Mandatory) 4.1.1. Service Basic Event - Trap
-- Service Basic Event Group (CONDITIONALLY MANDATORY)
-- --
- <span class="insert">Service</span> Basic Event Group <span class="insert">(CONDITIONALLY MANDATORY)</span>
-- Implementation of this group is conditionally mandatory; -- Implementation of this group is conditionally mandatory;
-- mandatory for systems which send this Device event via SNMP. -- mandatory for systems which send this Service traps via SNMP.
jmDeviceBasicV1Enterprise OBJECT-IDENTITY -- The jmServiceBasicEventGroup consists entirely of the
-- jmServiceBasicV2Event notification.
jmServiceBasicV1Enterprise 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 Device basic event' sent by this managed system." for a Service basic event sent by this managed system."
::= { jobmonMIBNotifications 1 } ::= { jobmonMIBNotifications 1 }
jmDeviceBasicV2EventPrefix jmServiceBasicV2EventPrefix
OBJECT IDENTIFIER ::= { jmDeviceBasicV1Enterprise 0 } OBJECT IDENTIFIER ::= { jmServiceBasicV1Enterprise 0 }
jmDeviceBasicV2Event NOTIFICATION-TYPE jmServiceBasicV2Event NOTIFICATION-TYPE
OBJECTS { OBJECTS {
jmEventTriggerEvent, jmServiceEventNotifyEvent,
jmEventSubscriptionID, jmServiceState,
jmEventSubscriberUserName, jmServiceStateReasons
jmEventSubscriberUserData,
jmEventDeviceURI,
jmEventDeviceName,
jmEventJobSetIndex,
jmEventJobIndex,
jmEventJobName,
jmEventDeviceState,
jmEventDeviceStateReasons,
jmEventDeviceIsAcceptingJobs
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This SMIv2 trap corresponds to an IPP Printer basic event. "This SMIv2 trap corresponds to an IPP Printer basic event.
The value of 'jmServiceIndex' for
use with 'jmServiceTable' for this Service is conveyed in the
instance qualifier (OID suffix) of 'jmServiceState'.
This trap is sent when requested by a prior subscription. This trap is sent when requested by a prior subscription.
The event type is specified in 'jmEventTriggerEvent'. The subscribed event type is in 'jmServiceEventNotifyEvent'.
Event types reported via 'jmDeviceBasicV2Event' include: Standard Printer event types defined in [IPP-NOT] are:
- 'printer-state-changed'
- 'printer-restarted' - 'printer-restarted'
- 'printer-shutdown' - 'printer-shutdown'
- 'printer-state-changed'
- 'printer-media-changed'
- 'printer-config-changed' - 'printer-config-changed'
- 'printer-queue-changed' - 'printer-media-changed'
- 'printer-finishings-changed'
- 'printer-queue-order-changed'
- 'printer-full'
- 'printer-no-longer-full' - 'printer-no-longer-full'
- 'printer-almost-idle' - 'printer-almost-idle'
- 'device-restarted' - 'printer-not-almost-idle'
- 'device-shutdown'
- 'device-state-changed' Standard Service event types generalized from [IPP-NOT] are:
- 'device-media-changed' - 'service-state-changed'
- 'device-config-changed' - 'service-restarted'
- 'device-queue-changed' - 'service-shutdown'
- 'device-no-longer-full' - 'service-config-changed'
- 'device-almost-idle' - 'service-media-changed'
- 'service-finishings-changed'
- 'service-queue-order-changed'
- 'service-full'
- 'service-no-longer-full'
- 'service-almost-idle'
- 'service-not-almost-idle'
- and (optionally) vendor extension event types - 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 device-level events: - Systems with the Host Resources MIB (RFC 2790) SHOULD add
- Systems with the Host Resources MIB [RFC-1514] SHOULD add
'hrSystemDate' 'hrSystemDate'
(compare to IPP 'printer-current-time') and (compare to IPP 'printer-current-time')
'hrDeviceStatus'
(compare to IPP 'printer-state')
Additional variable-bindings MAY be appended to this trap Additional variable-bindings MAY be appended to this trap
for all printer-specific events: for all printer-specific events:
- Systems with the Host Resources MIB [RFC-1514] MAY add - Systems with the Host Resources MIB (RFC 2790) MAY add
'hrDeviceStatus'
(compare to IPP 'printer-state')
'hrPrinterStatus' 'hrPrinterStatus'
(compare to IPP 'printer-state') and (compare to IPP 'printer-state') and
'hrPrinterDetectedErrorState' 'hrPrinterDetectedErrorState'
(compare to IPP 'printer-state-reasons') (compare to IPP 'printer-state-reasons')
Systems MAY add other variable-bindings from any MIB. Systems MAY add other variable-bindings from any MIB.
See: Section 5.2 'notify-events' of [IPP-NOT]; See: Section 5.3.2 'notify-events' in [IPP-NOT];
Section 7 'Notification Content' in [IPP-NOT]." Section 8.1 'notify-subscribed-event' in [IPP-NOT];
::= { jmDeviceBasicV2EventPrefix 1 } Section 9 'Event Notification Content' in [IPP-NOT]."
::= { jmServiceBasicV2EventPrefix 1 }
4.2. Job Basic Event Trap 4.1.2. Job Basic Event - Trap
-- Job Basic Event Group (Cond Mandatory) -- Job Basic Event Group (CONDITIONALLY 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 traps via SNMP.
-- The jmJobBasicEventGroup consists entirely of the
-- jmJobBasicV2Event notification.
jmJobBasicV1Enterprise 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 Job basic event sent by this managed system." for a Job basic event sent by this managed system."
::= { jobmonMIBNotifications 2 } ::= { jobmonMIBNotifications 2 }
jmJobBasicV2EventPrefix jmJobBasicV2EventPrefix
OBJECT IDENTIFIER ::= { jmJobBasicV1Enterprise 0 } OBJECT IDENTIFIER ::= { jmJobBasicV1Enterprise 0 }
jmJobBasicV2Event NOTIFICATION-TYPE jmJobBasicV2Event NOTIFICATION-TYPE
OBJECTS { OBJECTS {
jmEventTriggerEvent, jmJobEventNotifyEvent,
jmEventSubscriptionID, jmJobState,
jmEventSubscriberUserName, jmJobEventJobStateReasons
jmEventSubscriberUserData,
jmEventDeviceURI,
jmEventDeviceName,
jmEventJobSetIndex,
jmEventJobIndex,
jmEventJobName,
jmEventJobState,
jmEventJobStateReasons
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This SMIv2 trap corresponds to an IPP Job basic event. "This SMIv2 trap corresponds to an IPP Job basic event.
The values of 'jmGeneralJobSetIndex' and 'jmJobIndex' for
use with 'jmJobTable' for this Job are conveyed in the
instance qualifier (OID suffix) of 'jmJobState'.
This trap is sent when requested by a prior subscription. This trap is sent when requested by a prior subscription.
The event type is specified in 'jmEventTriggerEvent'. The subscribed event type is in 'jmJobEventNotifyEvent'.
Event types reported via 'jmJobBasicV2Event' include: Event types reported via 'jmJobBasicV2Event' include:
- 'job-created'
- 'job-state-changed' - 'job-state-changed'
- 'job-config-changed' - 'job-created'
- 'job-completed'
- 'job-purged' - 'job-purged'
- 'job-config-changed'
- and (optionally) vendor extension event types - and (optionally) vendor extension event types
Additional variable-bindings SHOULD be appended to this trap:
- Systems with the Host Resources MIB (RFC 2790) SHOULD add
'hrSystemDate'
(compare to IPP 'printer-current-time')
Systems MAY add other variable-bindings from any MIB. Systems MAY add other variable-bindings from any MIB.
See: Section 5.2 'notify-events' of [IPP-NOT]; See: Section 5.3.2 'notify-events' in [IPP-NOT];
Section 7 'Notification Content' in [IPP-NOT]." Section 8.1 'notify-subscribed-event' in [IPP-NOT];
Section 9 'Event Notification Content' in [IPP-NOT]."
::= { jmJobBasicV2EventPrefix 1 } ::= { jmJobBasicV2EventPrefix 1 }
4.3. Job Completed Event Trap 4.1.3. Job Completed Event - Trap
-- Job Completed Event Group (Cond Mandatory) -- Job Completed Event Group (CONDITIONALLY 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 traps via SNMP.
jmJobCompletedV1Enterprise OBJECT-IDENTITY jmJobCompletedV1Enterprise 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 Job completed event sent by this managed system." for a Job completed event sent by this managed system."
::= { jobmonMIBNotifications 3 } ::= { jobmonMIBNotifications 3 }
jmJobCompletedV2EventPrefix jmJobCompletedV2EventPrefix
OBJECT IDENTIFIER ::= { jmJobCompletedV1Enterprise 0 } OBJECT IDENTIFIER ::= { jmJobCompletedV1Enterprise 0 }
jmJobCompletedV2Event NOTIFICATION-TYPE jmJobCompletedV2Event NOTIFICATION-TYPE
OBJECTS { OBJECTS {
jmEventTriggerEvent, jmJobEventNotifyEvent,
jmEventSubscriptionID, jmJobState,
jmEventSubscriberUserName, jmJobEventJobStateReasons,
jmEventSubscriberUserData, jmJobKOctetsProcessed,
jmEventDeviceURI, jmJobImpressionsCompleted
jmEventDeviceName,
jmEventJobSetIndex,
jmEventJobIndex,
jmEventJobName,
jmEventJobState,
jmEventJobStateReasons,
jmEventJobKOctetsProcessed,
jmEventJobImpressionsCompleted,
jmEventJobMediaSheetsCompleted
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This SMIv2 trap corresponds to an IPP 'job-completed' event. "This SMIv2 trap corresponds to an IPP 'job-completed' event.
The values of 'jmGeneralJobSetIndex' and 'jmJobIndex' for
use with 'jmJobTable' for this Job are conveyed in the
instance qualifier (OID suffix) of 'jmJobState'.
This trap is sent when requested by a prior subscription. This trap is sent when requested by a prior subscription.
The event type is specified in 'jmEventTriggerEvent'. The subscribed event type is in 'jmJobEventNotifyEvent'.
Event types reported via 'jmJobCompletedV2Event' include: Event types reported via 'jmJobCompletedV2Event' include:
- 'job-completed' - 'job-completed'
- 'job-purged'
- and (optionally) vendor extension event types - 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-completed' events: - Systems with the Host Resources MIB (RFC 2790) SHOULD add
- Systems which support this job information SHOULD add 'hrSystemDate'
'jmEventJobKOctets' (compare to IPP 'printer-current-time')
(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. Systems MAY add other variable-bindings from any MIB.
See: Section 5.2 'notify-events' of [IPP-NOT]; See: Section 5.3.2 'notify-events' in [IPP-NOT];
Section 7 'Notification Content' in [IPP-NOT]." Section 8.1 'notify-subscribed-event' in [IPP-NOT];
Section 9 'Event Notification Content' in [IPP-NOT]."
::= { jmJobCompletedV2EventPrefix 1 } ::= { jmJobCompletedV2EventPrefix 1 }
4.4. Job Progress Event Trap
-- Job Progress Event Group (Cond Mandatory) 4.1.4. Job Progress Event - Trap
-- Job Progress Event Group (CONDITIONALLY MANDATORY)
-- --
- Job Progress Event Group <span class="insert">(CONDITIONALLY MANDATORY)</span>
-- 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 traps via SNMP.
jmJobProgressV1Enterprise OBJECT-IDENTITY jmJobProgressV1Enterprise 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 Job progress event sent by this managed system." for a Job progress event sent by this managed system."
::= { jobmonMIBNotifications 4 } ::= { jobmonMIBNotifications 4 }
jmJobProgressV2EventPrefix jmJobProgressV2EventPrefix
OBJECT IDENTIFIER ::= { jmJobProgressV1Enterprise 0 } OBJECT IDENTIFIER ::= { jmJobProgressV1Enterprise 0 }
jmJobProgressV2Event NOTIFICATION-TYPE jmJobProgressV2Event NOTIFICATION-TYPE
OBJECTS { OBJECTS {
jmEventTriggerEvent, jmJobKOctetsPerCopyRequested,
jmEventSubscriptionID, jmJobKOctetsProcessed,
jmEventSubscriberUserName, jmJobImpressionsPerCopyRequested,
jmEventSubscriberUserData, jmJobImpressionsCompleted,
jmEventDeviceURI, jmProgressJobCopiesRequested,
jmEventDeviceName, jmProgressJobCollationType,
jmEventJobSetIndex, jmProgressMediaSheetsCompleted,
jmEventJobIndex, jmProgressSheetCompletedCopyNum,
jmEventJobName, jmProgressSheetCompletedDocNum
jmEventJobState,
jmEventJobStateReasons,
jmEventJobKOctetsProcessed,
jmEventJobImpressionsCompleted,
jmEventJobMediaSheetsCompleted,
jmEventJobImpressionsCompletedCC,
jmEventJobCollationType,
jmEventJobSheetCompletedCopyNum,
jmEventJobSheetCompletedDocNum
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This SMIv2 trap corresponds to an IPP 'job-progress' event. "This SMIv2 trap corresponds to an IPP 'job-progress' event.
The values of 'jmGeneralJobSetIndex' and 'jmJobIndex' for
use with 'jmJobTable' for this Job are conveyed in the
instance qualifier (OID suffix) of 'jmJobKOctetsProcessed'.
This trap is sent when requested by a prior subscription. This trap is sent when requested by a prior subscription.
The event type is specified in 'jmEventTriggerEvent'. The event type is 'job-progress'.
Event types reported via 'jmJobProgressV2Event' include: Additional variable-bindings SHOULD be appended to this trap:
- 'job-progress' - Systems with the Host Resources MIB (RFC 2790) SHOULD add
- and (optionally) vendor extension event types 'hrSystemDate'
Additional variable-bindings SHOULD be appended to this trap (compare to IPP 'printer-current-time')
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. Systems MAY add other variable-bindings from any MIB.
See: Section 5.2 'notify-events' of [IPP-NOT]; See: Section 5.3.2 'notify-events' in [IPP-NOT];
Section 7 'Notification Content' in [IPP-NOT]." Section 8.1 'notify-subscribed-event' in [IPP-NOT];
Section 9 'Event Notification Content' in [IPP-NOT]."
::= { jmJobProgressV2EventPrefix 1 } ::= { jmJobProgressV2EventPrefix 1 }
4.5. Event Binding Group 4.2. Object Definitions
-- Event Binding Group (Cond Mandatory) 4.2.1. Service Group - Objects
-- The Service Group (CONDITIONALLY MANDATORY)
-- --
- <span class="insert">The Service</span> Group <span class="insert">(CONDITIONALLY MANDATORY)</span>
-- Implementation of this group is conditionally mandatory; -- Implementation of this group is conditionally mandatory;
-- mandatory for systems which send Device or Job events via SNMP. -- mandatory for systems which show Service state 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.
- mandatory for systems which <span class="insert">show Service state</span> via SNMP. -- The jmServiceGroup consists entirely of the jmServiceTable
jmEventBinding OBJECT IDENTIFIER ::= { jobmonMIBObjects 5 }
jmEventTriggerEvent OBJECT-TYPE jmService OBJECT IDENTIFIER ::= { jobmonMIBObjects 7 }
SYNTAX JmUTF8StringTC (SIZE (0..63)) -- 255 in [IPP-MOD]
MAX-ACCESS read-only jmServiceTable OBJECT-TYPE
SYNTAX SEQUENCE OF JmServiceEntry
MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The trigger event type associated with this event. "The jmServiceTable consists of basic service state and status
information for each service which offers one or more job
Standard Printer event types defined in [IPP-NOT] are: services on this managed system.
- '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: An entry SHALL exist in this table for each service, no matter
what the state of that service. A service MAY support multiple
configured job sets and configured devices.
- 'device-restarted' See: 'jmServiceJobSetsConfigured' and
- 'device-shutdown' 'jmServiceDevicesConfigured' bit-arrays in this MIB."
- 'device-state-changed' ::= { jmService 1 }
- '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: jmServiceEntry OBJECT-TYPE
- 'job-created' SYNTAX JmServiceEntry
- 'job-completed' MAX-ACCESS not-accessible
- 'job-state-changed' STATUS current
- 'job-config-changed' DESCRIPTION
- 'job-purged' "Basic service state and status information."
- 'job-progress' INDEX { jmServiceIndex }
::= { jmServiceTable 1 }
Conformance: The natural language for keywords JmServiceEntry ::= SEQUENCE {
in trigger event type SHALL always be US English. jmServiceIndex Integer32 (1..2147483647),
jmServiceName JmUTF8StringTC (SIZE (0..63)),
jmServiceURI JmUTF8StringTC (SIZE (0..63)),
jmServiceJobServiceTypes JmJobServiceTypesTC,
jmServiceJobSetsConfigured OCTET STRING (SIZE (0..255)),
jmServiceDevicesConfigured OCTET STRING (SIZE (0..255)),
jmServiceState JmServiceStateTC,
jmServiceStateReasons SnmpAdminString (SIZE (0..255))
}
Conformance: This trigger event type SHALL be valid jmServiceIndex OBJECT-TYPE
and reported in ALL Job Monitoring MIB notifications. SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The unique identifier for this service on this managed system.
See: Section 5.2 'notify-events' and See: 'jmServiceEventServiceIndex' object in this MIB."
Section 7 'Notification Content' in [IPP-NOT]." ::= { jmServiceEntry 1 }
-- DEFVAL intentionally omitted - reported value SHALL be valid
::= { jmEventBinding 1 }
jmEventSubscriptionID OBJECT-TYPE jmServiceName OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX JmUTF8StringTC (SIZE(0..63)) -- 127 in IPP
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The subscription identifier associated with this event "The human readable name of this managed service.
or zero (if none).
Conformance: This subscription identifier SHALL be valid
and reported, if available on this managed system.
See: Section 5.8 'subscription-id' and See: 'deviceNameRequested' job attribute in this MIB;
Section 7 'Notification Content' in [IPP-NOT]." 'physicalDevice' job attribute in this MIB;
DEFVAL { 0 } -- no subscription ID Section 4.4.4 'printer-name' in [IPP-MOD]."
::= { jmEventBinding 2 } DEFVAL { ''H } -- no service name
::= { jmServiceEntry 2 }
jmEventSubscriberUserName OBJECT-TYPE jmServiceURI OBJECT-TYPE
SYNTAX JmUTF8StringTC (SIZE (0..63)) -- 1023 in [IPP-MOD] SYNTAX JmUTF8StringTC (SIZE(0..63)) -- 1023 in IPP
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The subscriber user name associated with this event "A URI for this managed service (valid for job services).
or the empty string (if none).
Note: The natural language appropriate for text-to-speech See: Section 4.3.3 'job-printer-uri' in [IPP-MOD];
of subscriber user name is orthogonal to the localized text Section 4.4.1 'printer-uri-supported' in [IPP-MOD]."
context in IPP 'attributes-natural-language'. The subscriber DEFVAL { ''H } -- no service URI
user name MAY include an in-line 'language tag' using Plane ::= { jmServiceEntry 3 }
14 'language tag' characters approved for ISO 10646/Unicode.
Conformance: This subscriber user name SHALL be valid jmServiceJobServiceTypes OBJECT-TYPE
and reported, if available on this managed system. SYNTAX JmJobServiceTypesTC
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The types of job services supported by this managed service.
See: 'Language Tagging in Unicode Plain Text', RFC 2482 See: 'JmJobServiceTypesTC' textual convention in this MIB;
(January 1999); 'jobServiceTypes' job attribute in this MIB."
'Plane 14 Characters for Language Tags', Unicode DEFVAL { 0 } -- no job services
Technical Report #7 (January 1999); ::= { jmServiceEntry 4 }
Section 4.3.6 'job-originating-user-name' and
Section 4.4.2 'uri-authentication-supported'
(usage of 'requesting-user-name') in [IPP-MOD];
Section 5.11 'subscriber-user-name' and
Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { ''H } -- no subscriber user name
::= { jmEventBinding 3 }
jmEventSubscriberUserData OBJECT-TYPE jmServiceJobSetsConfigured OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..63)) -- 63 in [IPP-NOT] SYNTAX OCTET STRING (SIZE(0..255))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The subscriber user data associated with this event "A bit-array that specifies the job sets configured for this
or the empty string (if none). service, where each bit '2**n' is set if 'jmGeneralJobSetIndex'
is a configured job set. Uses network byte order (big-endian)
rules - the high-order bit of the first octet corresponds to
'jmGeneralJobSetIndex' of '0' (reserved) - the low-order bit of
the first octet corresponds to 'jmGeneralJobSetIndex' of '7'.
Supports values of 'jmGeneralJobSetIndex' from '1' to '2039'.
Conformance: This subscriber user data SHALL be valid Compare to the BITS pseudotype defined in IETF SMIv2 (RFC 2578)
and reported, if available on this managed system. which has the same bit ordering rules (big-endian).
See: Section 5.4 'subscriber-user-data' and See: 'queueNameRequested' job attribute in this MIB;
Section 7 'Notification Content' in [IPP-NOT]." 'jmGeneralJobSetIndex' table index in this MIB."
DEFVAL { ''H } -- no subscriber user data DEFVAL { ''H } -- no job sets configured
::= { jmEventBinding 4 } ::= { jmServiceEntry 5 }
jmEventDeviceURI OBJECT-TYPE jmServiceDevicesConfigured OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..255)) -- 1023 in [IPP-MOD] SYNTAX OCTET STRING (SIZE(0..255))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The device URI associated with this event "A bit-array that specifies the devices configured for this
or the empty string (if none). service, where each bit '2**n' is set if 'hrDeviceIndex'
is a configured device. Uses network byte order (big-endian)
rules - the high-order bit of the first octet corresponds to
'hrDeviceIndex' of '0' (reserved) - the low-order bit of
the first octet corresponds to 'hrDeviceIndex' of '7'.
Supports values of 'hrDeviceIndex' from '1' to '2039'.
Conformance: This device URI SHALL be valid Compare to the BITS pseudotype defined in IETF SMIv2 (RFC 2578)
and reported, if available on this managed system. which has the same bit ordering rules (big-endian).
See: Section 4.3.3 'job-printer-uri' in [IPP-MOD]; See: 'physicalDevice' job attribute in this MIB;
Section 4.4.1 'printer-uri-supported' in [IPP-MOD]; 'hrDeviceIndex' in IETF Host MIB (RFC 2790)."
Section 7 'Notification Content' in [IPP-NOT]." DEFVAL { ''H } -- no devices configured
DEFVAL { ''H } -- no device URI ::= { jmServiceEntry 6 }
::= { jmEventBinding 5 }
jmEventDeviceName OBJECT-TYPE jmServiceState OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..127)) -- 127 in [IPP-MOD] SYNTAX JmServiceStateTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The device name associated with this event "The current state of this managed service.
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]; See: 'jmServiceEventServiceState' object in this MIB;
Section 7 'Notification Content' in [IPP-NOT]." 'jmJobState' object in this MIB;
DEFVAL { ''H } -- no device name Section 4.4.11 'printer-state' in [IPP-MOD]."
::= { jmEventBinding 6 } DEFVAL { unknown } -- unknown service state
::= { jmServiceEntry 7 }
jmEventDeviceState OBJECT-TYPE jmServiceStateReasons OBJECT-TYPE
SYNTAX INTEGER { -- enum in [IPP-MOD] SYNTAX SnmpAdminString (SIZE (0..255)) -- multi-valued in IPP
unknown(2), -- unknown device state
idle(3),
processing(4),
stopped(5)
}
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The device state associated with this event "The service state reasons associated with this service state
or 'unknown'. (as a comma-separated list) or the empty string (if none).
Note: This object uses the keywords from the [IPP-MOD] See: 'jmServiceEventServiceStateReasons' object in this MIB;
enumerated type 'printer-state' for coherence. 'jmJobStateReasons1' object in this MIB;
Section 4.4.12 'printer-state-reasons' in [IPP-MOD]."
DEFVAL { ''H } -- no service state reasons
::= { jmServiceEntry 8 }
Conformance: This device state SHALL be valid 4.2.2. Service Event Group - Objects
and reported, if available on this managed system.
See: Section 4.4.11 'printer-state' in [IPP-MOD]; -- The Service Event Group (CONDITIONALLY MANDATORY)
Section 7 'Notification Content' in [IPP-NOT]." --
DEFVAL { unknown } -- unknown device state -- Implementation of this group is conditionally mandatory;
::= { jmEventBinding 7 } -- mandatory for systems which show Service events via SNMP.
jmEventDeviceStateReasons OBJECT-TYPE -- The jmServiceEventGroup consists entirely of the jmServiceEventTable
SYNTAX OCTET STRING (SIZE (0..255)) -- 255*n in [IPP-MOD]
jmServiceEvent OBJECT IDENTIFIER ::= { jobmonMIBObjects 8 }
jmServiceEventTable OBJECT-TYPE
SYNTAX SEQUENCE OF JmServiceEventEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The jmServiceEventTable contains service event entries for the
services which offer job services on this managed system."
::= { jmServiceEvent 1 }
jmServiceEventEntry OBJECT-TYPE
SYNTAX JmServiceEventEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Basic service event information."
INDEX { jmServiceEventIndex }
::= { jmServiceEventTable 1 }
JmServiceEventEntry ::= SEQUENCE {
jmServiceEventIndex Integer32 (1..2147483647),
jmServiceEventNotifyEvent SnmpAdminString (SIZE (0..63)),
jmServiceEventNotifyTime TimeTicks,
jmServiceEventServiceIndex Integer32 (1..2147483647),
jmServiceEventServiceState JmServiceStateTC,
jmServiceEventServiceStateReasons SnmpAdminString (SIZE (0..255))
}
jmServiceEventIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The unique identifier for this event on this managed system."
::= { jmServiceEventEntry 1 }
jmServiceEventNotifyEvent OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..63)) -- 255 in [IPP-NOT]
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The device state reasons associated with this event "The event type that created this row in 'jmServiceEventTable'.
(as a comma-separated list) or the empty string (if none).
Standard Printer event types defined in [IPP-NOT] are:
- 'printer-state-changed'
- 'printer-restarted'
- 'printer-shutdown'
- 'printer-config-changed'
- 'printer-media-changed'
- 'printer-finishings-changed'
- 'printer-queue-order-changed'
- 'printer-full'
- 'printer-no-longer-full'
- 'printer-almost-idle'
- 'printer-not-almost-idle'
Standard Service event types generalized from [IPP-NOT] are:
- 'service-state-changed'
- 'service-restarted'
- 'service-shutdown'
- 'service-config-changed'
- 'service-media-changed'
- 'service-finishings-changed'
- 'service-queue-order-changed'
- 'service-full'
- 'service-no-longer-full'
- 'service-almost-idle'
- 'service-not-almost-idle'
Conformance: The natural language for keywords Conformance: The natural language for keywords
in device state reasons SHALL always be US English. in subscribed event type SHALL always be US English.
Conformance: These device state reasons SHALL be valid Conformance: This subscribed event type SHALL be valid
and reported, if available on this managed system. and reported in ALL Job Monitoring MIB notifications.
See: Section 4.4.12 'printer-state-reasons' in [IPP-MOD]; See: Section 8.1 'notify-subscribed-event' in [IPP-NOT]."
Section 7 'Notification Content' in [IPP-NOT]." DEFVAL { ''H } -- no notify subscribed event
DEFVAL { ''H } -- no device state reasons ::= { jmServiceEventEntry 2 }
::= { jmEventBinding 8 }
jmEventDeviceIsAcceptingJobs OBJECT-TYPE jmServiceEventNotifyTime OBJECT-TYPE
SYNTAX TruthValue SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The device substate associated with this event "The time of this service event.
or 'true' (if unknown).
Conformance: This device substate SHALL be valid Usage: Conforming management agents, which MUST implement the
and reported, if available on this managed system. IETF MIB-II (RFC 1213), SHALL set 'jmServiceEventNotifyTime' to
'sysUpTime' when a service event row is created.
See: Section 4.4.23 'printer-is-accepting-jobs' See: 'sysUpTime' in IETF MIB-II (RFC 1213);
in [IPP-MOD]; Section 5.4.4 'notify-printer-up-time' in [IPP-NOT];
Section 7 'Notification Content' in [IPP-NOT]." Section 4.4.29 'printer-up-time' in [IPP-MOD]."
DEFVAL { true } -- device is accepting jobs ::= { jmServiceEventEntry 3 }
::= { jmEventBinding 9 }
jmEventJobSetIndex OBJECT-TYPE jmServiceEventServiceIndex OBJECT-TYPE
SYNTAX Integer32 (0..32767) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The job set index associated with this event "The unique identifier for this service on this managed system.
or zero (if none).
Conformance: This job set index SHALL be valid See: 'jmServiceIndex' object in this MIB."
and reported, if available on this managed system. ::= { jmServiceEventEntry 4 }
See: 'jmGeneralJobSetIndex' object in [RFC-2707]; jmServiceEventServiceState OBJECT-TYPE
Section 4.3.2 'job-id' in [IPP-MOD]; SYNTAX JmServiceStateTC
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 MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The job index associated with this event "The state of this managed service at the time of 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]; See: 'jmServiceState' object in this MIB;
Section 4.3.2 'job-id' in [IPP-MOD]; 'jmJobState' object in this MIB;
Section 7 'Notification Content' in [IPP-NOT]." Section 4.4.11 'printer-state' in [IPP-MOD]."
DEFVAL { 0 } -- no job index DEFVAL { unknown } -- unknown service state
::= { jmEventBinding 11 } ::= { jmServiceEventEntry 5 }
jmEventJobName OBJECT-TYPE jmServiceEventServiceStateReasons OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..255)) -- 255 in [IPP-MOD] SYNTAX SnmpAdminString (SIZE (0..255)) -- multi-valued in IPP
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The job name associated with this event "The service state reasons associated with this service state
or the empty string (if none). (as a comma-separated list) or the empty string (if none).
Conformance: This job name SHALL be valid See: 'jmServiceStateReasons' object in this MIB;
and reported, if available on this managed system. 'jmJobStateReasons1' object in this MIB;
Section 4.4.12 'printer-state-reasons' in [IPP-MOD]."
DEFVAL { ''H } -- no service state reasons
::= { jmServiceEventEntry 6 }
See: 'jobName' attribute in [RFC-2707]; 4.2.3. Job Event Group - Objects
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 -- The Job Event Group (CONDITIONALLY MANDATORY)
SYNTAX INTEGER { -- enum in [IPP-MOD] --
unknown(2), -- unknown job state -- Implementation of this group is conditionally mandatory;
pending(3), -- mandatory for systems which show Job events via SNMP.
pendingHeld(4),
processing(5), -- The jmJobEventGroup consists entirely of the jmJobEventTable
processingStopped(6),
canceled(7), jmJobEvent OBJECT IDENTIFIER ::= { jobmonMIBObjects 9 }
aborted(8),
completed(9) jmJobEventTable OBJECT-TYPE
} SYNTAX SEQUENCE OF JmJobEventEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The job state associated with this event "The jmJobEventTable contains job event entries for the
or 'unknown'. jobs present on this managed system."
::= { jmJobEvent 1 }
Note: This object uses the keywords from the [IPP-MOD] jmJobEventEntry OBJECT-TYPE
enumerated type 'job-state' for coherence. SYNTAX JmJobEventEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Basic job event information."
INDEX { jmJobEventIndex }
::= { jmJobEventTable 1 }
Conformance: This job state SHALL be valid JmJobEventEntry ::= SEQUENCE {
and reported, if available on this managed system. jmJobEventIndex Integer32 (1..2147483647),
jmJobEventNotifyEvent SnmpAdminString (SIZE (0..63)),
jmJobEventNotifyTime TimeTicks,
jmJobEventJobSetIndex Integer32 (1..32767),
jmJobEventJobIndex Integer32 (1..2147483647),
jmJobEventJobState JmJobStateTC,
jmJobEventJobStateReasons OCTET STRING (SIZE (4..16))
}
See: 'jmJobState' object in [RFC-2707]; jmJobEventIndex OBJECT-TYPE
Section 4.3.7 'job-state' in [IPP-MOD]; SYNTAX Integer32 (1..2147483647)
Section 7 'Notification Content' in [IPP-NOT]." MAX-ACCESS not-accessible
DEFVAL { unknown } -- unknown job state STATUS current
::= { jmEventBinding 13 } DESCRIPTION
"The unique identifier for this event on this managed system."
::= { jmJobEventEntry 1 }
jmEventJobStateReasons OBJECT-TYPE jmJobEventNotifyEvent OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..255)) -- 255*n in [IPP-MOD] SYNTAX SnmpAdminString (SIZE (0..63)) -- 255 in [IPP-NOT]
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The job state reasons associated with this event "The event type that created this row in 'jmJobEventTable'.
(as a comma-separated list) or the empty string (if none).
Standard Job event types defined in [IPP-NOT] are:
- 'job-state-changed'
- 'job-created'
- 'job-completed'
- 'job-purged'
- 'job-config-changed'
- 'job-progress'
Conformance: The natural language for keywords Conformance: The natural language for keywords
in job state reasons SHALL always be US English. in subscribed event type SHALL always be US English.
Conformance: These job state reasons SHALL be valid Conformance: This subscribed event type SHALL be valid
and reported, if available on this managed system. and reported in ALL Job Monitoring MIB notifications.
See: 'jmJobStateReasons1' object in [RFC-2707]; See: Section 8.1 'notify-subscribed-event' in [IPP-NOT]."
'jobStateReasons2', 'jobStateReasons3', and DEFVAL { ''H } -- no notify subscribed event
'jobStateReasons4' attributes in [RFC-2707]; ::= { jmJobEventEntry 2 }
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 jmJobEventNotifyTime OBJECT-TYPE
SYNTAX Integer32 (-2..2147483647) SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The job size in K octets associated with this event "The time of this job event.
or zero (if none) or '-2' (if unknown).
Conformance: This job size SHALL be valid Usage: Conforming management agents, which MUST implement the
and reported, if available on this managed system. IETF MIB-II (RFC 1213), SHALL set 'jmJobEventNotifyTime' to
'sysUpTime' when a job event row is created.
See: 'jobKOctetsTransferred' attribute in [RFC-2707]; See: 'sysUpTime' in IETF MIB-II (RFC 1213);
Section 4.3.17.1 'job-k-octets' in [IPP-MOD]; Section 5.4.4 'notify-printer-up-time' in [IPP-NOT];
Section 7 'Notification Content' in [IPP-NOT]." Section 4.4.29 'printer-up-time' in [IPP-MOD]."
DEFVAL { -2 } -- unknown job size ::= { jmJobEventEntry 3 }
::= { jmEventBinding 15 }
jmEventJobKOctetsProcessed OBJECT-TYPE jmJobEventJobSetIndex OBJECT-TYPE
SYNTAX Integer32 (-2..2147483647) SYNTAX Integer32 (1..32767)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The job progress in K octets associated with this event "The unique identifier for this job set on this managed system.
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]; See: 'jmGeneralJobSetIndex' object in this MIB."
Section 4.3.18.1 'job-k-octets-processed' ::= { jmJobEventEntry 4 }
in [IPP-MOD];
Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { -2 } -- unknown job progress
::= { jmEventBinding 16 }
jmEventJobImpressions OBJECT-TYPE jmJobEventJobIndex OBJECT-TYPE
SYNTAX Integer32 (-2..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The job size in impressions associated with this event "The unique identifier for this job on this managed system,
or zero (if none) or '-2' (if unknown). when prefixed with 'jmJobEventJobSetIndex'.
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]; See: 'jmJobIndex' object in this MIB."
Section 7 'Notification Content' in [IPP-NOT]." ::= { jmJobEventEntry 5 }
DEFVAL { -2 } -- unknown job size
::= { jmEventBinding 17 }
jmEventJobImpressionsCompleted OBJECT-TYPE jmJobEventJobState OBJECT-TYPE
SYNTAX Integer32 (-2..2147483647) SYNTAX JmJobStateTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The job progress in impressions associated with this event "The state of this managed job at the time of 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]; See: 'jmJobState' in this MIB;
Section 4.3.18.2 'job-impressions-completed' Section 4.3.7 'job-state' in [IPP-MOD]."
in [IPP-MOD]; DEFVAL { unknown } -- unknown job state
Section 7 'Notification Content' in [IPP-NOT]." ::= { jmJobEventEntry 6 }
DEFVAL { -2 } -- unknown job progress
::= { jmEventBinding 18 }
jmEventJobMediaSheets OBJECT-TYPE jmJobEventJobStateReasons OBJECT-TYPE
SYNTAX Integer32 (-2..2147483647) SYNTAX OCTET STRING (SIZE (4..16)) -- multi-valued in IPP
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The job size in media sheets associated with this event "The job state reasons associated with this job state
or zero (if none) or '-2' (if unknown). represented as one to four concatenated 32-bit integers
in network byte order (big-endian).
Conformance: This job size SHALL be valid Usage: Conforming management stations SHALL always report the
and reported, if available on this managed system. value of the object 'jmJobStateReasons1' in the first four
octets of 'jmJobEventJobStateReasons' and SHOULD report values
of the attributes 'jobStateReasons2', 'jobStateReasons3', and
'jobStateReasons4' in subsequent octets.
See: 'sheetsRequested' attribute in [RFC-2707]; See: 'jmJobStateReasons1' in this MIB;
Section 4.3.17.3 'job-media-sheets' in [IPP-MOD]; Section 4.3.8 'job-state-reasons' in [IPP-MOD]."
Section 7 'Notification Content' in [IPP-NOT]." DEFVAL { '00000000'H } -- no job state reasons
DEFVAL { -2 } -- unknown job size ::= { jmJobEventEntry 7 }
::= { jmEventBinding 19 }
jmEventJobMediaSheetsCompleted OBJECT-TYPE 4.2.4. Job Progress Group - Objects
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 -- The Job Progress Group (CONDITIONALLY MANDATORY)
and reported, if available on this managed system. --
-- Implementation of this group is conditionally mandatory;
-- mandatory for systems which send Job progress traps via SNMP.
See: 'sheetsCompleted' attribute in [RFC-2707]; -- The jmProgressGroup consists entirely of leaf objects for traps
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 }
- <span class="insert">The jmProgressGroup consists entirely of leaf objects for traps</span> jmProgress OBJECT IDENTIFIER ::= { jobmonMIBObjects 10 }
jmEventJobImpressionsCompletedCC OBJECT-TYPE
jmProgressJobCopiesRequested OBJECT-TYPE
SYNTAX Integer32 (-2..2147483647) SYNTAX Integer32 (-2..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The job progress in impressions completed "The number of copies of this job requested by the client.
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]; See: 'jobCopiesRequested' attribute in this MIB."
'impressions-completed-current-copy' in [IPP-PROG]; DEFVAL { -2 } -- unknown job copies
Section 7 'Notification Content' in [IPP-NOT]." ::= { jmProgress 1 }
DEFVAL { unknown } -- unknown job progress
::= { jmEventBinding 21 }
jmEventJobCollationType OBJECT-TYPE jmProgressJobCollationType OBJECT-TYPE
SYNTAX JmJobCollationTypeTC SYNTAX JmJobCollationTypeTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The job collation type associated with this event "The number of copies of this job requested by the client.
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]; See: 'jobCollationType' attribute in this MIB;
'job-collation-type' in [IPP-PROG]; 'job-collation-type' in [IPP-PROG];
Section 7 'Notification Content' in [IPP-NOT]." Section 9 'Event Notification Content' in [IPP-NOT]."
DEFVAL { unknown } -- unknown job collation type DEFVAL { unknown } -- unknown job collation type
::= { jmEventBinding 22 } ::= { jmProgress 2 }
jmEventJobSheetCompletedCopyNum OBJECT-TYPE jmProgressMediaSheetsCompleted OBJECT-TYPE
SYNTAX Integer32 (-2..2147483647) SYNTAX Integer32 (-2..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The job progress number of the copy currently being "The number of media sheets completed for this job.
stacked for the document associated with this event
or zero (if none) or '-2' (if unknown).
Conformance: This job progress SHALL be valid See: 'sheetsCompleted' attribute in this MIB;
and reported, if available on this managed system. Section 4.3.18.3 'job-media-sheets-completed'
in [IPP-MOD];
Section 9 'Event Notification Content' in [IPP-NOT]."
DEFVAL { -2 } -- unknown job progress
::= { jmProgress 3 }
See: 'sheetCompletedCopyNumber' attribute jmProgressSheetCompletedCopyNum OBJECT-TYPE
in [RFC-2707]; SYNTAX Integer32 (-2..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of the job copy currently being stacked for the
current document or zero (if none) or '-2' (unknown).
See: 'sheetCompletedCopyNumber' attribute in this MIB;
'sheet-completed-copy-number' in [IPP-PROG]; 'sheet-completed-copy-number' in [IPP-PROG];
Section 7 'Notification Content' in [IPP-NOT]." Section 9 'Event Notification Content' in [IPP-NOT]."
DEFVAL { -2 } -- unknown copy number DEFVAL { -2 } -- unknown sheet complete copy
::= { jmEventBinding 23 } ::= { jmProgress 4 }
jmEventJobSheetCompletedDocNum OBJECT-TYPE jmProgressSheetCompletedDocNum OBJECT-TYPE
SYNTAX Integer32 (-2..2147483647) SYNTAX Integer32 (-2..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The job progress number of the document currently being "The number of the job document currently being stacked for the
stacked associated with this event current job or zero (if none) or '-2' (unknown).
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 See: 'sheetCompletedDocumentNumber' attribute in this MIB;
in [RFC-2707];
'sheet-completed-document-number' in [IPP-PROG]; 'sheet-completed-document-number' in [IPP-PROG];
Section 7 'Notification Content' in [IPP-NOT]." Section 9 'Event Notification Content' in [IPP-NOT]."
DEFVAL { -2 } -- unknown document number DEFVAL { -2 } -- unknown sheet complete doc
::= { jmEventBinding 24 } ::= { jmProgress 5 }
5. IANA Considerations 5. IANA Considerations
None. None.
6. Internationalization Considerations 6. Internationalization Considerations
The 'jmEventTriggerEvent', 'jmEventDeviceState', and The 'jmServiceStateReasons', 'jmServiceEventServiceStateReasons',
'jmEventDeviceStateReasons' text objects defined in this document are 'jmServiceEventNotifyEvent', and 'jmJobEventNotifyEvent', text string
of type 'JmUTF8StringTC' (UTF-8 stream-encoded ISO 10646/Unicode objects defined in this document are of type 'SnmpAdminString' (UTF-8
text) defined in the Job Monitoring MIB [RFC-2707]. The natural stream-encoded ISO 10646/Unicode text) defined in the SNMPv3
language of these objects is US English. Framework MIB [RFC-2571]. The natural language of these objects is
US English (they contain keywords).
The 'jmEventSubscriberUserName' text object defined in this document
is of type 'JmUTF8StringTC' (UTF-8 stream-encoded ISO 10646/Unicode
text) defined in the Job Monitoring MIB [RFC-2707]. The natural
language of this object is inherently ambiguous (as it usually
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
[IPP-MOD] R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell. [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> IPP/1.1 Model and Semantics, <draft-ietf-ipp-model-v11-07.txt>
(work-in-progress), March 2000. (work-in-progress), May 2000.
[IPP-NOT] S. Isaacson, J. Martin, R. deBry, T. Hastings, M. Shepherd, [IPP-NOT] S. Isaacson, J. Martin, R. deBry, T. Hastings, M. Shepherd,
R. Bergman. IPP Event Notification Specification, R. Bergman. IPP Event Notification Specification,
<draft-ietf-ipp-not-spec-02.txt> (work-in-progress), March 2000. <draft-ietf-ipp-not-spec-02.txt> (work-in-progress), March 2000.
[IPP-PROG] T. Hastings, R. Bergman, H. Lewis. Proposed Job Progress [IPP-PROG] T. Hastings, R. Bergman, H. Lewis. Proposed Job Progress
Attributes for IPP, <draft-ietf-ipp-job-prog.txt> (work-in-progress), Attributes for IPP, <draft-ietf-ipp-job-prog-00.txt>
February 2000. (work-in-progress), February 2000.
[RFC-1213] K. McCloghrie, M. Rose. MIB-II, RFC 1213, March 1991. [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, [RFC-1759] R. Smith, F. Wright, T. Hastings, S. Zilles,
J. Gyllenskog. Printer MIB, RFC 1759, March 1995. J. Gyllenskog. Printer MIB, RFC 1759, March 1995.
[RFC-2571] D. Harrington, R. Presuhn, B. Wijnen. Architecture for
SNMP Management Frameworks, RFC 2571, April 1999.
[RFC-2573] D. Levi, P. Meyer, B. Stewart. SNMP Applications, RFC [RFC-2573] D. Levi, P. Meyer, B. Stewart. SNMP Applications, RFC
2573, April 1999. 2573, April 1999.
[RFC-2576] R. Frye, D. Levi, S. Routhier, B. Wijnen. Coexistence [RFC-2576] R. Frye, D. Levi, S. Routhier, B. Wijnen. Coexistence
between Version 1, Version 2, and Version 3 of the Internet-standard between Version 1, Version 2, and Version 3 of the Internet-standard
Network Management Framework, RFC 2576, March 2000. Network Management Framework, RFC 2576, March 2000.
[RFC-2707] R. Bergman, T. Hastings, S. Isaacson, H. Lewis. Job [RFC-2707] R. Bergman, T. Hastings, S. Isaacson, H. Lewis. Job
Monitoring MIB v1.0, RFC 2707, November 1999 Monitoring MIB v1.0, RFC 2707, November 1999
[RFC-2790] P. Grillo, S. Waldbusser. Host Resources MIB, RFC 2790,
March 2000.
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-03.txt> - 6 July 2000
1) Added 'SnmpAdminString' to IMPORTS clause for new objects.
2) Corrected OID in MODULE-IDENTITY to use forward reference to
definition of 'pwg' from 'enterprises' and 'mibs' from 'pwg'.
3) Added 'JmServiceStateTC' textual convention.
4) Added 'jmMirrorAttr' and 'jmSystem' object identifiers reserved
for future extensions.
5) Major rewrite, per email discussion on IETF IPP WG list, to
specify four new small (traditional) SNMP traps for:
'jmServiceBasicV2Event' (generalized from IPP Printer event),
'jmJobBasicV2Event' (corresponds IPP Job event),
'jmJobCompletedV2Event' (corresponds IPP Job completed event),
'jmJobProgressV2Event' (corresponds IPP Job progress event).
6) Major rewrite, per email discussion on IETF IPP WG list, to
specify four new SNMP object groups: 'jmServiceTable' (name,
URI, state, etc. - from IPP Printer), 'jmServiceEventTable'
(records IPP Printer events for polling), 'jmJobEventTable'
(records IPP Job events for polling), 'jmJobProgressGroup' (leaf
objects for IPP Job progress event).
7) Revised section 3.1 'SNMP Mapping for IPP Printer Events' and
section 3.2 'SNMP Mapping for IPP Job Events', to agree with
above.
8) Deleted obsolete section 3.3 'Rules for Encoding Notifications',
as event bindings now always fit over all SNMP transport
protocols.
<draft-ietf-ipp-not-over-snmp-02.txt> - 19 March 2000 <draft-ietf-ipp-not-over-snmp-02.txt> - 19 March 2000
1) Renamed Printer Event notification group to Device Basic Event 1) Renamed Printer Event notification group to Device Basic Event
and 'jmPrinterEventV2Event' notification to and 'jmPrinterEventV2Event' notification to
'jmDeviceBasicV2Event', to better align with IPP and to support 'jmDeviceBasicV2Event', to better align with IPP and to support
non-printing jobs. non-printing jobs.
2) Revised 'jmDeviceBasicV2Event' notification to remove 2) Revised 'jmDeviceBasicV2Event' notification to remove
'hrDeviceStatus', 'hrPrinterStatus', 'hrDeviceStatus', 'hrPrinterStatus',
'hrPrinterDetectedErrorState' from mandatory trap bindings 'hrPrinterDetectedErrorState' from mandatory trap bindings
because they were redundant, per request of Ron Bergman. because they were redundant, per request of Ron Bergman.
3) Renamed Job Event notification group to Job Basic Event and 3) Renamed Job Event notification group to Job Basic Event and
skipping to change at page 31, line 4 skipping to change at page 29, line 44
Phone: +1 310-333-6413 Phone: +1 310-333-6413
Email: hastings@cp10.es.xerox.com Email: hastings@cp10.es.xerox.com
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
Email: imcdonal@sdsp.mc.xerox.com
12. Full Copyright Statement 12. Full Copyright Statement
Copyright (C) The Internet Society (2000). 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
 End of changes. 

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