idnits 2.17.1 draft-ietf-ipp-not-over-snmp-00.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. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == 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 ([PWG-JOB]), 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 168: '... SNMP traps MAY not fit the MTU (max...' RFC 2119 keyword, line 169: '...ation generators SHALL perform this pr...' RFC 2119 keyword, line 191: '...rror (variable-bindings MUST now fit)....' RFC 2119 keyword, line 201: '...-URI) operations MAY be used to create...' RFC 2119 keyword, line 202: '...P Subscription objects and MAY specify...' (31 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 163 has weird spacing: '...nt-copy impre...' == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHOULD not' in this paragraph: See: Section 5.2 'notify-events' and Section 7 'Notification Content' in [IPP-NOT]." SYNTAX INTEGER { other(1), unknown(2), none(3), -- SHOULD not be used printerRestarted(11), -- 'printer-restarted' printerShutdown(12), -- 'printer-shutdown' printerStateChanged(13), -- 'printer-state-changed' printerMediaChanged(14), -- 'printer-media-changed' printerConfigChanged(15), -- 'printer-config-changed' printerQueueChanged(16), -- 'printer-queue-changed' printerNoLongerFull(17), -- 'printer-no-longer-full' printerAlmostIdle(18), -- 'printer-almost-idle' jobCreated(21), -- 'job-created' jobCompleted(22), -- 'job-completed' jobStateChanged(23), -- 'job-state-changed' jobConfigChanged(24), -- 'job-config-changed' jobPurged(25), -- 'job-purged' jobProgress(26) -- 'job-progress' } -- 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 (10 October 1999) is 8965 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 section? 'PWG-JOB' on line 515 looks like a reference -- Missing reference section? 'IPP-PRO' on line 80 looks like a reference -- Missing reference section? 'RFC-2119' on line 92 looks like a reference -- Missing reference section? 'RFC-1908' on line 96 looks like a reference -- Missing reference section? 'V3-COEX' on line 99 looks like a reference -- Missing reference section? 'PRT-MIB2' on line 371 looks like a reference -- Missing reference section? 'RFC-2573' on line 221 looks like a reference -- Missing reference section? 'RFC-1514' on line 243 looks like a reference -- Missing reference section? 'RFC-1759' on line 255 looks like a reference -- Missing reference section? 'IPP-NOT' on line 500 looks like a reference -- Missing reference section? 'IPP-MOD' on line 482 looks like a reference Summary: 7 errors (**), 0 flaws (~~), 4 warnings (==), 13 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 10 April 2000 Ira McDonald 4 High North 5 10 October 1999 7 Internet Printing Protocol/1.1: Notifications over SNMP 8 10 Copyright (C) The Internet Society (1999). All Rights Reserved. 12 Status of this Memo 14 This document is an Internet-Draft and is in full conformance with 15 all provisions of Section 10 of RFC2026. Internet-Drafts are working 16 documents of the Internet Engineering Task Force (IETF), its areas, 17 and its working groups. Note that other groups may also distribute 18 working documents as Internet-Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference 23 material or to cite them other than as "work in progress." 25 To view the list of Internet-Draft Shadow Directories, see 26 http://www.ietf.org/shadow.html. 28 Abstract 30 This document is a submission to the Internet Printing Protocol 31 Working Group of the Internet Engineering Task Force (IETF). 32 Comments should be submitted to the ipp@pwg.org mailing list. 34 This document proposes a mapping of IPP notifications over SNMP, 35 using new Printer Event and Job Event traps (to be added to the PWG 36 Job Monitoring MIB [PWG-JOB]). This mapping may be used to deliver 37 printer notifications for any printer (not just IPP-capable ones) and 38 also job notifications for any job (not just ones submitted via IPP). 40 This document proposes: (2) SNMP traps; (1) SNMP textual convention; 41 and (4) SNMP leaf objects (for use in trap bindings). 43 Table of Contents 45 1. Introduction ............................................... 3 46 1.1. Terminology for Conformance ............................ 3 47 2. SNMP Network Management Framework .......................... 3 48 3. Managed Object Mapping ..................................... 3 49 3.1. SNMP Mapping for IPP Printer Events .................... 3 50 3.2. SNMP Mapping for IPP Job Events ........................ 4 51 3.3. Rules for Encoding Notifications ....................... 4 52 3.4. Registration for IPP Notifications ..................... 5 53 3.4.1. Registration via IPP ............................... 5 54 3.4.2. Registration via SNMP .............................. 5 55 3.5. Relationship to other MIBs ............................. 6 56 3.5.1. IETF Host Resources MIB (RFC 1514) ................. 6 57 3.5.2. IETF Printer MIB (RFC 1759) ........................ 6 58 3.5.3. Printer MIB v2 (work-in-progress) .................. 6 59 4. Managed Object Definitions ................................. 8 60 4.1. Printer Event Trap ..................................... 8 61 4.1.1. jmPrinterEventV2Event (notification) ............... 8 62 4.2. Job Event Trap ......................................... 9 63 4.2.1. jmJobEventV2Event (notification) ................... 9 64 4.3. Trigger Events ......................................... 10 65 4.3.1. JmTriggerEventTC (textual convention) .............. 10 66 4.4. Event Objects .......................................... 11 67 4.4.1. jmEventTriggerEvent (object) ....................... 11 68 4.4.2. jmEventSubscriptionID (object) ..................... 11 69 4.4.3. jmEventSubscriberUserName (object) ................. 12 70 4.4.4. jmEventSubscriberUserData (object) ................. 12 71 5. IANA Considerations ........................................ 13 72 6. Internationalization Considerations ........................ 13 73 7. Security Considerations .................................... 13 74 8. References ................................................. 14 75 9. Intellectual Property Notice ............................... 14 76 10. Authors' Addresses ........................................ 14 77 11. Full Copyright Statement .................................. 15 78 1. Introduction 80 The IPP protocol [IPP-PRO] supports passive monitoring of IPP Printer 81 and Job objects, via client polling of IPP object attributes using 82 the 'Get-Printer-Attributes' and 'Get-Job-Attributes' operations. 84 This IPP Notifications over SNMP mapping supports dynamic monitoring 85 of IPP Printer and Job objects, via server generation of SNMP traps. 87 1.1. Terminology for Conformance 89 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 90 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 91 document are to be interpreted per [RFC-2119]. 93 2. SNMP Network Management Framework 95 See: Section 1 'Introduction' and section 2 'Management Information' 96 of IETF Coexistence between SNMPv1 and SNMPv2 [RFC-1908]. 98 See: Section 1.1 'SNMPv1', section 1.2 'SNMPv2', and section 1.3 99 'SNMPv3' of IETF Coexistence between SNMP Versions [V3-COEX]. 101 3. Managed Object Mapping 103 3.1. SNMP Mapping for IPP Printer Events 105 IPP Printer event attribute Printer/Job MIB object mapping 106 --------------------------- ------------------------------ 107 version-number [no mapping - not useful] 108 status-code [implicit in generated trap] 109 request-id [request-id in SNMP trap header] 110 attributes-charset [no mapping - strings are UTF-8] 111 attributes-natural-language [no mapping - no text bindings] 112 printer-uri [prtChannelInformation in PMv2] 113 printer-name [prtGeneralPrinterName in PMv2] 114 job-id jmJobIndex in OID instance suffix 115 job-name jobName 116 trigger-event jmEventTriggerEvent 117 trigger-time [time-stamp in SNMP trap header] 118 trigger-date-time hrSystemDate in Host Res MIB 119 subscription-id jmEventSubscriptionID 120 subscriber-user-name jmEventSubscriberUserName 121 subscriber-user-data jmEventSubscriberUserData 122 printer-state hrDeviceStatus in Host Res MIB 123 hrPrinterStatus in Host Res MIB 124 printer-state-reasons hrPrinterDetectedErrorState 125 in Host Res MIB 126 printer-is-accepting-jobs [no mapping] 128 3.2. SNMP Mapping for IPP Job Events 130 IPP Job event attribute Printer/Job MIB object mapping 131 ----------------------- ------------------------------ 132 version-number [no mapping - not useful] 133 status-code [implicit in generated trap] 134 request-id [request-id in SNMP trap header] 135 attributes-charset [no mapping - strings are UTF-8] 136 attributes-natural-language [no mapping - no text bindings] 137 printer-uri [prtChannelInformation in PMv2] 138 printer-name [prtGeneralPrinterName in PMv2] 139 job-id jmJobIndex in OID instance suffix 140 job-name jobName 141 trigger-event jmEventTriggerEvent 142 trigger-time [time-stamp in SNMP trap header] 143 trigger-date-time hrSystemDate in Host Res MIB 144 subscription-id jmEventSubscriptionID 145 subscriber-user-name jmEventSubscriberUserName 146 subscriber-user-data jmEventSubscriberUserData 147 job-state jmJobState 148 job-state-reasons jmJobStateReasons1 149 jmJobStateReasons2 150 jmJobStateReasons3 151 jmJobStateReasons4 153 [job-completed|state-changed|purged - extra bindings] 154 job-k-octets-processed jmJobKOctetsProcessed 155 job-impressions-completed jmJobImpressionsCompleted 156 job-media-sheets-completed sheetsCompleted 158 [job-progress - extra bindings] 159 job-collation-type jobCollationType 160 sheet-completed-copy-number sheetCompletedCopyNumber 161 sheet-completed-document-number sheetCompletedDocumentNumber 162 impressions-interpreted impressionsInterpreted 163 impressions-completed-current-copy impressionsCompletedCurrentCopy 165 3.3. Rules for Encoding Notifications 167 Over some transports and/or media, the variable-bindings of these 168 SNMP traps MAY not fit the MTU (maximum transmission unit) size. 169 Conforming IPP Notification generators SHALL perform this procedure 170 to ensure that all variable-bindings of these SNMP traps are always 171 included in the generated SNMP trap packet: 173 1) Truncate all strings specified for variable-bindings 174 to the reduced maximum sizes that are specified in their 175 corresponding OBJECT clauses in their MODULE-COMPLIANCE. 176 1a) If all variable-bindings now fit within the MTU, 177 then exit this procedure and generate the SNMP trap. 178 2) Truncate the next one of the following string objects to 179 the empty string (zero length in the ASN.1 BER encoding), 180 in the order listed: 181 - 'prtChannelInformation' (from Printer MIB v2 [PRT-MIB2]) 182 - 'prtGeneralPrinterName' (from Printer MIB v2 [PRT-MIB2]) 183 - 'jmEventSubscriberUserName' 184 - 'jmEventSubscriberUserData' 185 - 'jmAttributeValue...jobName.1' 186 2a) If all variable-bindings now fit within the MTU, 187 then exit this procedure and generate the SNMP trap. 188 2b) If all variable-bindings do NOT fit within the MTU, 189 then repeat step (2) for next string object. 190 3) If all variable-bindings do NOT fit within the MTU, 191 then -> logic error (variable-bindings MUST now fit). 193 3.4. Registration for IPP Notifications 195 IPP Clients may register for IPP Notifications delivered via SNMP by 196 either of the following methods: 198 3.4.1. Registration via IPP 200 IPP Create-Subscription and Job creation (Create-Job, Print-Job, 201 Print-URI) operations MAY be used to create per-Printer or per-Job 202 IPP Subscription objects and MAY specify 204 'notify-recipient' = 'ipp-snmp://hostname[.port]' 206 3.4.2. Registration via SNMP 208 SNMP Set-Request operations MAY be used to create appropriate rows in 209 the SNMP Notification MIB defined in [RFC-2573] and MAY specify: 211 1) 'snmpNotifyTag' 212 - tag of this notification - see 'snmpTargetAddrTagList' below 213 - example "jmPrinterEventV2Event" or "jmJobEventV2Event" 214 2) 'snmpNotifyType' 215 - notification sent using either SNMP Trap (unacknowledged) 216 or SNMP Inform-Request (acknowledged) 217 3) 'snmpNotifyStorageType' 218 - row persistence of this registration 220 SNMP Set-Request operations MAY be used to create appropriate rows in 221 the SNMP Target MIB defined in [RFC-2573] and MAY specify: 223 1) 'snmpTargetAddrTDomain' and 'snmpTargetAddrTAddress' 224 - target transport protocol and address (equivalent to URI) 225 2) 'snmpTargetAddressTimeout' and 'snmpTargetAddrRetryCount' 226 - retry timeout and limit (for acknowledged notifications 227 delivered using SNMP Inform-Request rather than SNMP Trap) 228 3) 'snmpTargetAddrTagList' 229 - tags of notifications to be sent to this target (client) 230 - example value "jmPrinterEventV2Event jmJobEventV2Event" 231 4) 'snmpTargetAddrParamsEntry' 232 - notification security and SNMP protocol version 233 5) 'snmpTargetAddrStorageType' 234 - row persistence of this registration 236 3.5. Relationship to other MIBs 238 3.5.1. IETF Host Resources MIB (RFC 1514) 240 The 'jmPrinterEventV2Event' trap defined in this document includes a 241 'hrDeviceStatus' object for a device of type 'hrDevicePrinter'. The 242 'jmPrinterEventV2Event' trap defined in this document includes four 243 objects from the IETF HR MIB [RFC-1514] in the variable-bindings: 245 - 'hrDeviceStatus' --> IPP 'printer-state' 246 - 'hrPrinterStatus' --> IPP 'printer-state' 247 - 'hrPrinterDetectedErrorState' --> IPP 'printer-state-reasons' 248 - 'hrSystemDate' --> IPP 'printer-current-time' 250 3.5.2. IETF Printer MIB (RFC 1759) 252 The 'jmPrinterEventV2Event' trap defined in this document includes a 253 'hrDeviceStatus' object for a device of type 'hrDevicePrinter'. The 254 appropriate 'hrDeviceIndex' to use in the companion IETF Printer MIB 255 [RFC-1759] is indicated by the instance suffix of the variable's OID. 257 3.5.3. Printer MIB v2 (work-in-progress) 259 The 'jmPrinterEventV2Event' trap defined in this document includes 260 two objects from the (work-in-progress) Printer MIB v2 [PRT-MIB2] in 261 the variable-bindings: 263 - 'prtGeneralPrinterName' --> IPP 'printer-name' 264 - 'prtChannelInformation' --> IPP 'printer-uri' 266 4. Managed Object Definitions 268 4.1. Printer Event Trap 270 -- Printer Event Group (Cond Mandatory) 271 -- 272 -- Implementation of this group is conditionally mandatory; 273 -- mandatory for systems which send this Printer event via SNMP. 275 jmPrinterEventV1Enterprise OBJECT-IDENTITY 276 STATUS current 277 DESCRIPTION 278 "The value of the enterprise-specific OID in an SNMPv1 trap 279 for a 'basic-printer-event' sent by this managed system." 280 ::= { jobmonMIBNotifications 1 } 282 jmPrinterEventV2EventPrefix 283 OBJECT IDENTIFIER ::= { jmPrinterEventV1Enterprise 0 } 285 jmPrinterEventV2Event NOTIFICATION-TYPE 286 OBJECTS { 287 jmEventTriggerEvent, 288 jmEventSubscriptionID, 289 jmEventSubscriberUserName, 290 jmEventSubscriberUserData, 291 hrDeviceStatus, 292 hrPrinterStatus, 293 hrPrinterDetectedErrorState 294 } 295 STATUS current 296 DESCRIPTION 297 "This SMIv2 trap corresponds to an IPP 'basic-printer-event'. 299 This trap is sent when requested by a prior subscription for 300 the included printer-level 'jmEventTriggerEvent'. 302 Additional variable-bindings SHALL be appended to this trap 303 for all printer-level events: 304 - Systems that support 'jobName' SHALL add 305 'jmAttributeValue...jobName.1' (if job-level subscription) 306 - Systems that support 'hrSystemDate' defined in 307 the IETF Host Resources MIB (RFC 1514) SHALL add 308 'hrSystemDate' (corresponds to IPP 'printer-current-time') 310 Additional variable-bindings SHOULD be appended to this trap 311 for all printer-level events: 312 - Systems that support 'prtChannelInformation' defined in 313 the (work-in-progress) Printer MIB v2 [PRT-MIB2] SHOULD add 314 'prtChannelInformation' (corresponds to IPP 'printer-uri') 315 - Systems that support 'prtGeneralPrinterName' defined in 316 the (work-in-progress) Printer MIB v2 [PRT-MIB2] SHOULD add 317 'prtGeneralPrinterName' (corresponds to IPP 'printer-name') 319 Systems MAY add other variable-bindings from any MIB." 320 ::= { jmPrinterEventV2EventPrefix 1 } 322 4.2. Job Event Trap 324 -- Job Event Group (Cond Mandatory) 325 -- 326 -- Implementation of this group is conditionally mandatory; 327 -- mandatory for systems which send this Job event via SNMP. 329 jmJobEventV1Enterprise OBJECT-IDENTITY 330 STATUS current 331 DESCRIPTION 332 "The value of the enterprise-specific OID in an SNMPv1 trap 333 for a 'basic-job-event' sent by this managed system." 334 ::= { jobmonMIBNotifications 2 } 336 jmJobEventV2EventPrefix 337 OBJECT IDENTIFIER ::= { jmJobEventV1Enterprise 0 } 339 jmJobEventV2Event NOTIFICATION-TYPE 340 OBJECTS { 341 jmEventTriggerEvent, 342 jmEventSubscriptionID, 343 jmEventSubscriberUserName, 344 jmEventSubscriberUserData, 345 jmJobState, 346 jmJobStateReasons1 347 } 348 STATUS current 349 DESCRIPTION 350 "This SMIv2 trap corresponds to an IPP 'basic-job-event'. 352 This trap is sent when requested by a prior subscription for 353 the included job-level 'jmEventTriggerEvent'. 355 Additional variable-bindings SHALL be appended to this trap 356 for all job-level events: 357 - Systems that support 'jobName' SHALL add 358 'jmAttributeValue...jobName.1' 359 - Systems that support 'jobStateReasonsN' SHALL add 360 'jmAttributeValue...jobStateReasonsN.1' 361 - Systems that support 'hrSystemDate' defined in 362 the IETF Host Resources MIB (RFC 1514) SHALL add 363 'hrSystemDate' (corresponds to IPP 'printer-current-time') 365 Additional variable-bindings SHOULD be appended to this trap 366 for all job-level events: 367 - Systems that support 'prtChannelInformation' defined in 368 the (work-in-progress) Printer MIB v2 [PRT-MIB2] SHOULD add 369 'prtChannelInformation' (corresponds to IPP 'printer-uri') 370 - Systems that support 'prtGeneralPrinterName' defined in 371 the (work-in-progress) Printer MIB v2 [PRT-MIB2] SHOULD add 372 'prtGeneralPrinterName' (corresponds to IPP 'printer-name') 374 Additional variable-bindings SHALL be appended to this trap 375 for 'jobCompleted', 'jobStateChanged', or 'jobPurged': 376 - Systems SHALL add 377 'jmJobKOctetsProcessed' 378 'jmJobImpressionsCompleted' 379 - Systems that support 'sheetsCompleted' SHALL add 380 'jmAttributeValue...sheetsCompleted.1' 382 Additional variable-bindings SHALL be appended to this trap 383 for 'jobProgress': 384 - Systems that support the respective attributes SHALL add 385 'jmAttributeValue...jobCollationType.1' 386 'jmAttributeValue...sheetCompletedCopyNumber.1' 387 'jmAttributeValue...sheetCompletedDocumentNumber.1' 388 'jmAttributeValue...impressionsInterpreted.1' 389 'jmAttributeValue...impressionsCompletedCurrentCopy.1' 391 Systems MAY add other variable-bindings from any MIB." 392 ::= { jmJobEventV2EventPrefix 1 } 394 4.3. Trigger Events 396 JmTriggerEventTC ::= TEXTUAL-CONVENTION 397 STATUS current 398 DESCRIPTION 399 "The trigger event type associated with this event. 401 See: Section 5.2 'notify-events' and 402 Section 7 'Notification Content' in [IPP-NOT]." 403 SYNTAX INTEGER { 404 other(1), 405 unknown(2), 406 none(3), -- SHOULD not be used 407 printerRestarted(11), -- 'printer-restarted' 408 printerShutdown(12), -- 'printer-shutdown' 409 printerStateChanged(13), -- 'printer-state-changed' 410 printerMediaChanged(14), -- 'printer-media-changed' 411 printerConfigChanged(15), -- 'printer-config-changed' 412 printerQueueChanged(16), -- 'printer-queue-changed' 413 printerNoLongerFull(17), -- 'printer-no-longer-full' 414 printerAlmostIdle(18), -- 'printer-almost-idle' 415 jobCreated(21), -- 'job-created' 416 jobCompleted(22), -- 'job-completed' 417 jobStateChanged(23), -- 'job-state-changed' 418 jobConfigChanged(24), -- 'job-config-changed' 419 jobPurged(25), -- 'job-purged' 420 jobProgress(26) -- 'job-progress' 421 } 423 4.4. Event Objects 425 -- Event Group (Cond Mandatory) 426 -- 427 -- Implementation of this group is conditionally mandatory; 428 -- mandatory for systems which support Job events via SNMP. 430 jmEvent OBJECT IDENTIFIER ::= { jobmonMIBObjects 5 } 432 jmEventTriggerEvent OBJECT-TYPE 433 SYNTAX JmTriggerEventTC 434 MAX-ACCESS read-only 435 STATUS current 436 DESCRIPTION 437 "The trigger event type associated with this event. 439 Conformance: This trigger event type SHALL be valid and 440 consistent with [IPP-NOT]. 442 See: Section 5.2 'notify-events' and 443 Section 7 'Notification Content' in [IPP-NOT]." 444 -- DEFVAL intentionally omitted - trigger event SHALL be valid 445 ::= { jmEvent 1 } 447 jmEventSubscriptionID OBJECT-TYPE 448 SYNTAX Integer32 (0..2147483647) 449 MAX-ACCESS read-only 450 STATUS current 451 DESCRIPTION 452 "The subscription identifier associated with this event 453 or zero (if none). 455 Conformance: This subscription identifier SHALL be valid 456 and non-zero, if available on this managed system. 458 See: Section 5.8 'subscription-id' and 459 Section 7 'Notification Content' in [IPP-NOT]." 460 DEFVAL { 0 } -- no subscription ID 461 ::= { jmEvent 2 } 463 jmEventSubscriberUserName OBJECT-TYPE 464 SYNTAX JmUTF8StringTC (SIZE (0..63)) -- 1023 in [IPP-MOD] 465 MAX-ACCESS read-only 466 STATUS current 467 DESCRIPTION 468 "The subscriber user name associated with this event 469 or the empty string (if none). 471 Note: The natural language appropriate for text-to-speech 472 of subscriber user name is orthogonal to the localized text 473 context in IPP 'attributes-natural-language'. The subscriber 474 user name MAY include an in-line 'language tag' using Plane 475 14 'language tag' characters proposed for ISO 10646/Unicode. 477 Conformance: This subscriber user name SHALL be valid 478 and non-empty, if available on this managed system. 480 See: Section 4.3.6 'job-originating-user-name' and 481 Section 4.4.2 'uri-authentication-supported' 482 (usage of 'requesting-user-name') in [IPP-MOD]; 483 Section 5.11 'subscriber-user-name' and 484 Section 7 'Notification Content' in [IPP-NOT]." 485 DEFVAL { ''H } -- no subscriber user name 486 ::= { jmEvent 3 } 488 jmEventSubscriberUserData OBJECT-TYPE 489 SYNTAX OCTET STRING (SIZE (0..63)) -- 63 in [IPP-NOT] 490 MAX-ACCESS read-only 491 STATUS current 492 DESCRIPTION 493 "The subscriber user data associated with this event 494 or the empty string (if none). 496 Conformance: This subscriber user data SHALL be valid 497 and conserved, if available on this managed system. 499 See: Section 5.4 'subscriber-user-data' and 500 Section 7 'Notification Content' in [IPP-NOT]." 501 DEFVAL { ''H } -- no subscriber user data 502 ::= { jmEvent 4 } 504 5. IANA Considerations 506 None - the only enumerated textual convention defined in this documen 507 is proposed for addition to the PWG Job Monitoring MIB which is not a 508 IETF standards track document. The PWG does maintain a registration 509 process for updates to the PWG Job Monitoring MIB. 511 6. Internationalization Considerations 513 The 'jmEventSubscriberUserName' text string defined in this document 514 of type 'JmUTF8StringTC' (UTF-8 stream-encoded ISO 10646/Unicode text 515 defined in the PWG Job Monitoring MIB [PWG-JOB]. The natural languag 516 of this object is inherently ambiguous (as it usually contains some 517 transform of a personal name). 519 7. Security Considerations 521 This IPP Notifications over SNMP mapping defines only 'read-only' 522 objects. It is suitable for use with any version of SNMP, as no upda 523 security is required (because no configuration updates are supported) 525 No sensitive information is available via IPP Notifications over SNMP 527 8. References 529 To be supplied. 531 9. Intellectual Property Notice 533 The IETF takes no position regarding the validity or scope of any 534 intellectual property or other rights that might be claimed to 535 pertain to the implementation or use of the technology described in 536 this document or the extent to which any license under such rights 537 might or might not be available; neither does it represent that it 538 has made any effort to identify any such rights. Information on the 539 IETF's procedures with respect to rights in standards-track and 540 standards-related documentation can be found in BCP-11. Copies of 541 claims of rights made available for publication and any assurances of 542 licenses to be made available, or the result of an attempt made to 543 obtain a general license or permission for the use of such 544 proprietary rights by implementers or users of this specification can 545 be obtained from the IETF Secretariat. 547 The IETF invites any interested party to bring to its attention any 548 copyrights, patents or patent applications, or other proprietary 549 rights which may cover technology that may be required to practice 550 this standard. Please address the information to the IETF Executive 551 Director. 553 10. Authors' Addresses 555 Tom Hastings 556 Xerox Corporation 557 701 S Aviation Blvd, MS 834-03E 558 El Segundo, CA 90245 560 Phone: +1 310-333-6413 561 Email: hastings@cp10.es.xerox.com 563 Ira McDonald 564 High North Inc 565 221 Ridge Ave 566 Grand Marais, MI 49839 568 Phone: +1 906-494-2434 or +1 906-494-2697 569 Email: imcdonal@sdsp.mc.xerox.com 571 11. Full Copyright Statement 573 Copyright (C) The Internet Society (1999). All Rights Reserved. 575 This document and translations of it may be copied and furnished to 576 others, and derivative works that comment on or otherwise explain it 577 or assist in its implementation may be prepared, copied, published 578 and distributed, in whole or in part, without restriction of any 579 kind, provided that the above copyright notice and this paragraph are 580 included on all such copies and derivative works. However, this 581 document itself may not be modified in any way, such as by removing 582 the copyright notice or references to the Internet Society or other 583 Internet organizations, except as needed for the purpose of 584 developing Internet standards in which case the procedures for 585 copyrights defined in the Internet Standards process must be 586 followed, or as required to translate it into languages other than 587 English. 589 The limited permissions granted above are perpetual and will not be 590 revoked by the Internet Society or its successors or assigns. 592 This document and the information contained herein is provided on an 593 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 594 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 595 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 596 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 597 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.