idnits 2.17.1 draft-ietf-ipp-not-over-snmp-02.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 == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 59 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 31 pages 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]), 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 189: '... SNMP traps MAY not fit the MTU (max...' RFC 2119 keyword, line 190: '...ation generators SHALL perform this pr...' RFC 2119 keyword, line 214: '...rror (variable-bindings MUST now fit)....' RFC 2119 keyword, line 224: '...-URI) operations MAY be used to create...' RFC 2119 keyword, line 225: '...P Subscription objects and MAY specify...' (45 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 182 has weird spacing: '...nt-copy jmEve...' -- 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 (19 March 2000) is 8803 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: 'IPP-PRO' is mentioned on line 107, but not defined == Missing Reference: 'RFC-2119' is mentioned on line 119, but not defined -- 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 1514 (Obsoleted by RFC 2790) ** Obsolete normative reference: RFC 1759 (Obsoleted by RFC 3805) ** 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 (~~), 7 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 19 September 2000 Ira McDonald 4 High North 5 19 March 2000 7 Internet Printing Protocol (IPP): 8 Notifications over SNMP via Job Monitoring MIB 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 device and job traps 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) SNMP traps; and (24) SNMP leaf objects 45 (for use in various trap bindings). 47 Table of Contents 49 1. Introduction ............................................... 4 50 1.1. Terminology for Conformance ............................ 4 51 2. SNMP Network Management Framework .......................... 4 52 3. Managed Object Mapping ..................................... 5 53 3.1. SNMP Mapping for IPP Printer Events .................... 5 54 3.2. SNMP Mapping for IPP Job Events ........................ 5 55 3.3. Rules for Encoding Notifications ....................... 6 56 3.4. Registration for IPP Notifications ..................... 7 57 3.4.1. Registration via IPP ............................... 7 58 3.4.2. Registration via SNMP .............................. 7 59 3.5. Relationship to other MIBs ............................. 8 60 3.5.1. MIB-II (RFC 1213) .................................. 8 61 3.5.2. Host Resources MIB (RFC 1514) ...................... 8 62 3.5.3. Printer MIB (RFC 1759) ............................. 8 63 4. Managed Object Definitions ................................. 9 64 4.1. Device Basic Event Trap ................................ 9 65 4.1.1. jmDeviceBasicV2Event (notification) ................ 9 66 4.2. Job Basic Event Trap ................................... 10 67 4.2.1. jmJobBasicV2Event (notification) ................... 11 68 4.3. Job Completed Event Trap ............................... 11 69 4.3.1. jmJobCompletedV2Event (notification) ............... 12 70 4.4. Job Progress Event Trap ................................ 13 71 4.4.1. jmJobProgressV2Event (notification) ................ 13 72 4.5. Event Binding Group .................................... 14 73 4.5.1. jmEventTriggerEvent (object) ....................... 14 74 4.5.2. jmEventSubscriptionID (object) ..................... 15 75 4.5.3. jmEventSubscriberUserName (object) ................. 15 76 4.5.4. jmEventSubscriberUserData (object) ................. 16 77 4.5.5. jmEventDeviceURI (object) .......................... 16 78 4.5.6. jmEventDeviceName (object) ......................... 17 79 4.5.7. jmEventDeviceState (object) ........................ 17 80 4.5.8. jmEventDeviceStateReasons (object) ................. 17 81 4.5.9. jmEventDeviceIsAcceptingJobs (object) .............. 18 82 4.5.10. jmEventJobSetIndex (object) ....................... 18 83 4.5.11. jmEventJobIndex (object) .......................... 19 84 4.5.12. jmEventJobName (object) ........................... 19 85 4.5.13. jmEventJobState (object) .......................... 19 86 4.5.14. jmEventJobStateReasons (object) ................... 20 87 4.5.15. jmEventJobKOctets (object) ........................ 20 88 4.5.16. jmEventJobKOctetsProcessed (object) ............... 21 89 4.5.17. jmEventJobImpressions (object) .................... 21 90 4.5.18. jmEventJobImpressionsCompleted (object) ........... 21 91 4.5.19. jmEventJobMediaSheets (object) .................... 22 92 4.5.20. jmEventJobMediaSheetsCompleted (object) ........... 22 93 4.5.21. jmEventJobImpressionsCompletedCC (object) ......... 22 94 4.5.22. jmEventJobCollationType (object) .................. 23 95 4.5.23. jmEventJobSheetCompletedCopyNum (object) .......... 23 96 4.5.24. jmEventJobSheetCompletedDocNum (object) ........... 23 97 5. IANA Considerations ........................................ 25 98 6. Internationalization Considerations ........................ 25 99 7. Security Considerations .................................... 25 100 8. References ................................................. 26 101 9. Change Log ................................................. 27 102 10. Intellectual Property Notice .............................. 29 103 11. Authors' Addresses ........................................ 29 104 12. Full Copyright Statement .................................. 30 105 1. Introduction 107 The IPP protocol [IPP-PRO] supports passive monitoring of IPP Printer 108 and Job objects, via client polling of IPP object attributes using 109 the 'Get-Printer-Attributes' and 'Get-Job-Attributes' operations. 111 This IPP Notifications over SNMP mapping supports dynamic monitoring 112 of IPP Printer and Job objects, via server generation of SNMP traps. 114 1.1. Terminology for Conformance 116 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 117 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 118 document are to be interpreted per [RFC-2119]. 120 2. SNMP Network Management Framework 122 See: Section 1.1 'SNMPv1', section 1.2 'SNMPv2', and section 1.3 123 'SNMPv3' of [RFC-2576]. 125 3. Managed Object Mapping 127 3.1. SNMP Mapping for IPP Printer Events 129 IPP Printer event attribute Job Monitoring MIB object mapping 130 --------------------------- --------------------------------- 131 version-number [no mapping - not useful] 132 status-code [implicit in each generated trap] 133 request-id [request-id in SNMP trap header] 134 attributes-charset [no mapping - strings are UTF-8] 135 attributes-natural-language [no mapping - no text bindings] 136 printer-uri jmEventDeviceURI 137 printer-name jmEventDeviceName 138 job-id jmEventJobIndex 139 [and jmEventJobSetIndex] 140 job-name jmEventJobName 141 trigger-event jmEventTriggerEvent 142 trigger-time [sysUpTime in SNMP trap bindings] 143 trigger-date-time [hrSystemDate in Host Res MIB] 144 subscription-id jmEventSubscriptionID 145 subscriber-user-name jmEventSubscriberUserName 146 subscriber-user-data jmEventSubscriberUserData 147 printer-state jmEventDeviceState 148 printer-state-reasons jmEventDeviceStateReasons 149 printer-is-accepting-jobs jmEventDeviceIsAcceptingJobs 150 3.2. SNMP Mapping for IPP Job Events 152 IPP Job event attribute Job Monitoring MIB object mapping 153 ----------------------- --------------------------------- 154 version-number [no mapping - not useful] 155 status-code [implicit in each generated trap] 156 request-id [request-id in SNMP trap header] 157 attributes-charset [no mapping - strings are UTF-8] 158 attributes-natural-language [no mapping - no text bindings] 159 printer-uri jmEventDeviceURI 160 printer-name jmEventDeviceName 161 job-id jmEventJobIndex 162 [and jmEventJobSetIndex] 163 job-name jmEventJobName 164 trigger-event jmEventTriggerEvent 165 trigger-time [sysUpTime in SNMP trap bindings] 166 trigger-date-time [hrSystemDate in Host Res MIB] 167 subscription-id jmEventSubscriptionID 168 subscriber-user-name jmEventSubscriberUserName 169 subscriber-user-data jmEventSubscriberUserData 170 job-state jmEventJobState 171 job-state-reasons jmEventJobStateReasons 173 [job-completed - extra bindings] 174 job-k-octets jmEventJobKOctets 175 job-k-octets-processed jmEventJobKOctetsProcessed 176 job-impressions jmEventJobImpressions 177 job-impressions-completed jmEventJobImpressionsCompleted 178 job-media-sheets jmEventJobMediaSheets 179 job-media-sheets-completed jmEventJobMediaSheetsCompleted 181 [job-progress - extra bindings] 182 impressions-completed-current-copy jmEventJobImpressionsCompletedCC 183 job-collation-type jmEventJobCollationType 184 sheet-completed-copy-number jmEventJobSheetCompletedCopyNum 185 sheet-completed-document-number jmEventJobSheetCompletedDocNum 186 3.3. Rules for Encoding Notifications 188 Over some transports and/or media, the variable-bindings of these 189 SNMP traps MAY not fit the MTU (maximum transmission unit) size. 190 Conforming IPP Notification generators SHALL perform this procedure 191 to ensure that all variable-bindings of these SNMP traps are always 192 included in the generated SNMP trap packet: 194 1) Truncate all strings specified for variable-bindings 195 to the reduced maximum sizes that are specified in their 196 corresponding OBJECT clauses in their MODULE-COMPLIANCE. 197 1a) If all variable-bindings now fit within the MTU, 198 then exit this procedure and generate the SNMP trap. 199 2) Truncate the next one of the following string objects to 200 the empty string (zero length in the ASN.1 BER encoding), 201 in the order listed: 202 - 'jmEventSubscriberUserName' 203 - 'jmEventSubscriberUserData' 204 - 'jmEventDeviceURI' 205 - 'jmEventDeviceName' 206 - 'jmEventDeviceStateReasons' 207 - 'jmEventJobName' 208 - 'jmEventJobStateReasons' 209 2a) If all variable-bindings now fit within the MTU, 210 then exit this procedure and generate the SNMP trap. 211 2b) If all variable-bindings do NOT fit within the MTU, 212 then repeat step (2) for next string object. 213 3) If all variable-bindings do NOT fit within the MTU, 214 then -> logic error (variable-bindings MUST now fit). 216 3.4. Registration for IPP Notifications 218 IPP Clients may register for IPP Notifications delivered via SNMP by 219 either of the following methods: 221 3.4.1. Registration via IPP 223 IPP Create-Subscription and Job creation (Create-Job, Print-Job, 224 Print-URI) operations MAY be used to create per-Printer or per-Job 225 IPP Subscription objects and MAY specify 227 'notify-recipient' = 'snmpnotify://hostname[.port]' 229 3.4.2. Registration via SNMP 231 SNMP Set-Request operations MAY be used to create appropriate rows in 232 the SNMP Notification MIB defined in [RFC-2573] and MAY specify: 234 1) 'snmpNotifyTag' 235 - tag of this notification - see 'snmpTargetAddrTagList' below 236 - example "jmDeviceBasicV2Event" or "jmJobBasicV2Event" 237 2) 'snmpNotifyType' 238 - notification sent using either SNMP Trap (unacknowledged) 239 or SNMP Inform-Request (acknowledged) 240 3) 'snmpNotifyStorageType' 241 - row persistence of this registration 243 SNMP Set-Request operations MAY be used to create appropriate rows in 244 the SNMP Target MIB defined in [RFC-2573] and MAY specify: 246 1) 'snmpTargetAddrTDomain' and 'snmpTargetAddrTAddress' 247 - target transport protocol and address (equivalent to URI) 248 2) 'snmpTargetAddressTimeout' and 'snmpTargetAddrRetryCount' 249 - retry timeout and limit (for acknowledged notifications 250 delivered using SNMP Inform-Request rather than SNMP Trap) 251 3) 'snmpTargetAddrTagList' 252 - tags of notifications to be sent to this target (client) 253 - example "jmDeviceBasicV2Event" or "jmJobBasicV2Event" 254 4) 'snmpTargetAddrParamsEntry' 255 - notification security and SNMP protocol version 256 5) 'snmpTargetAddrStorageType' 257 - row persistence of this registration 259 3.5. Relationship to other MIBs 261 3.5.1. MIB-II (RFC 1213) 263 All SNMPv1 trap messages include 'time-stamp' which is the value of 264 the 'sysUpTime' object from MIB-II [RFC-1213]. 266 All SNMPv2 trap bindings include the 'sysUpTime' object from MIB-II 267 [RFC-1213]. 269 3.5.2. Host Resources MIB (RFC 1514) 271 The 'jmDeviceBasicV2Event' trap defined in this document permits 272 optional binding of the 'hrDeviceStatus', 'hrDevicePrinterStatus', 273 and 'hrPrinterDetectedErrorState' objects from Host Resources MIB 274 [RFC-1514]. 276 3.5.3. Printer MIB (RFC 1759) 278 The 'jmDeviceBasicV2Event' trap defined in this document permits 279 optional binding of the 'hrDeviceStatus', 'hrDevicePrinterStatus', 280 and 'hrPrinterDetectedErrorState' objects from Host Resources MIB 281 [RFC-1514]. 283 The appropriate value of 'hrDeviceIndex' to use in the Printer MIB 284 [RFC-1759] may be indicated by the instance suffix of the 285 'hrDeviceStatus' variable's OID. 287 4. Managed Object Definitions 289 4.1. Device Basic Event Trap 291 -- Device Basic Event Group (Cond Mandatory) 292 -- 293 -- Implementation of this group is conditionally mandatory; 294 -- mandatory for systems which send this Device event via SNMP. 296 jmDeviceBasicV1Enterprise OBJECT-IDENTITY 297 STATUS current 298 DESCRIPTION 299 "The value of the enterprise-specific OID in an SNMPv1 trap 300 for a Device basic event' sent by this managed system." 301 ::= { jobmonMIBNotifications 1 } 303 jmDeviceBasicV2EventPrefix 304 OBJECT IDENTIFIER ::= { jmDeviceBasicV1Enterprise 0 } 306 jmDeviceBasicV2Event NOTIFICATION-TYPE 307 OBJECTS { 308 jmEventTriggerEvent, 309 jmEventSubscriptionID, 310 jmEventSubscriberUserName, 311 jmEventSubscriberUserData, 312 jmEventDeviceURI, 313 jmEventDeviceName, 314 jmEventJobSetIndex, 315 jmEventJobIndex, 316 jmEventJobName, 317 jmEventDeviceState, 318 jmEventDeviceStateReasons, 319 jmEventDeviceIsAcceptingJobs 320 } 321 STATUS current 322 DESCRIPTION 323 "This SMIv2 trap corresponds to an IPP Printer basic event. 325 This trap is sent when requested by a prior subscription. 326 The event type is specified in 'jmEventTriggerEvent'. 328 Event types reported via 'jmDeviceBasicV2Event' include: 329 - 'printer-restarted' 330 - 'printer-shutdown' 331 - 'printer-state-changed' 332 - 'printer-media-changed' 333 - 'printer-config-changed' 334 - 'printer-queue-changed' 335 - 'printer-no-longer-full' 336 - 'printer-almost-idle' 337 - 'device-restarted' 338 - 'device-shutdown' 339 - 'device-state-changed' 340 - 'device-media-changed' 341 - 'device-config-changed' 342 - 'device-queue-changed' 343 - 'device-no-longer-full' 344 - 'device-almost-idle' 345 - and (optionally) vendor extension event types 347 Additional variable-bindings SHOULD be appended to this trap 348 for all device-level events: 349 - Systems with the Host Resources MIB [RFC-1514] SHOULD add 350 'hrSystemDate' 351 (compare to IPP 'printer-current-time') and 352 'hrDeviceStatus' 353 (compare to IPP 'printer-state') 355 Additional variable-bindings MAY be appended to this trap 356 for all printer-specific events: 357 - Systems with the Host Resources MIB [RFC-1514] MAY add 358 'hrPrinterStatus' 359 (compare to IPP 'printer-state') and 360 'hrPrinterDetectedErrorState' 361 (compare to IPP 'printer-state-reasons') 363 Systems MAY add other variable-bindings from any MIB. 365 See: Section 5.2 'notify-events' of [IPP-NOT]; 366 Section 7 'Notification Content' in [IPP-NOT]." 367 ::= { jmDeviceBasicV2EventPrefix 1 } 369 4.2. Job Basic Event Trap 371 -- Job Basic Event Group (Cond Mandatory) 372 -- 373 -- Implementation of this group is conditionally mandatory; 374 -- mandatory for systems which send this Job event via SNMP. 376 jmJobBasicV1Enterprise OBJECT-IDENTITY 377 STATUS current 378 DESCRIPTION 379 "The value of the enterprise-specific OID in an SNMPv1 trap 380 for a Job basic event sent by this managed system." 381 ::= { jobmonMIBNotifications 2 } 383 jmJobBasicV2EventPrefix 384 OBJECT IDENTIFIER ::= { jmJobBasicV1Enterprise 0 } 386 jmJobBasicV2Event NOTIFICATION-TYPE 387 OBJECTS { 388 jmEventTriggerEvent, 389 jmEventSubscriptionID, 390 jmEventSubscriberUserName, 391 jmEventSubscriberUserData, 392 jmEventDeviceURI, 393 jmEventDeviceName, 394 jmEventJobSetIndex, 395 jmEventJobIndex, 396 jmEventJobName, 397 jmEventJobState, 398 jmEventJobStateReasons 399 } 400 STATUS current 401 DESCRIPTION 402 "This SMIv2 trap corresponds to an IPP Job basic event. 404 This trap is sent when requested by a prior subscription. 405 The event type is specified in 'jmEventTriggerEvent'. 407 Event types reported via 'jmJobBasicV2Event' include: 408 - 'job-created' 409 - 'job-state-changed' 410 - 'job-config-changed' 411 - 'job-purged' 412 - and (optionally) vendor extension event types 414 Systems MAY add other variable-bindings from any MIB. 416 See: Section 5.2 'notify-events' of [IPP-NOT]; 417 Section 7 'Notification Content' in [IPP-NOT]." 418 ::= { jmJobBasicV2EventPrefix 1 } 420 4.3. Job Completed Event Trap 422 -- Job Completed Event Group (Cond Mandatory) 423 -- 424 -- Implementation of this group is conditionally mandatory; 425 -- mandatory for systems which send this Job event via SNMP. 427 jmJobCompletedV1Enterprise OBJECT-IDENTITY 428 STATUS current 429 DESCRIPTION 430 "The value of the enterprise-specific OID in an SNMPv1 trap 431 for a Job completed event sent by this managed system." 432 ::= { jobmonMIBNotifications 3 } 434 jmJobCompletedV2EventPrefix 435 OBJECT IDENTIFIER ::= { jmJobCompletedV1Enterprise 0 } 437 jmJobCompletedV2Event NOTIFICATION-TYPE 438 OBJECTS { 439 jmEventTriggerEvent, 440 jmEventSubscriptionID, 441 jmEventSubscriberUserName, 442 jmEventSubscriberUserData, 443 jmEventDeviceURI, 444 jmEventDeviceName, 445 jmEventJobSetIndex, 446 jmEventJobIndex, 447 jmEventJobName, 448 jmEventJobState, 449 jmEventJobStateReasons, 450 jmEventJobKOctetsProcessed, 451 jmEventJobImpressionsCompleted, 452 jmEventJobMediaSheetsCompleted 453 } 454 STATUS current 455 DESCRIPTION 456 "This SMIv2 trap corresponds to an IPP 'job-completed' event. 458 This trap is sent when requested by a prior subscription. 459 The event type is specified in 'jmEventTriggerEvent'. 461 Event types reported via 'jmJobCompletedV2Event' include: 462 - 'job-completed' 463 - and (optionally) vendor extension event types 465 Additional variable-bindings SHOULD be appended to this trap 466 for all 'job-completed' events: 467 - Systems which support this job information SHOULD add 468 'jmEventJobKOctets' 469 (compare to IPP 'job-k-octets' job size attribute 470 and to Job Mon MIB 'jobKOctetsTransferred' attribute) 471 'jmEventJobImpressions' 472 (compare to IPP 'job-impressions' job size attribute) 473 'jmEventJobMediaSheets' 474 (compare to IPP 'job-media-sheets' job size attribute 475 and to Job Mon MIB 'sheetsRequested' attribute) 477 Systems MAY add other variable-bindings from any MIB. 479 See: Section 5.2 'notify-events' of [IPP-NOT]; 480 Section 7 'Notification Content' in [IPP-NOT]." 481 ::= { jmJobCompletedV2EventPrefix 1 } 483 4.4. Job Progress Event Trap 485 -- Job Progress Event Group (Cond Mandatory) 486 -- 487 -- Implementation of this group is conditionally mandatory; 488 -- mandatory for systems which send this Job event via SNMP. 490 jmJobProgressV1Enterprise OBJECT-IDENTITY 491 STATUS current 492 DESCRIPTION 493 "The value of the enterprise-specific OID in an SNMPv1 trap 494 for a Job progress event sent by this managed system." 495 ::= { jobmonMIBNotifications 4 } 497 jmJobProgressV2EventPrefix 498 OBJECT IDENTIFIER ::= { jmJobProgressV1Enterprise 0 } 500 jmJobProgressV2Event NOTIFICATION-TYPE 501 OBJECTS { 502 jmEventTriggerEvent, 503 jmEventSubscriptionID, 504 jmEventSubscriberUserName, 505 jmEventSubscriberUserData, 506 jmEventDeviceURI, 507 jmEventDeviceName, 508 jmEventJobSetIndex, 509 jmEventJobIndex, 510 jmEventJobName, 511 jmEventJobState, 512 jmEventJobStateReasons, 513 jmEventJobKOctetsProcessed, 514 jmEventJobImpressionsCompleted, 515 jmEventJobMediaSheetsCompleted, 516 jmEventJobImpressionsCompletedCC, 517 jmEventJobCollationType, 518 jmEventJobSheetCompletedCopyNum, 519 jmEventJobSheetCompletedDocNum 520 } 521 STATUS current 522 DESCRIPTION 523 "This SMIv2 trap corresponds to an IPP 'job-progress' event. 525 This trap is sent when requested by a prior subscription. 526 The event type is specified in 'jmEventTriggerEvent'. 528 Event types reported via 'jmJobProgressV2Event' include: 529 - 'job-progress' 530 - and (optionally) vendor extension event types 531 Additional variable-bindings SHOULD be appended to this trap 532 for all 'job-progress' events: 533 - Systems which support this job information SHOULD add 534 'jmEventJobKOctets' 535 (compare to IPP 'job-k-octets' job size attribute 536 and to Job Mon MIB 'jobKOctetsTransferred' attribute) 537 'jmEventJobImpressions' 538 (compare to IPP 'job-impressions' job size attribute) 539 'jmEventJobMediaSheets' 540 (compare to IPP 'job-media-sheets' job size attribute 541 and to Job Mon MIB 'sheetsRequested' attribute) 543 Systems MAY add other variable-bindings from any MIB. 545 See: Section 5.2 'notify-events' of [IPP-NOT]; 546 Section 7 'Notification Content' in [IPP-NOT]." 547 ::= { jmJobProgressV2EventPrefix 1 } 549 4.5. Event Binding Group 551 -- Event Binding Group (Cond Mandatory) 552 -- 553 -- Implementation of this group is conditionally mandatory; 554 -- mandatory for systems which send Device or Job events via SNMP. 555 -- 556 -- Note: All of the objects in this group are defined ONLY for the 557 -- purpose of providing instantaneous bindings for SNMP traps - it's 558 -- NEVER suitable for an SNMP Manager to Get these objects directly. 560 jmEventBinding OBJECT IDENTIFIER ::= { jobmonMIBObjects 5 } 562 jmEventTriggerEvent OBJECT-TYPE 563 SYNTAX JmUTF8StringTC (SIZE (0..63)) -- 255 in [IPP-MOD] 564 MAX-ACCESS read-only 565 STATUS current 566 DESCRIPTION 567 "The trigger event type associated with this event. 569 Standard Printer event types defined in [IPP-NOT] are: 570 - 'printer-restarted' 571 - 'printer-shutdown' 572 - 'printer-state-changed' 573 - 'printer-media-changed' 574 - 'printer-config-changed' 575 - 'printer-queue-changed' 576 - 'printer-no-longer-full' 577 - 'printer-almost-idle' 579 Standard Device event types generalized from [IPP-NOT] are: 581 - 'device-restarted' 582 - 'device-shutdown' 583 - 'device-state-changed' 584 - 'device-media-changed' 585 - 'device-config-changed' 586 - 'device-queue-changed' 587 - 'device-no-longer-full' 588 - 'device-almost-idle' 590 Standard Job event types defined in [IPP-NOT] are: 591 - 'job-created' 592 - 'job-completed' 593 - 'job-state-changed' 594 - 'job-config-changed' 595 - 'job-purged' 596 - 'job-progress' 598 Conformance: The natural language for keywords 599 in trigger event type SHALL always be US English. 601 Conformance: This trigger event type SHALL be valid 602 and reported in ALL Job Monitoring MIB notifications. 604 See: Section 5.2 'notify-events' and 605 Section 7 'Notification Content' in [IPP-NOT]." 606 -- DEFVAL intentionally omitted - reported value SHALL be valid 607 ::= { jmEventBinding 1 } 609 jmEventSubscriptionID OBJECT-TYPE 610 SYNTAX Integer32 (0..2147483647) 611 MAX-ACCESS read-only 612 STATUS current 613 DESCRIPTION 614 "The subscription identifier associated with this event 615 or zero (if none). 617 Conformance: This subscription identifier SHALL be valid 618 and reported, if available on this managed system. 620 See: Section 5.8 'subscription-id' and 621 Section 7 'Notification Content' in [IPP-NOT]." 622 DEFVAL { 0 } -- no subscription ID 623 ::= { jmEventBinding 2 } 625 jmEventSubscriberUserName OBJECT-TYPE 626 SYNTAX JmUTF8StringTC (SIZE (0..63)) -- 1023 in [IPP-MOD] 627 MAX-ACCESS read-only 628 STATUS current 629 DESCRIPTION 630 "The subscriber user name associated with this event 631 or the empty string (if none). 633 Note: The natural language appropriate for text-to-speech 634 of subscriber user name is orthogonal to the localized text 635 context in IPP 'attributes-natural-language'. The subscriber 636 user name MAY include an in-line 'language tag' using Plane 637 14 'language tag' characters approved for ISO 10646/Unicode. 639 Conformance: This subscriber user name SHALL be valid 640 and reported, if available on this managed system. 642 See: 'Language Tagging in Unicode Plain Text', RFC 2482 643 (January 1999); 644 'Plane 14 Characters for Language Tags', Unicode 645 Technical Report #7 (January 1999); 646 Section 4.3.6 'job-originating-user-name' and 647 Section 4.4.2 'uri-authentication-supported' 648 (usage of 'requesting-user-name') in [IPP-MOD]; 649 Section 5.11 'subscriber-user-name' and 650 Section 7 'Notification Content' in [IPP-NOT]." 651 DEFVAL { ''H } -- no subscriber user name 652 ::= { jmEventBinding 3 } 654 jmEventSubscriberUserData OBJECT-TYPE 655 SYNTAX OCTET STRING (SIZE (0..63)) -- 63 in [IPP-NOT] 656 MAX-ACCESS read-only 657 STATUS current 658 DESCRIPTION 659 "The subscriber user data associated with this event 660 or the empty string (if none). 662 Conformance: This subscriber user data SHALL be valid 663 and reported, if available on this managed system. 665 See: Section 5.4 'subscriber-user-data' and 666 Section 7 'Notification Content' in [IPP-NOT]." 667 DEFVAL { ''H } -- no subscriber user data 668 ::= { jmEventBinding 4 } 670 jmEventDeviceURI OBJECT-TYPE 671 SYNTAX OCTET STRING (SIZE (0..255)) -- 1023 in [IPP-MOD] 672 MAX-ACCESS read-only 673 STATUS current 674 DESCRIPTION 675 "The device URI associated with this event 676 or the empty string (if none). 678 Conformance: This device URI SHALL be valid 679 and reported, if available on this managed system. 681 See: Section 4.3.3 'job-printer-uri' in [IPP-MOD]; 682 Section 4.4.1 'printer-uri-supported' in [IPP-MOD]; 683 Section 7 'Notification Content' in [IPP-NOT]." 684 DEFVAL { ''H } -- no device URI 685 ::= { jmEventBinding 5 } 687 jmEventDeviceName OBJECT-TYPE 688 SYNTAX OCTET STRING (SIZE (0..127)) -- 127 in [IPP-MOD] 689 MAX-ACCESS read-only 690 STATUS current 691 DESCRIPTION 692 "The device name associated with this event 693 or the empty string (if none). 695 Conformance: This device name SHALL be valid 696 and reported, if available on this managed system. 698 See: Section 4.4.4 'printer-name' in [IPP-MOD]; 699 Section 7 'Notification Content' in [IPP-NOT]." 700 DEFVAL { ''H } -- no device name 701 ::= { jmEventBinding 6 } 703 jmEventDeviceState OBJECT-TYPE 704 SYNTAX INTEGER { -- enum in [IPP-MOD] 705 unknown(2), -- unknown device state 706 idle(3), 707 processing(4), 708 stopped(5) 709 } 710 MAX-ACCESS read-only 711 STATUS current 712 DESCRIPTION 713 "The device state associated with this event 714 or 'unknown'. 716 Note: This object uses the keywords from the [IPP-MOD] 717 enumerated type 'printer-state' for coherence. 719 Conformance: This device state SHALL be valid 720 and reported, if available on this managed system. 722 See: Section 4.4.11 'printer-state' in [IPP-MOD]; 723 Section 7 'Notification Content' in [IPP-NOT]." 724 DEFVAL { unknown } -- unknown device state 725 ::= { jmEventBinding 7 } 727 jmEventDeviceStateReasons OBJECT-TYPE 728 SYNTAX OCTET STRING (SIZE (0..255)) -- 255*n in [IPP-MOD] 729 MAX-ACCESS read-only 730 STATUS current 731 DESCRIPTION 732 "The device state reasons associated with this event 733 (as a comma-separated list) or the empty string (if none). 735 Conformance: The natural language for keywords 736 in device state reasons SHALL always be US English. 738 Conformance: These device state reasons SHALL be valid 739 and reported, if available on this managed system. 741 See: Section 4.4.12 'printer-state-reasons' in [IPP-MOD]; 742 Section 7 'Notification Content' in [IPP-NOT]." 743 DEFVAL { ''H } -- no device state reasons 744 ::= { jmEventBinding 8 } 746 jmEventDeviceIsAcceptingJobs OBJECT-TYPE 747 SYNTAX TruthValue 748 MAX-ACCESS read-only 749 STATUS current 750 DESCRIPTION 751 "The device substate associated with this event 752 or 'true' (if unknown). 754 Conformance: This device substate SHALL be valid 755 and reported, if available on this managed system. 757 See: Section 4.4.23 'printer-is-accepting-jobs' 758 in [IPP-MOD]; 759 Section 7 'Notification Content' in [IPP-NOT]." 760 DEFVAL { true } -- device is accepting jobs 761 ::= { jmEventBinding 9 } 763 jmEventJobSetIndex OBJECT-TYPE 764 SYNTAX Integer32 (0..32767) 765 MAX-ACCESS read-only 766 STATUS current 767 DESCRIPTION 768 "The job set index associated with this event 769 or zero (if none). 771 Conformance: This job set index SHALL be valid 772 and reported, if available on this managed system. 774 See: 'jmGeneralJobSetIndex' object in [RFC-2707]; 775 Section 4.3.2 'job-id' in [IPP-MOD]; 776 Section 7 'Notification Content' in [IPP-NOT]." 777 DEFVAL { 0 } -- no job set index 778 ::= { jmEventBinding 10 } 780 jmEventJobIndex OBJECT-TYPE 781 SYNTAX Integer32 (0..2147483647) 782 MAX-ACCESS read-only 783 STATUS current 784 DESCRIPTION 785 "The job index associated with this event 786 or zero (if none). 788 Conformance: This job index SHALL be valid 789 and reported, if available on this managed system. 791 See: 'jmJobIndex' object in [RFC-2707]; 792 Section 4.3.2 'job-id' in [IPP-MOD]; 793 Section 7 'Notification Content' in [IPP-NOT]." 794 DEFVAL { 0 } -- no job index 795 ::= { jmEventBinding 11 } 797 jmEventJobName OBJECT-TYPE 798 SYNTAX OCTET STRING (SIZE (0..255)) -- 255 in [IPP-MOD] 799 MAX-ACCESS read-only 800 STATUS current 801 DESCRIPTION 802 "The job name associated with this event 803 or the empty string (if none). 805 Conformance: This job name SHALL be valid 806 and reported, if available on this managed system. 808 See: 'jobName' attribute in [RFC-2707]; 809 Section 4.3.5 'job-name' in [IPP-MOD]; 810 Section 7 'Notification Content' in [IPP-NOT]." 811 DEFVAL { ''H } -- no job name 812 ::= { jmEventBinding 12 } 814 jmEventJobState OBJECT-TYPE 815 SYNTAX INTEGER { -- enum in [IPP-MOD] 816 unknown(2), -- unknown job state 817 pending(3), 818 pendingHeld(4), 819 processing(5), 820 processingStopped(6), 821 canceled(7), 822 aborted(8), 823 completed(9) 824 } 825 MAX-ACCESS read-only 826 STATUS current 827 DESCRIPTION 828 "The job state associated with this event 829 or 'unknown'. 831 Note: This object uses the keywords from the [IPP-MOD] 832 enumerated type 'job-state' for coherence. 834 Conformance: This job state SHALL be valid 835 and reported, if available on this managed system. 837 See: 'jmJobState' object in [RFC-2707]; 838 Section 4.3.7 'job-state' in [IPP-MOD]; 839 Section 7 'Notification Content' in [IPP-NOT]." 840 DEFVAL { unknown } -- unknown job state 841 ::= { jmEventBinding 13 } 843 jmEventJobStateReasons OBJECT-TYPE 844 SYNTAX OCTET STRING (SIZE (0..255)) -- 255*n in [IPP-MOD] 845 MAX-ACCESS read-only 846 STATUS current 847 DESCRIPTION 848 "The job state reasons associated with this event 849 (as a comma-separated list) or the empty string (if none). 851 Conformance: The natural language for keywords 852 in job state reasons SHALL always be US English. 854 Conformance: These job state reasons SHALL be valid 855 and reported, if available on this managed system. 857 See: 'jmJobStateReasons1' object in [RFC-2707]; 858 'jobStateReasons2', 'jobStateReasons3', and 859 'jobStateReasons4' attributes in [RFC-2707]; 860 Section 4.3.8 'job-state-reasons' in [IPP-MOD]; 861 Section 7 'Notification Content' in [IPP-NOT]." 862 DEFVAL { ''H } -- no job state reasons 863 ::= { jmEventBinding 14 } 865 jmEventJobKOctets OBJECT-TYPE 866 SYNTAX Integer32 (-2..2147483647) 867 MAX-ACCESS read-only 868 STATUS current 869 DESCRIPTION 870 "The job size in K octets associated with this event 871 or zero (if none) or '-2' (if unknown). 873 Conformance: This job size SHALL be valid 874 and reported, if available on this managed system. 876 See: 'jobKOctetsTransferred' attribute in [RFC-2707]; 877 Section 4.3.17.1 'job-k-octets' in [IPP-MOD]; 878 Section 7 'Notification Content' in [IPP-NOT]." 879 DEFVAL { -2 } -- unknown job size 880 ::= { jmEventBinding 15 } 882 jmEventJobKOctetsProcessed OBJECT-TYPE 883 SYNTAX Integer32 (-2..2147483647) 884 MAX-ACCESS read-only 885 STATUS current 886 DESCRIPTION 887 "The job progress in K octets associated with this event 888 or zero (if none) or '-2' (if unknown). 890 Conformance: This job progress SHALL be valid 891 and reported, if available on this managed system. 893 See: 'jmJobKOctetsProcessed' object in [RFC-2707]; 894 Section 4.3.18.1 'job-k-octets-processed' 895 in [IPP-MOD]; 896 Section 7 'Notification Content' in [IPP-NOT]." 897 DEFVAL { -2 } -- unknown job progress 898 ::= { jmEventBinding 16 } 900 jmEventJobImpressions OBJECT-TYPE 901 SYNTAX Integer32 (-2..2147483647) 902 MAX-ACCESS read-only 903 STATUS current 904 DESCRIPTION 905 "The job size in impressions associated with this event 906 or zero (if none) or '-2' (if unknown). 908 Conformance: This job size SHALL be valid 909 and reported, if available on this managed system. 911 See: Section 4.3.17.2 'job-impressions' in [IPP-MOD]; 912 Section 7 'Notification Content' in [IPP-NOT]." 913 DEFVAL { -2 } -- unknown job size 914 ::= { jmEventBinding 17 } 916 jmEventJobImpressionsCompleted OBJECT-TYPE 917 SYNTAX Integer32 (-2..2147483647) 918 MAX-ACCESS read-only 919 STATUS current 920 DESCRIPTION 921 "The job progress in impressions associated with this event 922 or zero (if none) or '-2' (if unknown). 924 Conformance: This job progress SHALL be valid 925 and reported, if available on this managed system. 927 See: 'jmJobImpressionsCompleted' object in [RFC-2707]; 928 Section 4.3.18.2 'job-impressions-completed' 929 in [IPP-MOD]; 930 Section 7 'Notification Content' in [IPP-NOT]." 931 DEFVAL { -2 } -- unknown job progress 932 ::= { jmEventBinding 18 } 934 jmEventJobMediaSheets OBJECT-TYPE 935 SYNTAX Integer32 (-2..2147483647) 936 MAX-ACCESS read-only 937 STATUS current 938 DESCRIPTION 939 "The job size in media sheets associated with this event 940 or zero (if none) or '-2' (if unknown). 942 Conformance: This job size SHALL be valid 943 and reported, if available on this managed system. 945 See: 'sheetsRequested' attribute in [RFC-2707]; 946 Section 4.3.17.3 'job-media-sheets' in [IPP-MOD]; 947 Section 7 'Notification Content' in [IPP-NOT]." 948 DEFVAL { -2 } -- unknown job size 949 ::= { jmEventBinding 19 } 951 jmEventJobMediaSheetsCompleted OBJECT-TYPE 952 SYNTAX Integer32 (-2..2147483647) 953 MAX-ACCESS read-only 954 STATUS current 955 DESCRIPTION 956 "The job progress in media sheets associated with this event 957 or zero (if none) or '-2' (if unknown). 959 Conformance: This job progress SHALL be valid 960 and reported, if available on this managed system. 962 See: 'sheetsCompleted' attribute in [RFC-2707]; 963 Section 4.3.18.3 'job-media-sheets-completed' 964 in [IPP-MOD]; 965 Section 7 'Notification Content' in [IPP-NOT]." 966 DEFVAL { -2 } -- unknown job progress 967 ::= { jmEventBinding 20 } 969 jmEventJobImpressionsCompletedCC OBJECT-TYPE 970 SYNTAX Integer32 (-2..2147483647) 971 MAX-ACCESS read-only 972 STATUS current 973 DESCRIPTION 974 "The job progress in impressions completed 975 on the current copy associated with this event 976 or zero (if none) or '-2' (if unknown). 978 Conformance: This job progress SHALL be valid 979 and reported, if available on this managed system. 981 See: 'jmJobImpressionsCompleted' object in [RFC-2707]; 982 'impressions-completed-current-copy' in [IPP-PROG]; 983 Section 7 'Notification Content' in [IPP-NOT]." 984 DEFVAL { unknown } -- unknown job progress 985 ::= { jmEventBinding 21 } 987 jmEventJobCollationType OBJECT-TYPE 988 SYNTAX JmJobCollationTypeTC 989 MAX-ACCESS read-only 990 STATUS current 991 DESCRIPTION 992 "The job collation type associated with this event 993 or 'unknown' (if unknown). 995 Conformance: This job collation type be valid 996 and reported, if available on this managed system. 998 See: 'jobCollationType' attribute in [RFC-2707]; 999 'job-collation-type' in [IPP-PROG]; 1000 Section 7 'Notification Content' in [IPP-NOT]." 1001 DEFVAL { unknown } -- unknown job collation type 1002 ::= { jmEventBinding 22 } 1004 jmEventJobSheetCompletedCopyNum OBJECT-TYPE 1005 SYNTAX Integer32 (-2..2147483647) 1006 MAX-ACCESS read-only 1007 STATUS current 1008 DESCRIPTION 1009 "The job progress number of the copy currently being 1010 stacked for the document associated with this event 1011 or zero (if none) or '-2' (if unknown). 1013 Conformance: This job progress SHALL be valid 1014 and reported, if available on this managed system. 1016 See: 'sheetCompletedCopyNumber' attribute 1017 in [RFC-2707]; 1018 'sheet-completed-copy-number' in [IPP-PROG]; 1019 Section 7 'Notification Content' in [IPP-NOT]." 1020 DEFVAL { -2 } -- unknown copy number 1021 ::= { jmEventBinding 23 } 1023 jmEventJobSheetCompletedDocNum OBJECT-TYPE 1024 SYNTAX Integer32 (-2..2147483647) 1025 MAX-ACCESS read-only 1026 STATUS current 1027 DESCRIPTION 1028 "The job progress number of the document currently being 1029 stacked associated with this event 1030 or zero (if none) or '-2' (if unknown). 1032 Conformance: This job progress SHALL be valid 1033 and reported, if available on this managed system. 1035 See: 'sheetCompletedDocumentNumber' attribute 1036 in [RFC-2707]; 1037 'sheet-completed-document-number' in [IPP-PROG]; 1038 Section 7 'Notification Content' in [IPP-NOT]." 1039 DEFVAL { -2 } -- unknown document number 1040 ::= { jmEventBinding 24 } 1042 5. IANA Considerations 1044 None. 1046 6. Internationalization Considerations 1048 The 'jmEventTriggerEvent', 'jmEventDeviceState', and 1049 'jmEventDeviceStateReasons' text objects defined in this document are 1050 of type 'JmUTF8StringTC' (UTF-8 stream-encoded ISO 10646/Unicode 1051 text) defined in the Job Monitoring MIB [RFC-2707]. The natural 1052 language of these objects is US English. 1054 The 'jmEventSubscriberUserName' text object defined in this document 1055 is of type 'JmUTF8StringTC' (UTF-8 stream-encoded ISO 10646/Unicode 1056 text) defined in the Job Monitoring MIB [RFC-2707]. The natural 1057 language of this object is inherently ambiguous (as it usually 1058 contains some transform of a personal name). 1060 7. Security Considerations 1062 This IPP Notifications over SNMP mapping defines only 'read-only' 1063 objects. It is suitable for use with any version of SNMP, as no 1064 update security is required (because no configuration updates are 1065 supported). 1067 No sensitive information is available via IPP Notifications over 1068 SNMP. 1070 8. References 1072 [IPP-MOD] R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell. 1073 IPP/1.1 Model and Semantics, 1074 (work-in-progress), March 2000. 1076 [IPP-NOT] S. Isaacson, J. Martin, R. deBry, T. Hastings, M. Shepherd, 1077 R. Bergman. IPP Event Notification Specification, 1078 (work-in-progress), March 2000. 1080 [IPP-PROG] T. Hastings, R. Bergman, H. Lewis. Proposed Job Progress 1081 Attributes for IPP, (work-in-progress), 1082 February 2000. 1084 [RFC-1213] K. McCloghrie, M. Rose. MIB-II, RFC 1213, March 1991. 1086 [RFC-1514] P. Grillo, S. Waldbusser. Host Resources MIB, RFC 1514, 1087 September 1993. 1089 [RFC-1759] R. Smith, F. Wright, T. Hastings, S. Zilles, 1090 J. Gyllenskog. Printer MIB, RFC 1759, March 1995. 1092 [RFC-2573] D. Levi, P. Meyer, B. Stewart. SNMP Applications, RFC 1093 2573, April 1999. 1095 [RFC-2576] R. Frye, D. Levi, S. Routhier, B. Wijnen. Coexistence 1096 between Version 1, Version 2, and Version 3 of the Internet-standard 1097 Network Management Framework, RFC 2576, March 2000. 1099 [RFC-2707] R. Bergman, T. Hastings, S. Isaacson, H. Lewis. Job 1100 Monitoring MIB v1.0, RFC 2707, November 1999 1102 9. Change Log 1104 Changes in reverse chronological order (most recent first). 1106 - 19 March 2000 1107 1) Renamed Printer Event notification group to Device Basic Event 1108 and 'jmPrinterEventV2Event' notification to 1109 'jmDeviceBasicV2Event', to better align with IPP and to support 1110 non-printing jobs. 1111 2) Revised 'jmDeviceBasicV2Event' notification to remove 1112 'hrDeviceStatus', 'hrPrinterStatus', 1113 'hrPrinterDetectedErrorState' from mandatory trap bindings 1114 because they were redundant, per request of Ron Bergman. 1115 3) Renamed Job Event notification group to Job Basic Event and 1116 'jmJobEventV2Event' notification to 'jmJobBasicV2Event', to 1117 better align with IPP and to support variant job events. 1118 4) Defined new Job Completed Event notification group and defined 1119 new Job Progress Event notification group, to better align with 1120 IPP and to support variant job events. 1121 5) Renamed Event object group to Event Binding, 1122 'jmEventPrinterState' to 'jmEventDeviceState', 1123 'jmEventPrinterStateReasons' to 'jmEventDeviceStateReasons', 1124 'jmEventPrinterIsAcceptingJobs' to 1125 'jmEventDeviceIsAcceptingJobs', to support non-printing jobs. 1126 6) Revised Event Binding object group, adding explicit objects 1127 'jmEventDeviceURI', 'jmEventDeviceName', 'jmEventJobSetIndex', 1128 'jmEventJobIndex', 'jmEventJobName', 'jmEventJobState', 1129 'jmEventJobStateReasons', 'jmEventJobKOctets', 1130 'jmEventJobKOctetsProcessed', 'jmEventJobImpressions', 1131 'jmEventJobImpressionsCompleted', 'jmEventJobMediaSheets', 1132 'jmEventJobMediaSheetsCompleted', 1133 'jmEventJobImpressionsCompletedCC', 'jmEventJobCollationType', 1134 'jmEventJobSheetCompletedCopyNum', 1135 'jmEventJobSheetCompletedDocNum', per request of Ron Bergman. 1136 7) Revised SYNTAX of 'jmEventTriggerEvent' object from from 1137 'JmUTF8StringTC' (string) to IPP-aligned enumeration, per request 1138 of Ron Bergman. 1139 8) Removed all references to Printer MIB v2, as they were of limited 1140 value, per request of Ron Bergman. 1141 9) Revised 'SNMP Mapping for IPP Printer Events' section for renamed 1142 event binding objects, per request of Ron Bergman. 1143 10) Revised 'Rules for Encoding Notifications' section to truncate 1144 additional string bindings, per request of Ron Bergman. 1145 11) Revised 'Registration via IPP' section, to change scheme name 1146 from 'ipp-snmp:' to 'snmpnotify:', per request of Ron Bergman. 1148 - 1 December 1999 1149 1) Deleted 'JmTriggerEventTC' textual convention (see below). 1151 2) Revised SYNTAX of 'jmEventTriggerEvent' object from 1152 'JmTriggerEventTC' (enumeration) to 'JmUTF8StringTC' (string), to 1153 support use of IPP standard keywords. 1154 3) Added 'jmEventPrinterState', 'jmEventPrinterStateReasons', and 1155 'jmEventPrinterIsAcceptingJobs' objects for consistency w/ 1156 [IPP-NOT] and to reduce ambiguity about printer states inherent 1157 in RFC 1759. 1158 4) Revised DESCRIPTION of 'jmPrinterEventV2Event' notification to 1159 add SHOULD (recommendation) for 'jmEventPrinterState', 1160 'jmEventPrinterStateReasons', and 'jmEventPrinterIsAcceptingJobs' 1161 objects. 1162 5) Revised 'SNMP Mapping for IPP Printer Events' section to add 1163 direct mapping of IPP notification attributes to 1164 'jmEventPrinterState', 'jmEventPrinterStateReasons', and 1165 'jmEventPrinterIsAcceptingJobs' objects. 1166 6) Revised 'Rules for Encoding Notifications' section to add 1167 'jmEventPrinterState' and 'jmEventPrinterStateReasons'. 1168 7) Revised 'IANA Considerations' section to specify there are none - 1169 no enumerated or keyword textual conventions are now defined in 1170 this document. 1171 8) Revised 'Internationalization Considerations' section to specify 1172 that US English keywords are used in 'jmEventTriggerEvent', 1173 'jmEventPrinterState', and 'jmEventPrinterStateReasons' objects 1174 and thus no explicit natural language tagging is required. 1176 - 10 October 1999 1177 1) Initial version. 1179 10. Intellectual Property Notice 1181 The IETF takes no position regarding the validity or scope of any 1182 intellectual property or other rights that might be claimed to 1183 pertain to the implementation or use of the technology described in 1184 this document or the extent to which any license under such rights 1185 might or might not be available; neither does it represent that it 1186 has made any effort to identify any such rights. Information on the 1187 IETF's procedures with respect to rights in standards-track and 1188 standards-related documentation can be found in BCP-11. Copies of 1189 claims of rights made available for publication and any assurances of 1190 licenses to be made available, or the result of an attempt made to 1191 obtain a general license or permission for the use of such 1192 proprietary rights by implementers or users of this specification can 1193 be obtained from the IETF Secretariat. 1195 The IETF invites any interested party to bring to its attention any 1196 copyrights, patents or patent applications, or other proprietary 1197 rights which may cover technology that may be required to practice 1198 this standard. Please address the information to the IETF Executive 1199 Director. 1201 11. Authors' Addresses 1203 Tom Hastings 1204 Xerox Corporation 1205 701 S Aviation Blvd, MS 834-03E 1206 El Segundo, CA 90245 1208 Phone: +1 310-333-6413 1209 Email: hastings@cp10.es.xerox.com 1211 Ira McDonald 1212 High North Inc 1213 221 Ridge Ave 1214 Grand Marais, MI 49839 1216 Phone: +1 906-494-2434 or +1 906-494-2697 1217 Email: imcdonald@sharplabs.com 1219 12. Full Copyright Statement 1221 Copyright (C) The Internet Society (2000). All Rights Reserved. 1223 This document and translations of it may be copied and furnished to 1224 others, and derivative works that comment on or otherwise explain it 1225 or assist in its implementation may be prepared, copied, published 1226 and distributed, in whole or in part, without restriction of any 1227 kind, provided that the above copyright notice and this paragraph are 1228 included on all such copies and derivative works. However, this 1229 document itself may not be modified in any way, such as by removing 1230 the copyright notice or references to the Internet Society or other 1231 Internet organizations, except as needed for the purpose of 1232 developing Internet standards in which case the procedures for 1233 copyrights defined in the Internet Standards process must be 1234 followed, or as required to translate it into languages other than 1235 English. 1237 The limited permissions granted above are perpetual and will not be 1238 revoked by the Internet Society or its successors or assigns. 1240 This document and the information contained herein is provided on an 1241 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1242 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1243 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1244 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1245 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.