idnits 2.17.1 draft-ietf-ipp-not-over-snmp-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([RFC-2707], [RFC2707]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? RFC 2119 keyword, line 180: '... IPP Clients MAY subscribe for IPP N...' RFC 2119 keyword, line 186: '...ption operations MAY be used to create...' RFC 2119 keyword, line 187: '...P Subscription objects and MAY specify...' RFC 2119 keyword, line 196: '... MAY be used to create SNMP subscrip...' RFC 2119 keyword, line 198: '...a SNMP, the IPP Client MAY use an SNMP...' (30 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (6 July 2000) is 8694 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC 2707' is mentioned on line 97, but not defined == Missing Reference: 'IPP-PRO' is mentioned on line 102, but not defined == Missing Reference: 'RFC-2119' is mentioned on line 115, but not defined == Unused Reference: 'RFC-1759' is defined on line 1074, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'IPP-MOD' -- Possible downref: Non-RFC (?) normative reference: ref. 'IPP-NOT' -- Possible downref: Non-RFC (?) normative reference: ref. 'IPP-PROG' ** Obsolete normative reference: RFC 1759 (Obsoleted by RFC 3805) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2576 (Obsoleted by RFC 3584) ** Downref: Normative reference to an Informational RFC: RFC 2707 Summary: 10 errors (**), 0 flaws (~~), 6 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Printing Protocol Working Group Tom Hastings 2 INTERNET DRAFT Xerox 3 Expires 6 January 2001 Ira McDonald 4 High North 5 6 July 2000 7 Internet Printing Protocol (IPP): 8 Notifications over SNMP via Job Monitoring MIB Traps 9 11 Copyright (C) The Internet Society (2000). All Rights Reserved. 13 Status of this Memo 15 This document is an Internet-Draft and is in full conformance with 16 all provisions of Section 10 of RFC2026. Internet-Drafts are working 17 documents of the Internet Engineering Task Force (IETF), its areas, 18 and its working groups. Note that other groups may also distribute 19 working documents as Internet-Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 Abstract 34 This document is a submission to the Internet Printing Protocol 35 Working Group of the Internet Engineering Task Force (IETF). 36 Comments should be submitted to the ipp@pwg.org mailing list. 38 This document proposes a mapping of IPP notifications over SNMP via 39 new service and job trap extensions defined for the Job Monitoring 40 MIB [RFC-2707]. This mapping may be used to deliver printer 41 notifications for any printer (not just IPP-capable ones) and also 42 job notifications for any job (not just ones submitted via IPP). 44 This document proposes (4) new object groups and (4) new SNMP traps 45 for addition to the Job Monitoring MIB [RFC 2707]. A working copy of 46 this proposal integrated into the original Job Monitoring MIB ASN.1 47 is at: 48 ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/jmp-trap-000706.mib 49 Table of Contents 51 1. Introduction ............................................... 3 52 1.1. Terminology for Conformance ............................ 3 53 2. SNMP Network Management Framework .......................... 3 54 3. Managed Object Mapping ..................................... 4 55 3.1. SNMP Mapping for IPP Notifications ..................... 4 56 3.1.1. SNMP Mapping for IPP Printer Events ................ 4 57 3.1.2. SNMP Mapping for IPP Job Events .................... 5 58 3.2. Subscription for IPP Notifications ..................... 6 59 3.2.1. Subscription via IPP ............................... 6 60 3.2.2. Subscription via SNMP .............................. 6 61 3.3. Relationship to other MIBs ............................. 7 62 3.3.1. MIB-II (RFC 1213) .................................. 7 63 3.3.2. Host Resources MIB (RFC 2790) ...................... 7 64 3.3.3. Printer MIB (RFC 1759) ............................. 7 65 4. Managed Object Definitions ................................. 8 66 4.1. Notification Definitions ............................... 8 67 4.1.1. Service Basic Event - Trap ......................... 8 68 4.1.2. Job Basic Event - Trap ............................. 9 69 4.1.3. Job Completed Event - Trap ......................... 11 70 4.1.4. Job Progress Event - Trap .......................... 12 71 4.2. Object Definitions ..................................... 13 72 4.2.1. Service Group - Objects ............................ 13 73 4.2.2. Service Event Group - Objects ...................... 16 74 4.2.3. Job Event Group - Objects .......................... 19 75 4.2.4. Job Progress Group - Objects ....................... 22 76 5. IANA Considerations ........................................ 24 77 6. Internationalization Considerations ........................ 24 78 7. Security Considerations .................................... 24 79 8. References ................................................. 25 80 9. Change Log ................................................. 26 81 10. Intellectual Property Notice .............................. 29 82 11. Authors' Addresses ........................................ 29 83 12. Full Copyright Statement .................................. 30 84 1. Introduction 86 This document is a submission to the Internet Printing Protocol 87 Working Group of the Internet Engineering Task Force (IETF). 88 Comments should be submitted to the ipp@pwg.org mailing list. 90 This document proposes a mapping of IPP notifications over SNMP via 91 new service and job trap extensions defined for the Job Monitoring 92 MIB [RFC-2707]. This mapping may be used to deliver printer 93 notifications for any printer (not just IPP-capable ones) and also 94 job notifications for any job (not just ones submitted via IPP). 96 This document proposes (4) new object groups and (4) new SNMP traps 97 for addition to the Job Monitoring MIB [RFC 2707]. A working copy of 98 this proposal integrated into the original Job Monitoring MIB ASN.1 99 is at: 100 ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/jmp-trap-000706.mib 102 The IPP protocol [IPP-PRO] supports passive monitoring of IPP Printer 103 and Job objects, via client polling of IPP object attributes using 104 the 'Get-Printer-Attributes' and 'Get-Job-Attributes' operations. 106 This document proposes support for dynamic monitoring of IPP Printer 107 and Job objects via SNMP traps generated by the service provider 108 (server or device). 110 1.1. Terminology for Conformance 112 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 113 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 114 document are to be interpreted per [RFC-2119]. 116 2. SNMP Network Management Framework 118 See: Section 1.1 'SNMPv1', section 1.2 'SNMPv2', and section 1.3 119 'SNMPv3' of [RFC-2576]. 121 3. Managed Object Mapping 123 3.1. SNMP Mapping for IPP Notifications 125 3.1.1. SNMP Mapping for IPP Printer Events 127 IPP Printer event attribute Job Monitoring MIB object mapping 128 --------------------------- --------------------------------- 129 version-number [no mapping - not useful] 130 status-code [implicit in each generated trap] 131 notify-sequence-number [request-id in SNMP trap header] 132 notify-charset [no mapping - strings are UTF-8] 133 notify-natural-language [no mapping - no text bindings] 134 subscription-id [no mapping] 135 notify-subscribed-event jmServiceEventNotifyEvent 136 notify-printer-uri jmServiceURI 137 printer-up-time [sysUpTime in SNMP trap bindings] 138 printer-current-time [hrSystemDate in Host Res MIB] 139 notify-user-data [no mapping] 140 notify-text [no mapping] 141 printer-state jmServiceState 142 printer-state-reasons jmServiceStateReasons 143 printer-is-accepting-jobs [jmServiceStateReasons keyword] 144 3.1.2. SNMP Mapping for IPP Job Events 146 IPP Job event attribute Job Monitoring MIB object mapping 147 ----------------------- --------------------------------- 148 version-number [no mapping - not useful] 149 status-code [implicit in each generated trap] 150 notify-sequence-number [request-id in SNMP trap header] 151 notify-charset [no mapping - strings are UTF-8] 152 notify-natural-language [no mapping - no text bindings] 153 subscription-id [no mapping] 154 notify-subscribed-event jmJobEventNotifyEvent 155 notify-printer-uri jmServiceURI 156 job-id [via jmJobState OID instance] 157 printer-up-time [sysUpTime in SNMP trap bindings] 158 printer-current-time [hrSystemDate in Host Res MIB] 159 notify-user-data [no mapping] 160 notify-text [no mapping] 161 job-state jmJobState 162 job-state-reasons jmJobEventJobStateReasons 163 [jmJobStateReasons1 plus zero or] 164 [more jobStateReasonsN in a strin 166 [job-completed and job-purged - extra bindings] 167 job-k-octets-processed jmJobKOctetsProcessed 168 job-impressions-completed jmJobImpressionsCompleted 170 [job-progress - extra bindings] 171 job-k-octets jmJobKOctetsPerCopyRequested 172 job-impressions jmJobImpressionsPerCopyRequested 173 job-copies jmProgressJobCopiesRequested 174 job-collation-type jmProgressJobCollationType 175 job-media-sheets-completed jmProgressMediaSheetsCompleted 176 sheet-completed-copy-number jmProgressSheetCompletedCopyNum 177 sheet-completed-document-number jmProgressSheetCompletedDocNum 178 3.2. Subscription for IPP Notifications 180 IPP Clients MAY subscribe for IPP Notifications delivered via SNMP by 181 either of the following two standard methods: 183 3.2.1. Subscription via IPP 185 IPP Job creation (Create-Job, Print-Job, Print-URI) and 186 Create-Subscription operations MAY be used to create per-Printer or 187 per-Job IPP Subscription objects and MAY specify 189 "notify-recipient-uri" = 'snmpnotify://hostname[.port]' 191 "notify-events" = 193 3.2.2. Subscription via SNMP 195 The SNMP Notification MIB and SNMP Target MIB (both in [RFC-2573]) 196 MAY be used to create SNMP subscriptions. 198 To create a subscription via SNMP, the IPP Client MAY use an SNMP 199 Set-Request operation to create an appropriate row in the SNMP 200 Notification MIB with the following variable-bindings: 202 1) 'snmpNotifyTag' 203 - tag of this notification - see 'snmpTargetAddrTagList' below 204 2) 'snmpNotifyType' 205 - deliver via SNMP Trap (unacknowledged) or Inform (acknowledged) 206 3) 'snmpNotifyStorageType' 207 - persistence (volatile, nonVolatile, permanent, readOnly) 209 Note: The SNMP Notification MIB uses persistence instead of the 210 lease duration supported in IPP Subscription objects. 212 To complete a subscription via SNMP, the IPP Client MAY use an SNMP 213 Set-Request operation to create an appropriate row in the SNMP Target 214 MIB with the following variable-bindings: 216 1) 'snmpTargetAddrTDomain' and 'snmpTargetAddrTAddress' 217 - notification target (client) transport protocol and address 218 (corresponds to IPP 'notify-recipient-uri') 219 2) 'snmpTargetAddressTimeout' and 'snmpTargetAddrRetryCount' 220 - retry timeout and limit (for acknowledged SNMP Inform only) 221 3) 'snmpTargetAddrTagList' 222 - tags of notifications to be sent to this target (client) 223 4) 'snmpTargetAddrParamsEntry' 224 - notification security and SNMP protocol version 225 5) 'snmpTargetAddrStorageType' 226 - persistence (volatile, nonVolatile, permanent, readOnly) 228 Note: The SNMP Target MIB uses persistence instead of the lease 229 duration supported in IPP Subscription objects. 231 3.3. Relationship to other MIBs 233 3.3.1. MIB-II (RFC 1213) 235 All SNMPv1 trap messages include 'time-stamp' which is the value of 236 the 'sysUpTime' object from MIB-II [RFC-1213]. 238 All SNMPv2 trap bindings include the 'sysUpTime' object from MIB-II 239 [RFC-1213]. 241 3.3.2. Host Resources MIB (RFC 2790) 243 The 'jmServiceTable' defined in this document MAY have a sparse 244 mapping to the 'hrDeviceTable' (same indices) in Host Resources MIB 245 [RFC-2790]. 247 3.3.3. Printer MIB (RFC 1759) 249 The 'jmServiceTable' defined in this document MAY have a sparse 250 mapping to the 'hrDeviceTable' (same indices) in Host Resources MIB 251 [RFC-2790], thus offering access to the Printer MIB via a 252 'hrDeviceIndex' value. 254 4. Managed Object Definitions 256 4.1. Notification Definitions 258 4.1.1. Service Basic Event - Trap 260 -- Service Basic Event Group (CONDITIONALLY MANDATORY) 261 -- 262 -- Implementation of this group is conditionally mandatory; 263 -- mandatory for systems which send this Service traps via SNMP. 265 -- The jmServiceBasicEventGroup consists entirely of the 266 -- jmServiceBasicV2Event notification. 268 jmServiceBasicV1Enterprise OBJECT-IDENTITY 269 STATUS current 270 DESCRIPTION 271 "The value of the enterprise-specific OID in an SNMPv1 trap 272 for a Service basic event sent by this managed system." 273 ::= { jobmonMIBNotifications 1 } 275 jmServiceBasicV2EventPrefix 276 OBJECT IDENTIFIER ::= { jmServiceBasicV1Enterprise 0 } 278 jmServiceBasicV2Event NOTIFICATION-TYPE 279 OBJECTS { 280 jmServiceEventNotifyEvent, 281 jmServiceState, 282 jmServiceStateReasons 283 } 284 STATUS current 285 DESCRIPTION 286 "This SMIv2 trap corresponds to an IPP Printer basic event. 288 The value of 'jmServiceIndex' for 289 use with 'jmServiceTable' for this Service is conveyed in the 290 instance qualifier (OID suffix) of 'jmServiceState'. 292 This trap is sent when requested by a prior subscription. 293 The subscribed event type is in 'jmServiceEventNotifyEvent'. 295 Standard Printer event types defined in [IPP-NOT] are: 296 - 'printer-state-changed' 297 - 'printer-restarted' 298 - 'printer-shutdown' 300 - 'printer-config-changed' 301 - 'printer-media-changed' 302 - 'printer-finishings-changed' 303 - 'printer-queue-order-changed' 304 - 'printer-full' 305 - 'printer-no-longer-full' 306 - 'printer-almost-idle' 307 - 'printer-not-almost-idle' 309 Standard Service event types generalized from [IPP-NOT] are: 310 - 'service-state-changed' 311 - 'service-restarted' 312 - 'service-shutdown' 313 - 'service-config-changed' 314 - 'service-media-changed' 315 - 'service-finishings-changed' 316 - 'service-queue-order-changed' 317 - 'service-full' 318 - 'service-no-longer-full' 319 - 'service-almost-idle' 320 - 'service-not-almost-idle' 321 - and (optionally) vendor extension event types 323 Additional variable-bindings SHOULD be appended to this trap: 324 - Systems with the Host Resources MIB (RFC 2790) SHOULD add 325 'hrSystemDate' 326 (compare to IPP 'printer-current-time') 328 Additional variable-bindings MAY be appended to this trap 329 for all printer-specific events: 330 - Systems with the Host Resources MIB (RFC 2790) MAY add 331 'hrDeviceStatus' 332 (compare to IPP 'printer-state') 333 'hrPrinterStatus' 334 (compare to IPP 'printer-state') and 335 'hrPrinterDetectedErrorState' 336 (compare to IPP 'printer-state-reasons') 338 Systems MAY add other variable-bindings from any MIB. 340 See: Section 5.3.2 'notify-events' in [IPP-NOT]; 341 Section 8.1 'notify-subscribed-event' in [IPP-NOT]; 342 Section 9 'Event Notification Content' in [IPP-NOT]." 343 ::= { jmServiceBasicV2EventPrefix 1 } 345 4.1.2. Job Basic Event - Trap 347 -- Job Basic Event Group (CONDITIONALLY MANDATORY) 348 -- 349 -- Implementation of this group is conditionally mandatory; 350 -- mandatory for systems which send this Job traps via SNMP. 352 -- The jmJobBasicEventGroup consists entirely of the 353 -- jmJobBasicV2Event notification. 355 jmJobBasicV1Enterprise OBJECT-IDENTITY 356 STATUS current 357 DESCRIPTION 358 "The value of the enterprise-specific OID in an SNMPv1 trap 359 for a Job basic event sent by this managed system." 360 ::= { jobmonMIBNotifications 2 } 362 jmJobBasicV2EventPrefix 363 OBJECT IDENTIFIER ::= { jmJobBasicV1Enterprise 0 } 365 jmJobBasicV2Event NOTIFICATION-TYPE 366 OBJECTS { 367 jmJobEventNotifyEvent, 368 jmJobState, 369 jmJobEventJobStateReasons 370 } 371 STATUS current 372 DESCRIPTION 373 "This SMIv2 trap corresponds to an IPP Job basic event. 375 The values of 'jmGeneralJobSetIndex' and 'jmJobIndex' for 376 use with 'jmJobTable' for this Job are conveyed in the 377 instance qualifier (OID suffix) of 'jmJobState'. 379 This trap is sent when requested by a prior subscription. 380 The subscribed event type is in 'jmJobEventNotifyEvent'. 382 Event types reported via 'jmJobBasicV2Event' include: 383 - 'job-state-changed' 384 - 'job-created' 385 - 'job-completed' 386 - 'job-purged' 387 - 'job-config-changed' 388 - and (optionally) vendor extension event types 390 Additional variable-bindings SHOULD be appended to this trap: 391 - Systems with the Host Resources MIB (RFC 2790) SHOULD add 392 'hrSystemDate' 393 (compare to IPP 'printer-current-time') 395 Systems MAY add other variable-bindings from any MIB. 397 See: Section 5.3.2 'notify-events' in [IPP-NOT]; 398 Section 8.1 'notify-subscribed-event' in [IPP-NOT]; 399 Section 9 'Event Notification Content' in [IPP-NOT]." 401 ::= { jmJobBasicV2EventPrefix 1 } 403 4.1.3. Job Completed Event - Trap 405 -- Job Completed Event Group (CONDITIONALLY MANDATORY) 406 -- 407 -- Implementation of this group is conditionally mandatory; 408 -- mandatory for systems which send this Job traps via SNMP. 410 jmJobCompletedV1Enterprise OBJECT-IDENTITY 411 STATUS current 412 DESCRIPTION 413 "The value of the enterprise-specific OID in an SNMPv1 trap 414 for a Job completed event sent by this managed system." 415 ::= { jobmonMIBNotifications 3 } 417 jmJobCompletedV2EventPrefix 418 OBJECT IDENTIFIER ::= { jmJobCompletedV1Enterprise 0 } 420 jmJobCompletedV2Event NOTIFICATION-TYPE 421 OBJECTS { 422 jmJobEventNotifyEvent, 423 jmJobState, 424 jmJobEventJobStateReasons, 425 jmJobKOctetsProcessed, 426 jmJobImpressionsCompleted 427 } 428 STATUS current 429 DESCRIPTION 430 "This SMIv2 trap corresponds to an IPP 'job-completed' event. 432 The values of 'jmGeneralJobSetIndex' and 'jmJobIndex' for 433 use with 'jmJobTable' for this Job are conveyed in the 434 instance qualifier (OID suffix) of 'jmJobState'. 436 This trap is sent when requested by a prior subscription. 437 The subscribed event type is in 'jmJobEventNotifyEvent'. 439 Event types reported via 'jmJobCompletedV2Event' include: 440 - 'job-completed' 441 - 'job-purged' 442 - and (optionally) vendor extension event types 444 Additional variable-bindings SHOULD be appended to this trap: 445 - Systems with the Host Resources MIB (RFC 2790) SHOULD add 446 'hrSystemDate' 447 (compare to IPP 'printer-current-time') 449 Systems MAY add other variable-bindings from any MIB. 451 See: Section 5.3.2 'notify-events' in [IPP-NOT]; 452 Section 8.1 'notify-subscribed-event' in [IPP-NOT]; 453 Section 9 'Event Notification Content' in [IPP-NOT]." 454 ::= { jmJobCompletedV2EventPrefix 1 } 456 4.1.4. Job Progress Event - Trap 458 -- Job Progress Event Group (CONDITIONALLY MANDATORY) 459 -- 460 -- Implementation of this group is conditionally mandatory; 461 -- mandatory for systems which send this Job traps via SNMP. 463 jmJobProgressV1Enterprise OBJECT-IDENTITY 464 STATUS current 465 DESCRIPTION 466 "The value of the enterprise-specific OID in an SNMPv1 trap 467 for a Job progress event sent by this managed system." 468 ::= { jobmonMIBNotifications 4 } 470 jmJobProgressV2EventPrefix 471 OBJECT IDENTIFIER ::= { jmJobProgressV1Enterprise 0 } 473 jmJobProgressV2Event NOTIFICATION-TYPE 474 OBJECTS { 475 jmJobKOctetsPerCopyRequested, 476 jmJobKOctetsProcessed, 477 jmJobImpressionsPerCopyRequested, 478 jmJobImpressionsCompleted, 479 jmProgressJobCopiesRequested, 480 jmProgressJobCollationType, 481 jmProgressMediaSheetsCompleted, 482 jmProgressSheetCompletedCopyNum, 483 jmProgressSheetCompletedDocNum 484 } 485 STATUS current 486 DESCRIPTION 487 "This SMIv2 trap corresponds to an IPP 'job-progress' event. 489 The values of 'jmGeneralJobSetIndex' and 'jmJobIndex' for 490 use with 'jmJobTable' for this Job are conveyed in the 491 instance qualifier (OID suffix) of 'jmJobKOctetsProcessed'. 493 This trap is sent when requested by a prior subscription. 494 The event type is 'job-progress'. 496 Additional variable-bindings SHOULD be appended to this trap: 497 - Systems with the Host Resources MIB (RFC 2790) SHOULD add 498 'hrSystemDate' 499 (compare to IPP 'printer-current-time') 501 Systems MAY add other variable-bindings from any MIB. 503 See: Section 5.3.2 'notify-events' in [IPP-NOT]; 504 Section 8.1 'notify-subscribed-event' in [IPP-NOT]; 505 Section 9 'Event Notification Content' in [IPP-NOT]." 506 ::= { jmJobProgressV2EventPrefix 1 } 508 4.2. Object Definitions 510 4.2.1. Service Group - Objects 512 -- The Service Group (CONDITIONALLY MANDATORY) 513 -- 514 -- Implementation of this group is conditionally mandatory; 515 -- mandatory for systems which show Service state via SNMP. 517 -- The jmServiceGroup consists entirely of the jmServiceTable 519 jmService OBJECT IDENTIFIER ::= { jobmonMIBObjects 7 } 521 jmServiceTable OBJECT-TYPE 522 SYNTAX SEQUENCE OF JmServiceEntry 523 MAX-ACCESS not-accessible 524 STATUS current 525 DESCRIPTION 526 "The jmServiceTable consists of basic service state and status 527 information for each service which offers one or more job 528 services on this managed system. 530 An entry SHALL exist in this table for each service, no matter 531 what the state of that service. A service MAY support multiple 532 configured job sets and configured devices. 534 See: 'jmServiceJobSetsConfigured' and 535 'jmServiceDevicesConfigured' bit-arrays in this MIB." 536 ::= { jmService 1 } 538 jmServiceEntry OBJECT-TYPE 539 SYNTAX JmServiceEntry 540 MAX-ACCESS not-accessible 541 STATUS current 542 DESCRIPTION 543 "Basic service state and status information." 544 INDEX { jmServiceIndex } 545 ::= { jmServiceTable 1 } 547 JmServiceEntry ::= SEQUENCE { 548 jmServiceIndex Integer32 (1..2147483647), 549 jmServiceName JmUTF8StringTC (SIZE (0..63)), 550 jmServiceURI JmUTF8StringTC (SIZE (0..63)), 551 jmServiceJobServiceTypes JmJobServiceTypesTC, 552 jmServiceJobSetsConfigured OCTET STRING (SIZE (0..255)), 553 jmServiceDevicesConfigured OCTET STRING (SIZE (0..255)), 554 jmServiceState JmServiceStateTC, 555 jmServiceStateReasons SnmpAdminString (SIZE (0..255)) 556 } 558 jmServiceIndex OBJECT-TYPE 559 SYNTAX Integer32 (1..2147483647) 560 MAX-ACCESS not-accessible 561 STATUS current 562 DESCRIPTION 563 "The unique identifier for this service on this managed system. 565 See: 'jmServiceEventServiceIndex' object in this MIB." 566 ::= { jmServiceEntry 1 } 568 jmServiceName OBJECT-TYPE 569 SYNTAX JmUTF8StringTC (SIZE(0..63)) -- 127 in IPP 570 MAX-ACCESS read-only 571 STATUS current 572 DESCRIPTION 573 "The human readable name of this managed service. 575 See: 'deviceNameRequested' job attribute in this MIB; 576 'physicalDevice' job attribute in this MIB; 577 Section 4.4.4 'printer-name' in [IPP-MOD]." 578 DEFVAL { ''H } -- no service name 579 ::= { jmServiceEntry 2 } 581 jmServiceURI OBJECT-TYPE 582 SYNTAX JmUTF8StringTC (SIZE(0..63)) -- 1023 in IPP 583 MAX-ACCESS read-only 584 STATUS current 585 DESCRIPTION 586 "A URI for this managed service (valid for job services). 588 See: Section 4.3.3 'job-printer-uri' in [IPP-MOD]; 589 Section 4.4.1 'printer-uri-supported' in [IPP-MOD]." 590 DEFVAL { ''H } -- no service URI 591 ::= { jmServiceEntry 3 } 593 jmServiceJobServiceTypes OBJECT-TYPE 594 SYNTAX JmJobServiceTypesTC 595 MAX-ACCESS read-only 596 STATUS current 597 DESCRIPTION 598 "The types of job services supported by this managed service. 600 See: 'JmJobServiceTypesTC' textual convention in this MIB; 601 'jobServiceTypes' job attribute in this MIB." 602 DEFVAL { 0 } -- no job services 603 ::= { jmServiceEntry 4 } 605 jmServiceJobSetsConfigured OBJECT-TYPE 606 SYNTAX OCTET STRING (SIZE(0..255)) 607 MAX-ACCESS read-only 608 STATUS current 609 DESCRIPTION 610 "A bit-array that specifies the job sets configured for this 611 service, where each bit '2**n' is set if 'jmGeneralJobSetIndex' 612 is a configured job set. Uses network byte order (big-endian) 613 rules - the high-order bit of the first octet corresponds to 614 'jmGeneralJobSetIndex' of '0' (reserved) - the low-order bit of 615 the first octet corresponds to 'jmGeneralJobSetIndex' of '7'. 616 Supports values of 'jmGeneralJobSetIndex' from '1' to '2039'. 618 Compare to the BITS pseudotype defined in IETF SMIv2 (RFC 2578) 619 which has the same bit ordering rules (big-endian). 621 See: 'queueNameRequested' job attribute in this MIB; 622 'jmGeneralJobSetIndex' table index in this MIB." 623 DEFVAL { ''H } -- no job sets configured 624 ::= { jmServiceEntry 5 } 626 jmServiceDevicesConfigured OBJECT-TYPE 627 SYNTAX OCTET STRING (SIZE(0..255)) 628 MAX-ACCESS read-only 629 STATUS current 630 DESCRIPTION 631 "A bit-array that specifies the devices configured for this 632 service, where each bit '2**n' is set if 'hrDeviceIndex' 633 is a configured device. Uses network byte order (big-endian) 634 rules - the high-order bit of the first octet corresponds to 635 'hrDeviceIndex' of '0' (reserved) - the low-order bit of 636 the first octet corresponds to 'hrDeviceIndex' of '7'. 637 Supports values of 'hrDeviceIndex' from '1' to '2039'. 639 Compare to the BITS pseudotype defined in IETF SMIv2 (RFC 2578) 640 which has the same bit ordering rules (big-endian). 642 See: 'physicalDevice' job attribute in this MIB; 643 'hrDeviceIndex' in IETF Host MIB (RFC 2790)." 644 DEFVAL { ''H } -- no devices configured 645 ::= { jmServiceEntry 6 } 647 jmServiceState OBJECT-TYPE 648 SYNTAX JmServiceStateTC 649 MAX-ACCESS read-only 650 STATUS current 651 DESCRIPTION 652 "The current state of this managed service. 654 See: 'jmServiceEventServiceState' object in this MIB; 655 'jmJobState' object in this MIB; 656 Section 4.4.11 'printer-state' in [IPP-MOD]." 657 DEFVAL { unknown } -- unknown service state 658 ::= { jmServiceEntry 7 } 660 jmServiceStateReasons OBJECT-TYPE 661 SYNTAX SnmpAdminString (SIZE (0..255)) -- multi-valued in IPP 662 MAX-ACCESS read-only 663 STATUS current 664 DESCRIPTION 665 "The service state reasons associated with this service state 666 (as a comma-separated list) or the empty string (if none). 668 See: 'jmServiceEventServiceStateReasons' object in this MIB; 669 'jmJobStateReasons1' object in this MIB; 670 Section 4.4.12 'printer-state-reasons' in [IPP-MOD]." 671 DEFVAL { ''H } -- no service state reasons 672 ::= { jmServiceEntry 8 } 674 4.2.2. Service Event Group - Objects 676 -- The Service Event Group (CONDITIONALLY MANDATORY) 677 -- 678 -- Implementation of this group is conditionally mandatory; 679 -- mandatory for systems which show Service events via SNMP. 681 -- The jmServiceEventGroup consists entirely of the jmServiceEventTable 683 jmServiceEvent OBJECT IDENTIFIER ::= { jobmonMIBObjects 8 } 685 jmServiceEventTable OBJECT-TYPE 686 SYNTAX SEQUENCE OF JmServiceEventEntry 687 MAX-ACCESS not-accessible 688 STATUS current 689 DESCRIPTION 690 "The jmServiceEventTable contains service event entries for the 691 services which offer job services on this managed system." 692 ::= { jmServiceEvent 1 } 694 jmServiceEventEntry OBJECT-TYPE 695 SYNTAX JmServiceEventEntry 696 MAX-ACCESS not-accessible 697 STATUS current 698 DESCRIPTION 699 "Basic service event information." 700 INDEX { jmServiceEventIndex } 701 ::= { jmServiceEventTable 1 } 703 JmServiceEventEntry ::= SEQUENCE { 704 jmServiceEventIndex Integer32 (1..2147483647), 705 jmServiceEventNotifyEvent SnmpAdminString (SIZE (0..63)), 706 jmServiceEventNotifyTime TimeTicks, 707 jmServiceEventServiceIndex Integer32 (1..2147483647), 708 jmServiceEventServiceState JmServiceStateTC, 709 jmServiceEventServiceStateReasons SnmpAdminString (SIZE (0..255)) 710 } 712 jmServiceEventIndex OBJECT-TYPE 713 SYNTAX Integer32 (1..2147483647) 714 MAX-ACCESS not-accessible 715 STATUS current 716 DESCRIPTION 717 "The unique identifier for this event on this managed system." 718 ::= { jmServiceEventEntry 1 } 720 jmServiceEventNotifyEvent OBJECT-TYPE 721 SYNTAX SnmpAdminString (SIZE (0..63)) -- 255 in [IPP-NOT] 722 MAX-ACCESS read-only 723 STATUS current 724 DESCRIPTION 725 "The event type that created this row in 'jmServiceEventTable'. 727 Standard Printer event types defined in [IPP-NOT] are: 728 - 'printer-state-changed' 729 - 'printer-restarted' 730 - 'printer-shutdown' 731 - 'printer-config-changed' 732 - 'printer-media-changed' 733 - 'printer-finishings-changed' 734 - 'printer-queue-order-changed' 735 - 'printer-full' 736 - 'printer-no-longer-full' 737 - 'printer-almost-idle' 738 - 'printer-not-almost-idle' 740 Standard Service event types generalized from [IPP-NOT] are: 741 - 'service-state-changed' 742 - 'service-restarted' 743 - 'service-shutdown' 744 - 'service-config-changed' 745 - 'service-media-changed' 746 - 'service-finishings-changed' 747 - 'service-queue-order-changed' 748 - 'service-full' 749 - 'service-no-longer-full' 750 - 'service-almost-idle' 751 - 'service-not-almost-idle' 753 Conformance: The natural language for keywords 754 in subscribed event type SHALL always be US English. 756 Conformance: This subscribed event type SHALL be valid 757 and reported in ALL Job Monitoring MIB notifications. 759 See: Section 8.1 'notify-subscribed-event' in [IPP-NOT]." 760 DEFVAL { ''H } -- no notify subscribed event 761 ::= { jmServiceEventEntry 2 } 763 jmServiceEventNotifyTime OBJECT-TYPE 764 SYNTAX TimeTicks 765 MAX-ACCESS read-only 766 STATUS current 767 DESCRIPTION 768 "The time of this service event. 770 Usage: Conforming management agents, which MUST implement the 771 IETF MIB-II (RFC 1213), SHALL set 'jmServiceEventNotifyTime' to 772 'sysUpTime' when a service event row is created. 774 See: 'sysUpTime' in IETF MIB-II (RFC 1213); 775 Section 5.4.4 'notify-printer-up-time' in [IPP-NOT]; 776 Section 4.4.29 'printer-up-time' in [IPP-MOD]." 777 ::= { jmServiceEventEntry 3 } 779 jmServiceEventServiceIndex OBJECT-TYPE 780 SYNTAX Integer32 (1..2147483647) 781 MAX-ACCESS read-only 782 STATUS current 783 DESCRIPTION 784 "The unique identifier for this service on this managed system. 786 See: 'jmServiceIndex' object in this MIB." 787 ::= { jmServiceEventEntry 4 } 789 jmServiceEventServiceState OBJECT-TYPE 790 SYNTAX JmServiceStateTC 791 MAX-ACCESS read-only 792 STATUS current 793 DESCRIPTION 794 "The state of this managed service at the time of this event. 796 See: 'jmServiceState' object in this MIB; 797 'jmJobState' object in this MIB; 798 Section 4.4.11 'printer-state' in [IPP-MOD]." 799 DEFVAL { unknown } -- unknown service state 800 ::= { jmServiceEventEntry 5 } 802 jmServiceEventServiceStateReasons OBJECT-TYPE 803 SYNTAX SnmpAdminString (SIZE (0..255)) -- multi-valued in IPP 804 MAX-ACCESS read-only 805 STATUS current 806 DESCRIPTION 807 "The service state reasons associated with this service state 808 (as a comma-separated list) or the empty string (if none). 810 See: 'jmServiceStateReasons' object in this MIB; 811 'jmJobStateReasons1' object in this MIB; 812 Section 4.4.12 'printer-state-reasons' in [IPP-MOD]." 813 DEFVAL { ''H } -- no service state reasons 814 ::= { jmServiceEventEntry 6 } 816 4.2.3. Job Event Group - Objects 818 -- The Job Event Group (CONDITIONALLY MANDATORY) 819 -- 820 -- Implementation of this group is conditionally mandatory; 821 -- mandatory for systems which show Job events via SNMP. 823 -- The jmJobEventGroup consists entirely of the jmJobEventTable 825 jmJobEvent OBJECT IDENTIFIER ::= { jobmonMIBObjects 9 } 827 jmJobEventTable OBJECT-TYPE 828 SYNTAX SEQUENCE OF JmJobEventEntry 829 MAX-ACCESS not-accessible 830 STATUS current 831 DESCRIPTION 832 "The jmJobEventTable contains job event entries for the 833 jobs present on this managed system." 834 ::= { jmJobEvent 1 } 836 jmJobEventEntry OBJECT-TYPE 837 SYNTAX JmJobEventEntry 838 MAX-ACCESS not-accessible 839 STATUS current 840 DESCRIPTION 841 "Basic job event information." 843 INDEX { jmJobEventIndex } 844 ::= { jmJobEventTable 1 } 846 JmJobEventEntry ::= SEQUENCE { 847 jmJobEventIndex Integer32 (1..2147483647), 848 jmJobEventNotifyEvent SnmpAdminString (SIZE (0..63)), 849 jmJobEventNotifyTime TimeTicks, 850 jmJobEventJobSetIndex Integer32 (1..32767), 851 jmJobEventJobIndex Integer32 (1..2147483647), 852 jmJobEventJobState JmJobStateTC, 853 jmJobEventJobStateReasons OCTET STRING (SIZE (4..16)) 854 } 856 jmJobEventIndex OBJECT-TYPE 857 SYNTAX Integer32 (1..2147483647) 858 MAX-ACCESS not-accessible 859 STATUS current 860 DESCRIPTION 861 "The unique identifier for this event on this managed system." 862 ::= { jmJobEventEntry 1 } 864 jmJobEventNotifyEvent OBJECT-TYPE 865 SYNTAX SnmpAdminString (SIZE (0..63)) -- 255 in [IPP-NOT] 866 MAX-ACCESS read-only 867 STATUS current 868 DESCRIPTION 869 "The event type that created this row in 'jmJobEventTable'. 871 Standard Job event types defined in [IPP-NOT] are: 872 - 'job-state-changed' 873 - 'job-created' 874 - 'job-completed' 875 - 'job-purged' 876 - 'job-config-changed' 877 - 'job-progress' 879 Conformance: The natural language for keywords 880 in subscribed event type SHALL always be US English. 882 Conformance: This subscribed event type SHALL be valid 883 and reported in ALL Job Monitoring MIB notifications. 885 See: Section 8.1 'notify-subscribed-event' in [IPP-NOT]." 886 DEFVAL { ''H } -- no notify subscribed event 887 ::= { jmJobEventEntry 2 } 889 jmJobEventNotifyTime OBJECT-TYPE 890 SYNTAX TimeTicks 891 MAX-ACCESS read-only 892 STATUS current 893 DESCRIPTION 894 "The time of this job event. 896 Usage: Conforming management agents, which MUST implement the 897 IETF MIB-II (RFC 1213), SHALL set 'jmJobEventNotifyTime' to 898 'sysUpTime' when a job event row is created. 900 See: 'sysUpTime' in IETF MIB-II (RFC 1213); 901 Section 5.4.4 'notify-printer-up-time' in [IPP-NOT]; 902 Section 4.4.29 'printer-up-time' in [IPP-MOD]." 903 ::= { jmJobEventEntry 3 } 905 jmJobEventJobSetIndex OBJECT-TYPE 906 SYNTAX Integer32 (1..32767) 907 MAX-ACCESS read-only 908 STATUS current 909 DESCRIPTION 910 "The unique identifier for this job set on this managed system. 912 See: 'jmGeneralJobSetIndex' object in this MIB." 913 ::= { jmJobEventEntry 4 } 915 jmJobEventJobIndex OBJECT-TYPE 916 SYNTAX Integer32 (1..2147483647) 917 MAX-ACCESS read-only 918 STATUS current 919 DESCRIPTION 920 "The unique identifier for this job on this managed system, 921 when prefixed with 'jmJobEventJobSetIndex'. 923 See: 'jmJobIndex' object in this MIB." 924 ::= { jmJobEventEntry 5 } 926 jmJobEventJobState OBJECT-TYPE 927 SYNTAX JmJobStateTC 928 MAX-ACCESS read-only 929 STATUS current 930 DESCRIPTION 931 "The state of this managed job at the time of this event. 933 See: 'jmJobState' in this MIB; 934 Section 4.3.7 'job-state' in [IPP-MOD]." 935 DEFVAL { unknown } -- unknown job state 936 ::= { jmJobEventEntry 6 } 938 jmJobEventJobStateReasons OBJECT-TYPE 939 SYNTAX OCTET STRING (SIZE (4..16)) -- multi-valued in IPP 940 MAX-ACCESS read-only 941 STATUS current 942 DESCRIPTION 943 "The job state reasons associated with this job state 944 represented as one to four concatenated 32-bit integers 945 in network byte order (big-endian). 947 Usage: Conforming management stations SHALL always report the 948 value of the object 'jmJobStateReasons1' in the first four 949 octets of 'jmJobEventJobStateReasons' and SHOULD report values 950 of the attributes 'jobStateReasons2', 'jobStateReasons3', and 951 'jobStateReasons4' in subsequent octets. 953 See: 'jmJobStateReasons1' in this MIB; 954 Section 4.3.8 'job-state-reasons' in [IPP-MOD]." 955 DEFVAL { '00000000'H } -- no job state reasons 956 ::= { jmJobEventEntry 7 } 958 4.2.4. Job Progress Group - Objects 960 -- The Job Progress Group (CONDITIONALLY MANDATORY) 961 -- 962 -- Implementation of this group is conditionally mandatory; 963 -- mandatory for systems which send Job progress traps via SNMP. 965 -- The jmProgressGroup consists entirely of leaf objects for traps 967 jmProgress OBJECT IDENTIFIER ::= { jobmonMIBObjects 10 } 969 jmProgressJobCopiesRequested OBJECT-TYPE 970 SYNTAX Integer32 (-2..2147483647) 971 MAX-ACCESS read-only 972 STATUS current 973 DESCRIPTION 974 "The number of copies of this job requested by the client. 976 See: 'jobCopiesRequested' attribute in this MIB." 977 DEFVAL { -2 } -- unknown job copies 978 ::= { jmProgress 1 } 980 jmProgressJobCollationType OBJECT-TYPE 981 SYNTAX JmJobCollationTypeTC 982 MAX-ACCESS read-only 983 STATUS current 984 DESCRIPTION 985 "The number of copies of this job requested by the client. 987 See: 'jobCollationType' attribute in this MIB; 988 'job-collation-type' in [IPP-PROG]; 989 Section 9 'Event Notification Content' in [IPP-NOT]." 990 DEFVAL { unknown } -- unknown job collation type 991 ::= { jmProgress 2 } 993 jmProgressMediaSheetsCompleted OBJECT-TYPE 994 SYNTAX Integer32 (-2..2147483647) 995 MAX-ACCESS read-only 996 STATUS current 997 DESCRIPTION 998 "The number of media sheets completed for this job. 1000 See: 'sheetsCompleted' attribute in this MIB; 1001 Section 4.3.18.3 'job-media-sheets-completed' 1002 in [IPP-MOD]; 1003 Section 9 'Event Notification Content' in [IPP-NOT]." 1004 DEFVAL { -2 } -- unknown job progress 1005 ::= { jmProgress 3 } 1007 jmProgressSheetCompletedCopyNum OBJECT-TYPE 1008 SYNTAX Integer32 (-2..2147483647) 1009 MAX-ACCESS read-only 1010 STATUS current 1011 DESCRIPTION 1012 "The number of the job copy currently being stacked for the 1013 current document or zero (if none) or '-2' (unknown). 1015 See: 'sheetCompletedCopyNumber' attribute in this MIB; 1016 'sheet-completed-copy-number' in [IPP-PROG]; 1017 Section 9 'Event Notification Content' in [IPP-NOT]." 1018 DEFVAL { -2 } -- unknown sheet complete copy 1019 ::= { jmProgress 4 } 1021 jmProgressSheetCompletedDocNum OBJECT-TYPE 1022 SYNTAX Integer32 (-2..2147483647) 1023 MAX-ACCESS read-only 1024 STATUS current 1025 DESCRIPTION 1026 "The number of the job document currently being stacked for the 1027 current job or zero (if none) or '-2' (unknown). 1029 See: 'sheetCompletedDocumentNumber' attribute in this MIB; 1030 'sheet-completed-document-number' in [IPP-PROG]; 1031 Section 9 'Event Notification Content' in [IPP-NOT]." 1032 DEFVAL { -2 } -- unknown sheet complete doc 1033 ::= { jmProgress 5 } 1035 5. IANA Considerations 1037 None. 1039 6. Internationalization Considerations 1041 The 'jmServiceStateReasons', 'jmServiceEventServiceStateReasons', 1042 'jmServiceEventNotifyEvent', and 'jmJobEventNotifyEvent', text string 1043 objects defined in this document are of type 'SnmpAdminString' (UTF-8 1044 stream-encoded ISO 10646/Unicode text) defined in the SNMPv3 1045 Framework MIB [RFC-2571]. The natural language of these objects is 1046 US English (they contain keywords). 1048 7. Security Considerations 1050 This IPP Notifications over SNMP mapping defines only 'read-only' 1051 objects. It is suitable for use with any version of SNMP, as no 1052 update security is required (because no configuration updates are 1053 supported). 1055 No sensitive information is available via IPP Notifications over 1056 SNMP. 1058 8. References 1060 [IPP-MOD] R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell. 1061 IPP/1.1 Model and Semantics, 1062 (work-in-progress), May 2000. 1064 [IPP-NOT] S. Isaacson, J. Martin, R. deBry, T. Hastings, M. Shepherd, 1065 R. Bergman. IPP Event Notification Specification, 1066 (work-in-progress), March 2000. 1068 [IPP-PROG] T. Hastings, R. Bergman, H. Lewis. Proposed Job Progress 1069 Attributes for IPP, 1070 (work-in-progress), February 2000. 1072 [RFC-1213] K. McCloghrie, M. Rose. MIB-II, RFC 1213, March 1991. 1074 [RFC-1759] R. Smith, F. Wright, T. Hastings, S. Zilles, 1075 J. Gyllenskog. Printer MIB, RFC 1759, March 1995. 1077 [RFC-2571] D. Harrington, R. Presuhn, B. Wijnen. Architecture for 1078 SNMP Management Frameworks, RFC 2571, April 1999. 1080 [RFC-2573] D. Levi, P. Meyer, B. Stewart. SNMP Applications, RFC 1081 2573, April 1999. 1083 [RFC-2576] R. Frye, D. Levi, S. Routhier, B. Wijnen. Coexistence 1084 between Version 1, Version 2, and Version 3 of the Internet-standard 1085 Network Management Framework, RFC 2576, March 2000. 1087 [RFC-2707] R. Bergman, T. Hastings, S. Isaacson, H. Lewis. Job 1088 Monitoring MIB v1.0, RFC 2707, November 1999 1090 [RFC-2790] P. Grillo, S. Waldbusser. Host Resources MIB, RFC 2790, 1091 March 2000. 1093 9. Change Log 1095 Changes in reverse chronological order (most recent first). 1097 - 6 July 2000 1098 1) Added 'SnmpAdminString' to IMPORTS clause for new objects. 1099 2) Corrected OID in MODULE-IDENTITY to use forward reference to 1100 definition of 'pwg' from 'enterprises' and 'mibs' from 'pwg'. 1101 3) Added 'JmServiceStateTC' textual convention. 1102 4) Added 'jmMirrorAttr' and 'jmSystem' object identifiers reserved 1103 for future extensions. 1104 5) Major rewrite, per email discussion on IETF IPP WG list, to 1105 specify four new small (traditional) SNMP traps for: 1106 'jmServiceBasicV2Event' (generalized from IPP Printer event), 1107 'jmJobBasicV2Event' (corresponds IPP Job event), 1108 'jmJobCompletedV2Event' (corresponds IPP Job completed event), 1109 'jmJobProgressV2Event' (corresponds IPP Job progress event). 1110 6) Major rewrite, per email discussion on IETF IPP WG list, to 1111 specify four new SNMP object groups: 'jmServiceTable' (name, 1112 URI, state, etc. - from IPP Printer), 'jmServiceEventTable' 1113 (records IPP Printer events for polling), 'jmJobEventTable' 1114 (records IPP Job events for polling), 'jmJobProgressGroup' (leaf 1115 objects for IPP Job progress event). 1116 7) Revised section 3.1 'SNMP Mapping for IPP Printer Events' and 1117 section 3.2 'SNMP Mapping for IPP Job Events', to agree with 1118 above. 1119 8) Deleted obsolete section 3.3 'Rules for Encoding Notifications', 1120 as event bindings now always fit over all SNMP transport 1121 protocols. 1123 - 19 March 2000 1124 1) Renamed Printer Event notification group to Device Basic Event 1125 and 'jmPrinterEventV2Event' notification to 1126 'jmDeviceBasicV2Event', to better align with IPP and to support 1127 non-printing jobs. 1128 2) Revised 'jmDeviceBasicV2Event' notification to remove 1129 'hrDeviceStatus', 'hrPrinterStatus', 1130 'hrPrinterDetectedErrorState' from mandatory trap bindings 1131 because they were redundant, per request of Ron Bergman. 1132 3) Renamed Job Event notification group to Job Basic Event and 1133 'jmJobEventV2Event' notification to 'jmJobBasicV2Event', to 1134 better align with IPP and to support variant job events. 1135 4) Defined new Job Completed Event notification group and defined 1136 new Job Progress Event notification group, to better align with 1137 IPP and to support variant job events. 1138 5) Renamed Event object group to Event Binding, 1139 'jmEventPrinterState' to 'jmEventDeviceState', 1140 'jmEventPrinterStateReasons' to 'jmEventDeviceStateReasons', 1141 'jmEventPrinterIsAcceptingJobs' to 1142 'jmEventDeviceIsAcceptingJobs', to support non-printing jobs. 1143 6) Revised Event Binding object group, adding explicit objects 1144 'jmEventDeviceURI', 'jmEventDeviceName', 'jmEventJobSetIndex', 1145 'jmEventJobIndex', 'jmEventJobName', 'jmEventJobState', 1146 'jmEventJobStateReasons', 'jmEventJobKOctets', 1147 'jmEventJobKOctetsProcessed', 'jmEventJobImpressions', 1148 'jmEventJobImpressionsCompleted', 'jmEventJobMediaSheets', 1149 'jmEventJobMediaSheetsCompleted', 1150 'jmEventJobImpressionsCompletedCC', 'jmEventJobCollationType', 1151 'jmEventJobSheetCompletedCopyNum', 1152 'jmEventJobSheetCompletedDocNum', per request of Ron Bergman. 1153 7) Revised SYNTAX of 'jmEventTriggerEvent' object from from 1154 'JmUTF8StringTC' (string) to IPP-aligned enumeration, per request 1155 of Ron Bergman. 1156 8) Removed all references to Printer MIB v2, as they were of limited 1157 value, per request of Ron Bergman. 1158 9) Revised 'SNMP Mapping for IPP Printer Events' section for renamed 1159 event binding objects, per request of Ron Bergman. 1160 10) Revised 'Rules for Encoding Notifications' section to truncate 1161 additional string bindings, per request of Ron Bergman. 1162 11) Revised 'Registration via IPP' section, to change scheme name 1163 from 'ipp-snmp:' to 'snmpnotify:', per request of Ron Bergman. 1165 - 1 December 1999 1166 1) Deleted 'JmTriggerEventTC' textual convention (see below). 1167 2) Revised SYNTAX of 'jmEventTriggerEvent' object from 1168 'JmTriggerEventTC' (enumeration) to 'JmUTF8StringTC' (string), to 1169 support use of IPP standard keywords. 1170 3) Added 'jmEventPrinterState', 'jmEventPrinterStateReasons', and 1171 'jmEventPrinterIsAcceptingJobs' objects for consistency w/ 1172 [IPP-NOT] and to reduce ambiguity about printer states inherent 1173 in RFC 1759. 1174 4) Revised DESCRIPTION of 'jmPrinterEventV2Event' notification to 1175 add SHOULD (recommendation) for 'jmEventPrinterState', 1176 'jmEventPrinterStateReasons', and 'jmEventPrinterIsAcceptingJobs' 1177 objects. 1178 5) Revised 'SNMP Mapping for IPP Printer Events' section to add 1179 direct mapping of IPP notification attributes to 1180 'jmEventPrinterState', 'jmEventPrinterStateReasons', and 1181 'jmEventPrinterIsAcceptingJobs' objects. 1182 6) Revised 'Rules for Encoding Notifications' section to add 1183 'jmEventPrinterState' and 'jmEventPrinterStateReasons'. 1184 7) Revised 'IANA Considerations' section to specify there are none - 1185 no enumerated or keyword textual conventions are now defined in 1186 this document. 1187 8) Revised 'Internationalization Considerations' section to specify 1188 that US English keywords are used in 'jmEventTriggerEvent', 1189 'jmEventPrinterState', and 'jmEventPrinterStateReasons' objects 1190 and thus no explicit natural language tagging is required. 1192 - 10 October 1999 1193 1) Initial version. 1195 10. Intellectual Property Notice 1197 The IETF takes no position regarding the validity or scope of any 1198 intellectual property or other rights that might be claimed to 1199 pertain to the implementation or use of the technology described in 1200 this document or the extent to which any license under such rights 1201 might or might not be available; neither does it represent that it 1202 has made any effort to identify any such rights. Information on the 1203 IETF's procedures with respect to rights in standards-track and 1204 standards-related documentation can be found in BCP-11. Copies of 1205 claims of rights made available for publication and any assurances of 1206 licenses to be made available, or the result of an attempt made to 1207 obtain a general license or permission for the use of such 1208 proprietary rights by implementers or users of this specification can 1209 be obtained from the IETF Secretariat. 1211 The IETF invites any interested party to bring to its attention any 1212 copyrights, patents or patent applications, or other proprietary 1213 rights which may cover technology that may be required to practice 1214 this standard. Please address the information to the IETF Executive 1215 Director. 1217 11. Authors' Addresses 1219 Tom Hastings 1220 Xerox Corporation 1221 701 S Aviation Blvd, MS 834-03E 1222 El Segundo, CA 90245 1224 Phone: +1 310-333-6413 1225 Email: hastings@cp10.es.xerox.com 1227 Ira McDonald 1228 High North Inc 1229 221 Ridge Ave 1230 Grand Marais, MI 49839 1232 Phone: +1 906-494-2434 or +1 906-494-2697 1233 Email: imcdonald@sharplabs.com 1234 Email: imcdonal@sdsp.mc.xerox.com 1236 12. Full Copyright Statement 1238 Copyright (C) The Internet Society (2000). All Rights Reserved. 1240 This document and translations of it may be copied and furnished to 1241 others, and derivative works that comment on or otherwise explain it 1242 or assist in its implementation may be prepared, copied, published 1243 and distributed, in whole or in part, without restriction of any 1244 kind, provided that the above copyright notice and this paragraph are 1245 included on all such copies and derivative works. However, this 1246 document itself may not be modified in any way, such as by removing 1247 the copyright notice or references to the Internet Society or other 1248 Internet organizations, except as needed for the purpose of 1249 developing Internet standards in which case the procedures for 1250 copyrights defined in the Internet Standards process must be 1251 followed, or as required to translate it into languages other than 1252 English. 1254 The limited permissions granted above are perpetual and will not be 1255 revoked by the Internet Society or its successors or assigns. 1257 This document and the information contained herein is provided on an 1258 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1259 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1260 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1261 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1262 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.