idnits 2.17.1 draft-mcdonald-ldap-printer-schema-10.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([RFC1179], [IPPSURI], [RFC2911], [RFC3510]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 5 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. -- The abstract seems to indicate that this document obsoletes RFC3805, but the header doesn't have an 'Obsoletes:' line to match this. -- The abstract seems to indicate that this document obsoletes RFC2911, but the header doesn't have an 'Obsoletes:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 565 has weird spacing: '...pported ipp-v...' == Line 575 has weird spacing: '...pported comp...' == Line 577 has weird spacing: '...e-color pages...' == Line 578 has weird spacing: '...pported fin...' == Line 583 has weird spacing: '...pported pri...' == (4 more instances...) == 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: Note: LDAP application clients SHOULD NOT attempt to use malformed URI values read from this attribute. LDAP administrative clients SHOULD not write malformed URI values into this attribute. == 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: Note: LDAP application clients SHOULD NOT attempt to use malformed URI values read from this attribute. LDAP administrative clients SHOULD not write malformed URI values into this attribute. == 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: Note: LDAP application clients SHOULD NOT attempt to use malformed URI values read from this attribute. LDAP administrative clients SHOULD not write malformed URI values into this attribute. == 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: Note: LDAP application clients SHOULD NOT attempt to use malformed URN values read from this attribute. LDAP administrative clients SHOULD not write malformed URN values into this attribute. == 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: Note: LDAP application clients SHOULD NOT attempt to use malformed URI values read from this attribute. LDAP administrative clients SHOULD not write malformed URI values into this attribute. == 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: Note: LDAP application clients SHOULD NOT attempt to use malformed URI values read from this attribute. LDAP administrative clients SHOULD not write malformed URI values into this attribute. == 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: 3 March 2014 - draft-mcdonald-ldap-printer-schema-06.txt Working draft - for IEEE-ISTO PWG IPP Everywhere project Global - updated publication and expiration dates in copyright, header, footer, and boilerplate. Global - replaced 'SHOULD not' w/ 'SHOULD NOT' for RFC 2911 compliance, per Alexey Melnikov. Editorial - revised Abstract and section 1 Introduction to clarify that this document is an individual submission to the IETF by the IPP WG of the IEEE-ISTO PWG, per Tom Petch and IPP WG review. Editorial - revised Abstract and section 1 Introduction to clarify that this document obsoletes [RFC3712], per Alexey Melnikov. Editorial - added section 1.1 'Relationship to SLP Printer Service' and section 1.2 'Source of LDAP Printer Attributes' for clarity. Editorial - added section 1.3 'Sources of LDAP Printer Schema OIDs' to describe permanent delegation of "1.3.18.0.2.24.46" to the IEEE-ISTO PWG by IBM in October 2011, per Alexey Melnikov. Editorial - added section 1.4 'Rationale for Design Choices' for clarity. Editorial - revised sections 3.1, 3.4, 3.5, and 3.6 to delete erroneous SHOULD references to structural classes, per Alexey Melnikov. Editorial - revised section 4 to clarify reference to section 4 of [RFC4517] and forward reference to section 6 of LDAP Printer Schema, per Alexey Melnikov. Editorial - revised section 4 to add implementation note about compatibility with existing implementations of [RFC3712] and underlying string length limits in [RFC2707], [RFC2911], [RFC3805], [PWG5107.2], [PWG5100.13], and [PWG5100.14], per Alexey Melnikov. Editorial - revised section 4.4 to change SHOULD to MUST for conformance to [BCP47] for natural language tags, per Alexey Melnikov. Editorial - revised section 4.4 printer-natural-language-configured and section 4.13 printer-generated-natural-language-supported definitions to clarify that they refer to LDAP Printer in syntax DirectoryString (UTF-8), per Alexey Melnikov. Editorial - revised section 4.11 printer-charset-configured and section 4.12 printer-charset-supported definitions to clarify that they refer to IPP protocol values and that corresponding LDAP Printer attributes are always in syntax DirectoryString (UTF-8), per Alexey Melnikov. -- The document date (29 January 2015) is 3375 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'RFC3805' is mentioned on line 2543, but not defined == Missing Reference: 'RFC2707' is mentioned on line 2329, but not defined == Missing Reference: 'RFC1759' is mentioned on line 2476, but not defined ** Obsolete undefined reference: RFC 1759 (Obsoleted by RFC 3805) == Missing Reference: 'IPPEVE1' is mentioned on line 2527, but not defined == Missing Reference: 'IPPJPS3' is mentioned on line 2587, but not defined == Unused Reference: 'RFC4519' is defined on line 2053, but no explicit reference was found in the text == Unused Reference: 'BCP35' is defined on line 2099, but no explicit reference was found in the text == Unused Reference: 'PWG' is defined on line 2107, but no explicit reference was found in the text == Unused Reference: 'PWGIPP' is defined on line 2110, but no explicit reference was found in the text -- No information found for draft-mcdonald-ipps-uri-scheme-xx - is the name correct? ** Obsolete normative reference: RFC 2617 (Obsoleted by RFC 7235, RFC 7615, RFC 7616, RFC 7617) ** Obsolete normative reference: RFC 2911 (Obsoleted by RFC 8011) ** Obsolete normative reference: RFC 5246 (Obsoleted by RFC 8446) ** Obsolete normative reference: RFC 7235 (Obsoleted by RFC 9110) -- Obsolete informational reference (is this intentional?): RFC 4395 (ref. 'BCP35') (Obsoleted by RFC 7595) -- Obsolete informational reference (is this intentional?): RFC 2566 (Obsoleted by RFC 2911) -- Obsolete informational reference (is this intentional?): RFC 3712 (Obsoleted by RFC 7612) Summary: 6 errors (**), 0 flaws (~~), 24 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Pat Fleming 3 INTERNET-DRAFT Independent 4 Obsoletes: 3712 (if approved) Ira McDonald 5 Intended Status: Informational High North 6 Expires: 29 July 2015 29 January 2015 8 Lightweight Directory Access Protocol (LDAP): 9 Schema for Printer Services 10 12 Abstract 14 This document defines a schema, object classes and attributes, for 15 Printers and Print Services, for use with directories that support 16 Lightweight Directory Access Protocol (RFC 4510). This document is 17 based on the Printer attributes listed in Appendix E of Internet 18 Printing Protocol/1.1 (RFC 2911). Additional Printer attributes are 19 based on definitions in the Printer MIB v2 (RFC 3805), IEEE-ISTO PWG 20 Command Set for IEEE 1284 Device ID (PWG 5107.2), IEEE-ISTO PWG IPP 21 Job and Printer Extensions - Set 3 (PWG 5100.13), and IEEE-ISTO PWG 22 IPP Everywhere (PWG 5100.14). 24 This memo is an independent submission to the RFC Editor Stream by 25 the Internet Printing Protocol Working Group of the IEEE-ISTO Printer 26 Working Group, as part of their PWG IPP Everywhere (PWG 5100.14) 27 project for secure mobile printing with vendor-neutral Client 28 software. 30 This document obsoletes RFC 3712. 32 Status of this Memo 34 This Internet-Draft is submitted in full conformance with the 35 provisions of BCP 78 and BCP 79. 37 Internet-Drafts are working documents of the Internet Engineering 38 Task Force (IETF). Note that other groups may also distribute 39 working documents as Internet-Drafts. The list of current Internet- 40 Drafts is at http://datatracker.ietf.org/drafts/current/. 42 Internet-Drafts are draft documents valid for a maximum of six months 43 and may be updated, replaced, or obsoleted by other documents at any 44 time. It is inappropriate to use Internet-Drafts as reference 45 material or to cite them other than as "work in progress." 47 This Internet-Draft will expire on 29 July 2015. 49 Copyright Notice 50 Copyright (c) 2015 IETF Trust and the persons identified as the 51 document authors. All rights reserved. 53 This document is subject to BCP 78 and the IETF Trust's Legal 54 Provisions Relating to IETF Documents 55 (http://trustee.ietf.org/license-info) in effect on the date of 56 publication of this document. Please review these documents 57 carefully, as they describe your rights and restrictions with respect 58 to this document. Code Components extracted from this document must 59 include Simplified BSD License text as described in Section 4.e of 60 the Trust Legal Provisions and are provided without warranty as 61 described in the Simplified BSD License. 63 Table of Contents 65 1. Introduction ............................................... 5 66 1.1. Relationship to SLP Printer Service .................... 5 67 1.2. Source of LDAP Printer Attributes ...................... 5 68 1.3. Source of LDAP Printer Schema OIDs ..................... 6 69 1.3.1. IBM Assignments for RFC 3712 ....................... 6 70 1.3.2. IEEE-ISTO PWG Assignments .......................... 6 71 1.4. Rationale for Design Choices ........................... 6 72 1.4.1. Rationale for using DirectoryString Syntax ......... 6 73 1.4.2. Rationale for using caseIgnoreMatch ................ 7 74 1.4.3. Rationale for using caseIgnoreSubstringsMatch ...... 8 75 2. Terminology and Conventions ................................ 8 76 3. Definition of Object Classes ............................... 10 77 3.1. slpServicePrinter ...................................... 11 78 3.2. printerAbstract ........................................ 11 79 3.3. printerService ......................................... 12 80 3.4. printerServiceAuxClass ................................. 12 81 3.5. printerIPP ............................................. 13 82 3.6. printerLPR ............................................. 13 83 4. Definition of Attribute Types .............................. 14 84 4.1. printer-uri ............................................ 16 85 4.2. printer-xri-supported .................................. 17 86 4.3. printer-name ........................................... 18 87 4.4. printer-natural-language-configured .................... 19 88 4.5. printer-location ....................................... 20 89 4.6. printer-info ........................................... 20 90 4.7. printer-more-info ...................................... 21 91 4.8. printer-make-and-model ................................. 21 92 4.9. printer-ipp-versions-supported ......................... 22 93 4.10. printer-multiple-document-jobs-supported .............. 23 94 4.11. printer-charset-configured ............................ 23 95 4.12. printer-charset-supported ............................. 23 96 4.13. printer-generated-natural-language-supported .......... 24 97 4.14. printer-document-format-supported ..................... 25 98 4.15. printer-color-supported ............................... 25 99 4.16. printer-compression-supported ......................... 25 100 4.17. printer-pages-per-minute .............................. 26 101 4.18. printer-pages-per-minute-color ........................ 26 102 4.19. printer-finishings-supported .......................... 27 103 4.20. printer-number-up-supported ........................... 28 104 4.21. printer-sides-supported ............................... 28 105 4.22. printer-media-supported ............................... 29 106 4.23. printer-media-local-supported ......................... 30 107 4.24. printer-resolution-supported .......................... 30 108 4.25. printer-print-quality-supported ....................... 31 109 4.26. printer-job-priority-supported ........................ 32 110 4.27. printer-copies-supported .............................. 32 111 4.28. printer-job-k-octets-supported ........................ 32 112 4.29. printer-current-operator .............................. 33 113 4.30. printer-service-person ................................ 33 114 4.31. printer-delivery-orientation-supported ................ 34 115 4.32. printer-stacking-order-supported ...................... 34 116 4.33. printer-output-features-supported ..................... 35 117 4.34. printer-aliases ....................................... 36 118 4.35. printer-device-id ..................................... 36 119 4.36. printer-device-service-count .......................... 37 120 4.37. printer-uuid .......................................... 37 121 4.38. printer-charge-info ................................... 38 122 4.39. printer-charge-info-uri ............................... 39 123 4.40. printer-geo-location .................................. 39 124 4.41. printer-ipp-features-supported ........................ 40 125 5. Definition of Syntaxes ..................................... 42 126 6. Definition of Matching Rules ............................... 42 127 7. IANA Considerations ........................................ 43 128 7.1. Existing Object Classes ................................ 43 129 7.2. Existing Attribute Types ............................... 43 130 7.3. Registration of Attribute Types ........................ 44 131 8. Internationalization Considerations ........................ 46 132 9. Security Considerations .................................... 46 133 10. References ................................................ 47 134 10.1. Normative References .................................. 47 135 10.2. Informative References ................................ 49 136 11. Acknowledgments ........................................... 51 137 12. Appendix A - Changes since RFC 3712 ....................... 51 138 13. Appendix B - Abbreviations Used in this Document .......... 52 139 14. Appendix X - Change History ............................... 53 140 15. Authors' Addresses ........................................ 59 141 1. Introduction 143 This document defines several object classes to provide Lightweight 144 Directory Access Protocol [RFC4510] applications with flexible 145 options in defining Printer information using LDAP schema. Classes 146 are provided for defining directory entries with common Printer 147 information as well as for extending existing directory entries with 148 SLPv2 [RFC2608], IPP/1.1 [RFC2911], and LPR [RFC1179] 149 protocol-specific information. 151 This memo is an independent submission to the RFC Editor Stream by 152 the Internet Printing Protocol Working Group of the IEEE-ISTO Printer 153 Working Group, as part of their PWG IPP Everywhere (PWG 5100.14) 154 project for secure mobile printing with vendor-neutral Client 155 software. 157 Please send comments directly to the authors at the addresses listed 158 in the section "Authors' Addresses". 160 1.1. Relationship to SLP Printer Service 162 The schema defined in this document is technically aligned with the 163 stable IANA-registered 'service:printer:' v2.0 template [SLPPRT20], 164 for compatibility with already deployed Service Location Protocol 165 (SLPv2) [RFC2608] service advertising and discovery infrastructure. 166 The attribute syntaxes are technically aligned with the 167 'service:printer:' v2.0 template - therefore simpler types are 168 sometimes used (for example, 'DirectoryString' [RFC4517] rather than 169 'labeledURI' [RFC2079] for the 'printer-uri' attribute). 171 1.2. Source of LDAP Printer Attributes 173 The schema defined in this document is based on: all of the Printer 174 attributes listed in Appendix E 'Generic Directory Schema' that are 175 defined in section 4.4 'Printer Description Attributes' of Internet 176 Printing Protocol/1.1: Model and Semantics [RFC2911]; and selected 177 Printer attributes defined in the Printer MIB v2 [RFC3805], IEEE-ISTO 178 PWG Command Set for IEEE 1284 Device ID [PWG5107.2], IEEE-ISTO PWG 179 IPP Job and Printer Extensions - Set 3 [PWG5100.13], and IEEE-ISTO 180 PWG IPP Everywhere [PWG5100.14] 182 See the table of Printer attributes and source documents in section 4 183 'Definition of Attribute Types' in this document. 185 1.3. Source of LDAP Printer Schema OIDs 187 1.3.1. IBM Assignments for RFC 3712 189 In March 2000, IBM permanently assigned ASN.1 OIDs to all of the 190 object classes and attributes types that were defined in the original 191 LDAP Printer Schema [RFC3712]. 193 1.3.2. IEEE-ISTO PWG Assignments 195 In October 2011, IBM permanently delegated the base ASN.1 OID 196 "1.3.18.0.2.24.46" to the IEEE-ISTO PWG for use in any PWG project. 197 Subsequently, the PWG permanently assigned subordinate ASN.1 OIDs to 198 all of the new attribute types defined in this updated LDAP Printer 199 Schema. 201 1.4. Rationale for Design Choices 203 1.4.1. Rationale for using DirectoryString Syntax 205 The attribute syntax 'DirectoryString' (UTF-8 [STD63]) defined in 206 [RFC4517] is specified for several groups of string attributes that 207 are defined in this document: 209 1) URI 210 - printer-uri, printer-xri-supported, printer-more-info, 211 printer-charge-info-uri, printer-uuid 213 The UTF-8 encoding is compatible with deployment of (UTF-8 based) 214 IRI Internationalized Resource Identifiers (IRIs) [RFC3987]. 216 2) Description 217 - printer-name, printer-location, printer-info, 218 printer-make-and-model 220 The UTF-8 encoding supports descriptions in any language, 221 conformant with the IETF Policy on Character Sets and Languages 222 [BCP18]. 224 Note: The printer-natural-language-configured attribute contains 225 a language tag [BCP47] for these description attributes (for 226 example, to support text-to-speech conversions). 228 3) Keyword 229 - printer-compression-supported, printer-finishings-supported, 230 printer-media-supported, printer-media-local-supported, 231 printer-print-quality-supported 233 The UTF-8 encoding is compatible with the current IPP/1.1 234 [RFC2911] definition of the equivalent attributes, most of which 235 have the IPP/1.1 union syntax 'keyword or name'. The keyword 236 attributes defined in this document are extensible by 237 site-specific or vendor-specific 'names' which behave like new 238 'keywords' 240 Note: In IPP/1.1, each value is strongly typed over-the-wire as 241 either 'keyword' or 'name'. This union selector is not preserved 242 in the definitions of these equivalent LDAP attributes. 244 1.4.2. Rationale for using caseIgnoreMatch 246 The EQUALITY matching rule 'caseIgnoreMatch' defined in [RFC4517] is 247 specified for several groups of string attributes that are defined in 248 this document: 250 1) URI 252 These URI attributes specify EQUALITY matching with 253 'caseIgnoreMatch' (rather than with 'caseExactMatch') in order to 254 conform to the spirit of [STD66], which requires case insensitive 255 matching on the host part of a URI versus case sensitive matching 256 on the remainder of a URI. 258 These URI attributes follow existing practice of supporting case 259 insensitive equality matching for host names in the 260 associatedDomain attribute defined in [RFC4524]. 262 Either equality matching rule choice would be a compromise: 263 a) case sensitive whole URI matching can lead to false negative 264 matches and has been shown to be fragile (given deployed client 265 applications that 'pretty up' host names displayed and 266 transferred in URI); 267 b) case insensitive whole URI matching can lead to false positive 268 matches, although it is a dangerous practice to publish URI that 269 differ only by case (for example, in the path elements). 271 2) Description 273 Case insensitive equality matching is more user-friendly for 274 description attributes. 276 3) Keyword 278 Case insensitive equality matching is more user-friendly for 279 keyword attributes. 281 4) IEEE 1284 Device ID 283 Case insensitive equality matching is mandatory for IEEE 1284 284 Device ID attributes. 286 1.4.3. Rationale for using caseIgnoreSubstringsMatch 288 The SUBSTR matching rule 'caseIgnoreSubstringsMatch' defined in 289 [RFC4517] is specified for several groups of string attributes that 290 are defined in this document: 292 1) URI 294 These URI attributes follow existing practice of supporting case 295 insensitive equality matching for host names in the 296 associatedDomain attribute defined in [RFC4524]. 298 2) Description 300 Support for case insensitive substring matching is more 301 user-friendly for description attributes. 303 3) Keyword 305 Support for case insensitive substring matching is more 306 user-friendly for keyword attributes. 308 4) IEEE 1284 Device ID 310 Support for case insensitive substring matching is mandatory for 311 IEEE 1284 Device ID attributes. 313 2. Terminology and Conventions 315 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 316 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 317 document are to be interpreted as described in [RFC2119]. 319 Schema definitions are provided using LDAP [RFC4510] description 320 formats. Definitions provided here are formatted (line wrapped) for 321 readability. 323 3. Definition of Object Classes 325 We define the following LDAP object classes for use with both generic 326 Printer related information and services specific to SLPv2 [RFC2608], 327 IPP/1.1 [RFC2911], and LPR [RFC1179]. 329 slpServicePrinter - auxiliary class for SLP registered Printers 330 printerAbstract - abstract class for all Printer classes 331 printerService - structural class for Printers 332 printerServiceAuxClass - auxiliary class for Printers 333 printerIPP - auxiliary class for IPP Printers 334 printerLPR - auxiliary class for LPR Printers 336 The following are some examples of how applications could choose to 337 use these classes when creating directory entries: 339 1) Use printerService for directory entries containing common 340 Printer information. 342 2) Use both printerService and slpServicePrinter for directory 343 entries containing common Printer information for SLP registered 344 Printers. 346 3) Use printerService, printerLPR and printerIPP for directory 347 entries containing common Printer information for Printers that 348 support both LPR and IPP. 350 4) Use printerServiceAuxClass and object classes not defined by this 351 document for directory entries containing common Printer 352 information. In this example, printerServiceAuxClass is used for 353 extending other structural classes defining Printer information 354 with common printer information defined in this document. 356 Refer to Section 4 for definition of attribute types referenced by 357 these object classes. We use attribute names instead of OIDs in 358 object class definitions for clarity. Some attribute names described 359 in [RFC2911] have been prefixed with 'printer-' as recommended in 360 [RFC2926] and [SLPPRT20]. 362 3.1. slpServicePrinter 364 ( 1.3.18.0.2.6.254 365 NAME 'slpServicePrinter' 366 DESC 'Service Location Protocol (SLP) information.' 367 AUXILIARY 368 SUP slpService 369 ) 371 This auxiliary class defines Service Location Protocol (SLPv2) 372 [RFC2608] specific information. It MAY be used to create new or 373 extend existing directory entries with SLP 'service:printer' abstract 374 service type information as defined in [SLPPRT20]. This object class 375 is derived from 'slpService', the parent class for all SLP services, 376 defined in [RFC2926]. 378 3.2. printerAbstract 380 ( 1.3.18.0.2.6.258 381 NAME 'printerAbstract' 382 DESC 'Printer related information.' 383 ABSTRACT 384 SUP top 385 MAY ( printer-name $ 386 printer-natural-language-configured $ 387 printer-location $ 388 printer-info $ 389 printer-more-info $ 390 printer-make-and-model $ 391 printer-multiple-document-jobs-supported $ 392 printer-charset-configured $ 393 printer-charset-supported $ 394 printer-generated-natural-language-supported $ 395 printer-document-format-supported $ 396 printer-color-supported $ 397 printer-compression-supported $ 398 printer-pages-per-minute $ 399 printer-pages-per-minute-color $ 400 printer-finishings-supported $ 401 printer-number-up-supported $ 402 printer-sides-supported $ 403 printer-media-supported $ 404 printer-media-local-supported $ 405 printer-resolution-supported $ 406 printer-print-quality-supported $ 407 printer-job-priority-supported $ 408 printer-copies-supported $ 409 printer-job-k-octets-supported $ 410 printer-current-operator $ 411 printer-service-person $ 412 printer-delivery-orientation-supported $ 413 printer-stacking-order-supported $ 414 printer-output-features-supported $ 415 printer-device-id $ 416 printer-device-service-count $ 417 printer-uuid $ 418 printer-charge-info $ 419 printer-charge-info-uri $ 420 printer-geo-location ) 421 ) 423 This abstract class defines Printer information. It is a base class 424 for deriving other Printer related classes, such as, but not limited 425 to, classes defined in this document. It defines a common set of 426 printer attributes that are not specific to any one type of service, 427 protocol or operating system. 429 3.3. printerService 431 ( 1.3.18.0.2.6.255 432 NAME 'printerService' 433 DESC 'Printer information.' 434 STRUCTURAL 435 SUP printerAbstract 436 MAY ( printer-uri $ 437 printer-xri-supported ) 438 ) 440 This structural class defines Printer information. It is derived 441 from class printerAbstract and thus inherits common Printer 442 attributes. This class can be used with or without auxiliary classes 443 to define printer information. Auxiliary classes can be used to 444 extend the common printer information with protocol, service or 445 operating system specific information. 447 Note: When extending other structural classes with auxiliary 448 classes, printerService SHOULD NOT be used. 450 3.4. printerServiceAuxClass 452 ( 1.3.18.0.2.6.257 453 NAME 'printerServiceAuxClass' 454 DESC 'Printer information.' 455 AUXILIARY 456 SUP printerAbstract 457 MAY ( printer-uri $ 458 printer-xri-supported ) 459 ) 461 This auxiliary class defines Printer information. It is derived from 462 class printerAbstract and thus inherits common Printer attributes. 464 3.5. printerIPP 466 ( 1.3.18.0.2.6.256 467 NAME 'printerIPP' 468 DESC 'Internet Printing Protocol (IPP) information.' 469 AUXILIARY 470 SUP top 471 MAY ( printer-ipp-versions-supported $ 472 printer-ipp-features-supported $ 473 printer-multiple-document-jobs-supported ) 474 ) 476 This auxiliary class defines Internet Printing Protocol (IPP/1.1) 477 [RFC2911] information. It is used to extend structural classes with 478 IPP specific Printer information. 480 Note: See IPP URL Scheme [RFC3510] and IPP over HTTPS Transport 481 Binding and 'ipps' URI Scheme [IPPSURI] for conforming URI for IPP 482 Printers. 484 3.6. printerLPR 486 ( 1.3.18.0.2.6.253 487 NAME 'printerLPR' 488 DESC 'LPR information.' 489 AUXILIARY 490 SUP top 491 MUST ( printer-name ) 492 MAY ( printer-aliases) 493 ) 495 This auxiliary class defines LPR [RFC1179] information. It is used 496 to identify directory entries that support LPR. 498 4. Definition of Attribute Types 500 The following attribute types are referenced by the object classes 501 defined in Section 3. 503 The following attribute types reference syntax OIDs defined in 504 Section 3 of [RFC4517] (see Section 5 'Definition of Syntaxes' 505 below). 507 The following attribute types reference matching rule names (instead 508 of OIDs) for clarity (see Section 6 below). For optional attributes, 509 if the Printer information is not known, the attribute value SHOULD 510 NOT be set. In the following definitions, referenced matching rules 511 are defined in Section 4 of [RFC4517] and discussed in Section 6 512 'Definition of Matching Rules' later in this document. 514 Note: For compatibility with existing implementations of [RFC3712] 515 and underlying string length limits in [RFC2707], [RFC2911], 516 [RFC3805], [PWG5107.2], [PWG5100.13], and [PWG5100.14], 517 implementations of the attributes defined in this document SHOULD NOT 518 exceed those underlying string length limits (to avoid truncation and 519 false matches). 521 Note: For interoperability and consistent text display, values of 522 attributes defined in this document: (a) SHOULD be normalized as 523 recommended in Unicode Format for Network Interchange [RFC5198]; (b) 524 SHOULD NOT contain DEL or any C0 or C1 control characters except for 525 HT, CR, and LF; (c) SHOULD only contain CR and LF characters together 526 (not as singletons); and SHOULD NOT contain HT, CR, or LF characters 527 in names, e.g., printer-name and printer-aliases. 529 Note: Some of the following attributes are described as 'List of 530 xxx' (using a comma as the member delimiter). Some other attributes 531 are described as 'One of xxx' (single-valued). In all cases, any 532 attribute can have multiple values represented as multiple instances, 533 except where explictly restricted in syntax to be single-valued. 535 Note: Values of the string attributes printer-xri-supported and 536 printer-resolution-supported use different field delimiters ('<' and 537 '>', respectively). These two field delimiters are different for 538 compatibility with the corresponding attributes in the 539 IANA-registered SLP 'service:printer:' v2.0 template [SLPPRT20], 540 which was defined before the original LDAP Printer Schema [RFC3712] 541 was written. 543 The following table is a summary of the attribute names defined by 544 this document and their corresponding source document names as 545 defined in [RFC2911], [RFC3805], [PWG5107.2], or [PWG5100.13]. Some 546 source attribute names have been prefixed with 'printer-' as 547 recommended in [RFC2926], to address the flat namespace for LDAP 548 identifiers. 550 LDAP & SLP Printer Schema Source Document and Attribute Name 551 ------------------------------ ------------------------------------- 552 *** IPP/1.1 and Semantics Model [RFC2911] 553 printer-uri 554 printer-xri-supported 555 [printer-uri-supported] 556 [uri-authentication-supported] 557 [uri-security-supported] 558 printer-name printer-name 559 printer-natural-language-configured 560 natural-language-configured 561 printer-location printer-location 562 printer-info printer-info 563 printer-more-info printer-more-info 564 printer-make-and-model printer-make-and-model 565 printer-ipp-versions-supported ipp-versions-supported 566 printer-multiple-document-jobs-supported 567 multiple-document-jobs-supported 568 printer-charset-configured charset-configured 569 printer-charset-supported charset-supported 570 printer-generated-natural-language-supported 571 generated-natural-language-supported 572 printer-document-format-supported 573 document-format-supported 574 printer-color-supported color-supported 575 printer-compression-supported compression-supported 576 printer-pages-per-minute pages-per-minute 577 printer-pages-per-minute-color pages-per-minute-color 578 printer-finishings-supported finishings-supported 579 printer-number-up-supported number-up-supported 580 printer-sides-supported sides-supported 581 printer-media-supported media-supported 582 printer-media-local-supported [site names from IPP media-supported] 583 printer-resolution-supported printer-resolution-supported 584 printer-print-quality-supported print-quality-supported 585 printer-job-priority-supported job-priority-supported 586 printer-copies-supported copies-supported 587 printer-job-k-octets-supported job-k-octets-supported 589 *** Printer MIB v2 [RFC3805] 590 printer-current-operator prtGeneralCurrentOperator 591 printer-service-person prtGeneralServicePerson 592 printer-delivery-orientation-supported 593 prtOutputPageDeliveryOrientation 594 printer-stacking-order-supported 595 prtOutputStackingOrder 596 printer-output-features-supported 597 [prtOutputBursting] 599 [prtOutputDecollating] 600 [prtOutputPageCollated] 601 [prtOutputOffsetStacking] 602 printer-aliases prtGeneralPrinterName 604 *** Cmd Set 1284 Device ID [PWG5107.2] 605 printer-device-id printer-device-id 607 *** IPP Job/Printer Ext Set3 [PWG5100.13] 608 printer-device-service-count device-service-count 609 printer-uuid printer-uuid 610 printer-charge-info printer-charge-info 611 printer-charge-info-uri printer-charge-info-uri 612 printer-geo-location printer-geo-location 613 printer-ipp-features-supported ipp-features-supported 615 4.1. printer-uri 617 ( 1.3.18.0.2.4.1140 618 NAME 'printer-uri' 619 DESC 'A URI supported by this Printer.' 620 EQUALITY caseIgnoreMatch 621 SUBSTR caseIgnoreSubstringsMatch 622 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 623 SINGLE-VALUE 624 ) 626 If the printer-xri-supported LDAP attribute is implemented, then this 627 printer-uri value MUST be listed in printer-xri-supported. 629 See [STD66] for details of URI syntax. 631 Note: For compatibility with IPP/1.1 [RFC2911], values of this 632 attribute SHOULD NOT exceed 1023 octets in length. 634 Note: LDAP application clients SHOULD NOT attempt to use malformed 635 URI values read from this attribute. LDAP administrative clients 636 SHOULD not write malformed URI values into this attribute. 638 Note: See IPP URL Scheme [RFC3510] and IPP over HTTPS Transport 639 Binding and 'ipps' URI Scheme [IPPSURI] for conforming URI for IPP 640 Printers. 642 Note: For SLP registered Printers, the LDAP printer-uri attribute 643 SHOULD be set to the value of the SLP-registered URL of the Printer, 644 for interworking with SLPv2 [RFC2608] service discovery. 646 Note: See Sections 1.1, 1.2, and 1.3 for rationale for design 647 choices. 649 4.2. printer-xri-supported 651 ( 1.3.18.0.2.4.1107 652 NAME 'printer-xri-supported' 653 DESC 'An XRI (extended resource identifier) supported by this 654 Printer.' 655 EQUALITY caseIgnoreMatch 656 SUBSTR caseIgnoreSubstringsMatch 657 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 658 ) 660 An XRI (extended resource identifier) supported by this Printer. 661 Each value of this attribute MUST consist of a URI (uniform resource 662 identifier) followed by (optional) authentication and security 663 fields. 665 Each XRI field MUST be delimited by '<', with optional trailing 666 whitespace. For example: 668 'uri=ipp://example.com/ipp< auth=digest< sec=tls<' 669 'uri=ipps://example.com/ipp< auth=digest< sec=tls<' 670 'uri=lpr://example.com/lpr< auth=none< sec=none<' 671 'uri=mailto:printer@example.com< auth=none< sec=none<' 673 Note: See the note in section 4 about the different field delimiters 674 used in the printer-xri-supported and printer-resolution-supported 675 attributes ('<' and '>', respectively), chosen for compatibility with 676 the IANA-registered SLP 'service:printer:' v2.0 template [SLPPRT20]. 678 Note: Multiple values for this attribute are represented as multiple 679 instances of this attribute. 681 See [STD66] for details of URI syntax. 683 Note: For compatibility with IPP/1.1 [RFC2911], values of this 684 attribute SHOULD NOT exceed 1023 octets in length. 686 Note: LDAP application clients SHOULD NOT attempt to use malformed 687 URI values read from this attribute. LDAP administrative clients 688 SHOULD not write malformed URI values into this attribute. 690 Note: This attribute is based on the IPP/1.1 [RFC2911] attributes 691 'printer-uri-supported', 'uri-authentication-supported', and 692 'uri-security-supported' (called the 'Three Musketeers' because they 693 are parallel, ordered attributes). This attribute unfolds those 694 IPP/1.1 attributes and thus avoids the ordering (and same number of 695 values) constraints of the IPP/1.1 separate attributes. 697 Defined keywords for fields include: 699 'uri' (IPP 'printer-uri-supported') 700 'auth' (IPP 'uri-authentication-supported') 701 'sec' (IPP 'uri-security-supported') 703 A missing 'auth' field SHOULD be interpreted to mean 'none'. Per 704 IPP/1.1 [RFC2911], IPP Job and Printer Extensions - Set 3 705 [PWG5100.13], and IANA IPP Registry [IANAIPP], defined values of the 706 'auth' field include: 708 'none' (no authentication for this URI) 709 'requesting-user-name' (from operation request) 710 'basic' (HTTP/1.1 Basic [RFC2617] and [RFC7235]) 711 'digest' (HTTP/1.1 Digest [RFC2617] and [RFC7235]) 712 'certificate' (X.509 Certificate [RFC5280] and [RFC6818]) 713 'negotiate' (HTTP/1.1 Negotiate [RFC4559]) 715 The 'certificate' value refers to the IPP Client certificate 716 extracted from the TLS session. 718 A missing 'sec' field SHOULD be interpreted to mean 'none'. Per 719 IPP/1.1 [RFC2911] and IANA IPP Registry [IANAIPP], defined values of 720 the 'sec' field include: 722 'none' (no security for this URI) 723 'ssl3' (Netscape SSL3) 724 'tls' (IETF TLS, [RFC5246]) 726 Note: The syntax and delimiter for this attribute are aligned with 727 the equivalent attribute in the 'service:printer:' v2.0 template 728 [SLPPRT20]. Whitespace is permitted after (but not before) the 729 delimiter '<'. 731 Note: See IPP URL Scheme [RFC3510] and IPP over HTTPS Transport 732 Binding and 'ipps' URI Scheme [IPPSURI] for conforming URI for IPP 733 Printers. 735 Note: See Sections 1.1, 1.2, and 1.3 for rationale for design 736 choices. 738 4.3. printer-name 740 ( 1.3.18.0.2.4.1135 741 NAME 'printer-name' 742 DESC 'The site-specific administrative name of this Printer.' 743 EQUALITY caseIgnoreMatch 744 SUBSTR caseIgnoreSubstringsMatch 745 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 746 SINGLE-VALUE 747 ) 749 Values of this attribute SHOULD be specified in the language 750 specified in printer-natural-language-configured (for example, to 751 support text-to-speech conversions), although the Printer's name MAY 752 be specified in any language. 754 Note: For compatibility with IPP/1.1 [RFC2911], values of this 755 attribute SHOULD NOT exceed 255 octets in length. 757 Note: This name can be the last part of the Printer's URI or it can 758 be completely unrelated. This name can contain characters that are 759 not allowed in a conventional URI (see [STD66]). 761 Note: For interoperability, values of this attribute: (a) SHOULD be 762 normalized as recommended in Unicode Format for Network Interchange 763 [RFC5198]; and (b) SHOULD NOT contain DEL or any C0 or C1 control 764 characters. 766 4.4. printer-natural-language-configured 768 ( 1.3.18.0.2.4.1119 769 NAME 'printer-natural-language-configured' 770 DESC 'The configured natural language for LDAP attributes of 771 syntax DirectoryString (UTF-8) in this directory entry.' 772 EQUALITY caseIgnoreMatch 773 SUBSTR caseIgnoreSubstringsMatch 774 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 775 SINGLE-VALUE 776 ) 778 Also, a possible natural language for IPP protocol string attributes 779 set by operator, system administrator, or manufacturer. Also, the 780 (declared) natural language of the printer-name, printer-location, 781 printer-info, and printer-make-and-model attributes of this Printer. 783 Values of language tags MUST conform to Tags for Identifying 784 Languages [BCP47]. For example: 786 'en-us' (English as spoken in the US) 787 'fr-fr' (French as spoken in France) 789 Note: For compatibility with IPP/1.1 [RFC2911], values of this 790 attribute SHOULD NOT exceed 63 octets in length. 792 Note: For compatibility with IPP/1.1 [RFC2911], language tags in 793 this attribute SHOULD be lowercase normalized. 795 4.5. printer-location 797 ( 1.3.18.0.2.4.1136 798 NAME 'printer-location' 799 DESC 'The physical location of this Printer.' 800 EQUALITY caseIgnoreMatch 801 SUBSTR caseIgnoreSubstringsMatch 802 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 803 SINGLE-VALUE 804 ) 806 For example: 808 'Room 123A' 809 'Second floor of building XYZ' 811 Note: For compatibility with IPP/1.1 [RFC2911], values of this 812 attribute SHOULD NOT exceed 127 octets in length. 814 Note: For interoperability and consistent text display, values of 815 this attribute: (a) SHOULD be normalized as recommended in Unicode 816 Format for Network Interchange [RFC5198]; (b) SHOULD NOT contain DEL 817 or any C0 or C1 control characters except for HT, CR, and LF; and (c) 818 SHOULD only contain CR and LF characters together (not as 819 singletons). 821 4.6. printer-info 823 ( 1.3.18.0.2.4.1139 824 NAME 'printer-info' 825 DESC 'Descriptive information about this Printer.' 826 EQUALITY caseIgnoreMatch 827 SUBSTR caseIgnoreSubstringsMatch 828 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 829 SINGLE-VALUE 830 ) 832 For example: 834 'This Printer can be used for printing color transparencies for 835 HR presentations' 836 'Out of courtesy for others, please print only small (1-5 page) 837 jobs at this Printer' 838 'This Printer is going away on July 1, 1997, please find a new 839 Printer' 841 Note: For compatibility with IPP/1.1 [RFC2911], values of this 842 attribute SHOULD NOT exceed 127 octets in length. 844 Note: For interoperability and consistent text display, values of 845 this attribute: (a) SHOULD be normalized as recommended in Unicode 846 Format for Network Interchange [RFC5198]; (b) SHOULD NOT contain DEL 847 or any C0 or C1 control characters except for HT, CR, and LF; and (c) 848 SHOULD only contain CR and LF characters together (not as 849 singletons). 851 4.7. printer-more-info 853 ( 1.3.18.0.2.4.1134 854 NAME 'printer-more-info' 855 DESC 'A URI for more information about this specific Printer.' 856 EQUALITY caseIgnoreMatch 857 SUBSTR caseIgnoreSubstringsMatch 858 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 859 SINGLE-VALUE 860 ) 862 For example, this could be an HTTP URI referencing an HTML page 863 accessible to a Web Browser. The information obtained from this URI 864 is intended for end user consumption. 866 See [STD66] for details of URI syntax. 868 Note: For compatibility with IPP/1.1 [RFC2911], values of this 869 attribute SHOULD NOT exceed 1023 octets in length. 871 Note: LDAP application clients SHOULD NOT attempt to use malformed 872 URI values read from this attribute. LDAP administrative clients 873 SHOULD not write malformed URI values into this attribute. 875 Note: See Sections 1.1, 1.2, and 1.3 for rationale for design 876 choices. 878 4.8. printer-make-and-model 880 ( 1.3.18.0.2.4.1138 881 NAME 'printer-make-and-model' 882 DESC 'Make and model of this Printer.' 883 EQUALITY caseIgnoreMatch 884 SUBSTR caseIgnoreSubstringsMatch 885 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 886 SINGLE-VALUE 887 ) 889 Note: For compatibility with IPP/1.1 [RFC2911], values of this 890 attribute SHOULD NOT exceed 127 octets in length. 892 Note: The Printer manufacturer MAY initially populate this 893 attribute. 895 Note: For interoperability and consistent text display, values of 896 this attribute: (a) SHOULD be normalized as recommended in Unicode 897 Format for Network Interchange [RFC5198]; (b) SHOULD NOT contain DEL 898 or any C0 or C1 control characters except for HT, CR, and LF; and (c) 899 SHOULD only contain CR and LF characters together (not as 900 singletons). 902 4.9. printer-ipp-versions-supported 904 ( 1.3.18.0.2.4.1133 905 NAME 'printer-ipp-versions-supported' 906 DESC 'List of IPP versions supported by this Printer.' 907 EQUALITY caseIgnoreMatch 908 SUBSTR caseIgnoreSubstringsMatch 909 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 910 ) 912 Comma-delimited list of IPP versions supported by this Printer. For 913 example: 915 '1.1,2.0' 917 Note: Length overflow in values of this attribute MUST be handled by 918 multiple instances of this attribute, i.e., individual 919 comma-delimited list members MUST NOT be truncated. 921 The IPP protocol version(s) MUST include major and minor versions, 922 i.e., the exact version numbers for which this Printer implementation 923 meets the IPP version-specific conformance requirements and 924 registered in the IANA IPP Registry [IANAIPP]. 926 IANA-registered versions of IPP currently are: 928 '1.0' (IPP/1.0 [RFC2566], OBSOLETE) 929 '1.1' (IPP/1.1 [RFC2911]) 930 '2.0' (IPP/2.0 [PWG5100.12]) 931 '2.1' (IPP/2.1 [PWG5100.12]) 932 '2.2' (IPP/2.2 [PWG5100.12]) 934 4.10. printer-multiple-document-jobs-supported 936 ( 1.3.18.0.2.4.1132 937 NAME 'printer-multiple-document-jobs-supported' 938 DESC 'Indicates whether or not this Printer supports more than one 939 document per job.' 940 EQUALITY booleanMatch 941 SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 942 SINGLE-VALUE 943 ) 945 4.11. printer-charset-configured 947 ( 1.3.18.0.2.4.1109 948 NAME 'printer-charset-configured' 949 DESC 'The configured charset for IPP protocol values of error 950 and status messages generated by this Printer.' 951 EQUALITY caseIgnoreMatch 952 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 953 SINGLE-VALUE 954 ) 956 Also, a possible charset for IPP protocol string attributes set by 957 operator, system administrator, or manufacturer. For example: 959 'utf-8' (ISO 10646/Unicode in UTF-8 transform [STD63]) 960 'iso-8859-1' (Latin1) 962 Values of charset tags SHOULD be defined in the IANA Registry of 963 Character Sets [IANACHAR] (see also [BCP19]) and the '(preferred MIME 964 name)' SHOULD be used as the charset tag in this attribute. 966 Note: For compatibility with IPP/1.1 [RFC2911], values of this 967 attribute SHOULD NOT exceed 63 octets in length. 969 Note: For compatibility with IPP/1.1 [RFC2911], charset tags in this 970 attribute SHOULD be lowercase normalized. 972 4.12. printer-charset-supported 974 ( 1.3.18.0.2.4.1131 975 NAME 'printer-charset-supported' 976 DESC 'One of the charsets supported for IPP protocol values of 977 IPP string attributes that correspond to attributes of 978 syntax DirectoryString (UTF-8) for this directory entry.' 980 EQUALITY caseIgnoreMatch 981 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 982 ) 984 One of the charsets supported for IPP protocol string attributes that 985 correspond to attributes of syntax DirectoryString (UTF-8) for this 986 directory entry. For example: 988 'iso-8859-1' (ISO Latin1) 989 'utf-8' (UTF-8 [STD63]) 991 Note: Multiple values for this attribute are represented as multiple 992 instances of this attribute. 994 Values of charset tags SHOULD be defined in the IANA Registry of 995 Character Sets [IANACHAR] (see also [BCP19]) and the '(preferred MIME 996 name)' SHOULD be used as the charset tag in this attribute. 998 Note: For compatibility with IPP/1.1 [RFC2911], values of this 999 attribute SHOULD NOT exceed 63 octets in length. 1001 Note: For compatibility with IPP/1.1 [RFC2911], charset tags in this 1002 attribute SHOULD be lowercase normalized. 1004 4.13. printer-generated-natural-language-supported 1006 ( 1.3.18.0.2.4.1137 1007 NAME 'printer-generated-natural-language-supported' 1008 DESC 'One of the natural languages supported for LDAP attributes of 1009 syntax DirectoryString (UTF-8) in this directory entry.' 1010 EQUALITY caseIgnoreMatch 1011 SUBSTR caseIgnoreSubstringsMatch 1012 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1013 ) 1015 Values of language tags SHOULD conform to Tags for Identifying 1016 Languages [BCP47]. For example: 1018 'en-us' (English as spoken in the US) 1019 'fr-ca' (French as spoken in Canada) 1021 Note: Multiple values for this attribute are represented as multiple 1022 instances of this attribute. 1024 Note: For compatibility with IPP/1.1 [RFC2911], values of this 1025 attribute SHOULD NOT exceed 63 octets in length. 1027 Note: For compatibility with IPP/1.1 [RFC2911], language tags in 1028 this attribute SHOULD be lowercase normalized. 1030 4.14. printer-document-format-supported 1032 ( 1.3.18.0.2.4.1130 1033 NAME 'printer-document-format-supported' 1034 DESC 'One of the source document formats which can be interpreted 1035 and printed by this Printer.' 1036 EQUALITY caseIgnoreMatch 1037 SUBSTR caseIgnoreSubstringsMatch 1038 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1039 ) 1041 Values of document formats SHOULD be MIME media types defined in the 1042 IANA Registry of MIME Media Types [IANAMIME] (see also [BCP13]). 1044 For example: 1046 'application/postscript' (Adobe PostScript) 1047 'text/plain' (plain text) 1049 Note: Multiple values for this attribute are represented as multiple 1050 instances of this attribute. 1052 Note: For compatibility with IPP/1.1 [RFC2911], values of this 1053 attribute SHOULD NOT exceed 255 octets in length. 1055 4.15. printer-color-supported 1057 ( 1.3.18.0.2.4.1129 1058 NAME 'printer-color-supported' 1059 DESC 'Indicates whether this Printer is capable of any type of color 1060 printing at all, including highlight color.' 1061 EQUALITY booleanMatch 1062 SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 1063 SINGLE-VALUE 1064 ) 1066 4.16. printer-compression-supported 1068 ( 1.3.18.0.2.4.1128 1069 NAME 'printer-compression-supported' 1070 DESC 'List of compression algorithms supported by this Printer.' 1071 EQUALITY caseIgnoreMatch 1072 SUBSTR caseIgnoreSubstringsMatch 1073 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1074 ) 1076 Comma-delimited list of compression algorithms supported by this 1077 Printer. For example: 1079 'none' 1080 'deflate,gzip' 1082 Note: Length overflow in values of this attribute MUST be handled by 1083 multiple instances of this attribute, i.e., individual 1084 comma-delimited list members MUST NOT be truncated. 1086 Note: For compatibility with IPP/1.1 [RFC2911], values of this 1087 attribute SHOULD NOT exceed 255 octets in length. 1089 Values defined in IPP/1.1 [RFC2911] and recorded in the IANA IPP 1090 Registry [IANAIPP] include: 1092 'none' (no compression is used) 1093 'deflate' (public domain ZIP described in [RFC1951]) 1094 'gzip' (GNU ZIP described in [RFC1952]) 1095 'compress' (UNIX compression described in [RFC1977]) 1097 4.17. printer-pages-per-minute 1099 ( 1.3.18.0.2.4.1127 1100 NAME 'printer-pages-per-minute' 1101 DESC 'The nominal number of pages per minute which can be output by 1102 this Printer.' 1103 EQUALITY integerMatch 1104 ORDERING integerOrderingMatch 1105 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1106 SINGLE-VALUE 1107 ) 1109 This attribute is informative, not a service guarantee. Typically, 1110 it is the value used in marketing literature to describe this 1111 Printer. For example, the value for a simplex or black-and-white 1112 print mode. 1114 4.18. printer-pages-per-minute-color 1116 ( 1.3.18.0.2.4.1126 1117 NAME 'printer-pages-per-minute-color' 1118 DESC 'The nominal number of color pages per minute which can be 1119 output by this Printer.' 1120 EQUALITY integerMatch 1121 ORDERING integerOrderingMatch 1122 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1123 SINGLE-VALUE 1124 ) 1126 This attribute is informative, not a service guarantee. Typically, 1127 it is the value used in marketing literature to describe this 1128 Printer. 1130 4.19. printer-finishings-supported 1132 ( 1.3.18.0.2.4.1125 1133 NAME 'printer-finishings-supported' 1134 DESC 'List of finishing operations supported by this Printer.' 1135 EQUALITY caseIgnoreMatch 1136 SUBSTR caseIgnoreSubstringsMatch 1137 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1138 ) 1140 Comma-delimited list of finishing operations supported by this 1141 Printer. For example: 1143 'staple' 1144 'staple,punch,bind' 1146 Note: Length overflow in values of this attribute MUST be handled by 1147 multiple instances of this attribute, i.e., individual 1148 comma-delimited list members MUST NOT be truncated. 1150 Note: For compatibility with IPP/1.1 [RFC2911], values of this 1151 attribute SHOULD NOT exceed 255 octets in length. 1153 Values defined in IPP/1.1 [RFC2911] and recorded in the IANA IPP 1154 Registry [IANAIPP] include: 1156 'none', 'staple', 'punch', 'cover', 'bind', 'saddle-stitch', 1157 'edge-stitch', 'staple-top-left', 'staple-bottom-left', 1158 'staple-top-right', 'staple-bottom-right', 'edge-stitch-left', 1159 'edge-stitch-top', 'edge-stitch-right', 'edge-stitch-bottom', 1160 'staple-dual-left', 'staple-dual-top', 'staple-dual-right', 1161 'staple-dual-bottom'. 1163 Note: Implementations MAY support other values. 1165 4.20. printer-number-up-supported 1167 ( 1.3.18.0.2.4.1124 1168 NAME 'printer-number-up-supported' 1169 DESC 'Maximum number of print-stream pages that can be imposed upon a 1170 single side of an instance of selected medium by this Printer.' 1171 EQUALITY integerMatch 1172 ORDERING integerOrderingMatch 1173 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1174 SINGLE-VALUE 1175 ) 1177 Maximum number of print-stream pages that can be imposed upon a 1178 single side of an instance of a selected medium by this Printer. For 1179 example: 1181 '1' 1182 '4' 1184 Note: Values of this attribute differ from the corresponding IPP 1185 attribute, in that only the maximum number-up is mapped from the 1186 corresponding IPP attribute 'number-up-supported' defined in 1187 [RFC2911]. 1189 4.21. printer-sides-supported 1191 ( 1.3.18.0.2.4.1123 1192 NAME 'printer-sides-supported' 1193 DESC 'List of impression sides (one or two) and the two-sided 1194 impression rotations supported by this Printer.' 1195 EQUALITY caseIgnoreMatch 1196 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1197 ) 1199 Comma-delimited list of impression sides (one or two) and the 1200 two-sided impression rotations supported by this Printer. For 1201 example: 1203 'one-sided' 1204 'one-sided,two-sided-short-edge' 1206 Note: Length overflow in values of this attribute MUST be handled by 1207 multiple instances of this attribute, i.e., individual 1208 comma-delimited list members MUST NOT be truncated. 1210 Note: For compatibility with IPP/1.1 [RFC2911], values of this 1211 attribute SHOULD NOT exceed 255 octets in length. 1213 Values defined in IPP/1.1 [RFC2911] and recorded in the IANA IPP 1214 Registry [IANAIPP] are: 1216 'one-sided' 1217 'two-sided-long-edge' 1218 'two-sided-short-edge' 1220 4.22. printer-media-supported 1222 ( 1.3.18.0.2.4.1122 1223 NAME 'printer-media-supported' 1224 DESC 'One of the names/sizes/types/colors of the media supported by 1225 this Printer.' 1226 EQUALITY caseIgnoreMatch 1227 SUBSTR caseIgnoreSubstringsMatch 1228 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1229 ) 1231 Values SHOULD conform to PWG Media Standardized Names [PWG5101.1]. 1233 Note: For compatibility with IPP/1.1 [RFC2911], values of this 1234 attribute SHOULD NOT exceed 255 octets in length. 1236 Values of standardized media size names defined in [PWG5101.1] and 1237 recorded in the IANA IPP Registry [IANAIPP] include: 1239 'na_letter_8.5x11in' 1240 'iso_a4_210x297mm' 1242 Values of standardized media types defined in [PWG5101.1] and 1243 recorded in the IANA IPP Registry [IANAIPP] include: 1245 'envelope' 1246 'stationery' 1248 Values of standardized media colors defined in [PWG5101.1] and 1249 recorded in the IANA IPP Registry [IANAIPP] include: 1251 'white' 1252 'blue' 1254 Note: Multiple values for this attribute are represented as multiple 1255 instances of this attribute. 1257 4.23. printer-media-local-supported 1259 ( 1.3.18.0.2.4.1117 1260 NAME 'printer-media-local-supported' 1261 DESC 'One of the site-specific media supported by this Printer.' 1262 EQUALITY caseIgnoreMatch 1263 SUBSTR caseIgnoreSubstringsMatch 1264 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1265 ) 1267 Values SHOULD conform to PWG Media Standardized Names [PWG5101.1]. 1269 For example: 1271 'custom_purchasing-form_8.5x11in' (site-specific name) 1273 Note: Multiple values for this attribute are represented as multiple 1274 instances of this attribute. 1276 Note: For compatibility with IPP/1.1 [RFC2911], values of this 1277 attribute SHOULD NOT exceed 255 octets in length. 1279 4.24. printer-resolution-supported 1281 ( 1.3.18.0.2.4.1121 1282 NAME 'printer-resolution-supported' 1283 DESC 'One of the resolutions supported for printing documents by this 1284 Printer.' 1285 EQUALITY caseIgnoreMatch 1286 SUBSTR caseIgnoreSubstringsMatch 1287 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1288 ) 1290 Each resolution value MUST be a string containing 3 fields: 1291 1) Cross feed direction resolution (positive integer); 1292 2) Feed direction resolution (positive integer); 1293 3) Unit - 'dpi' (dots per inch) or 'dpcm' (dots per centimeter). 1295 Each resolution field MUST be delimited by '>', with optional 1296 trailing whitespace. For example: 1298 '300> 300> dpi>' 1299 '600> 600> dpi>' 1301 Note: See the note in section 4 about the different field delimiters 1302 used in the printer-xri-supported and printer-resolution-supported 1303 attributes ('<' and '>', respectively), chosen for compatibility with 1304 the IANA-registered SLP 'service:printer:' v2.0 template [SLPPRT20]. 1306 Note: Multiple values for this attribute are represented as multiple 1307 instances of this attribute. 1309 Note: This attribute is based on 'printer-resolution-supported' 1310 defined in IPP/1.1 [RFC2911] (which has a binary complex encoding) 1311 derived from 'prtMarkerAddressabilityFeedDir', 1312 'prtMarkerAddressabilityXFeedDir', and 'prtMarkerAddressabilityUnit' 1313 defined in the Printer MIB v2 [RFC3805] (which have integer 1314 encodings). 1316 Note: The syntax and delimiter for this attribute are aligned with 1317 the equivalent attribute in the 'service:printer:' v2.0 template 1318 [SLPPRT20]. Whitespace is permitted after (but not before) the 1319 delimiter '>'. 1321 4.25. printer-print-quality-supported 1323 ( 1.3.18.0.2.4.1120 1324 NAME 'printer-print-quality-supported' 1325 DESC 'List of print qualities supported for printing documents on 1326 this Printer.' 1327 EQUALITY caseIgnoreMatch 1328 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1329 ) 1331 Comma-delimited list of print qualities supported for printing 1332 documents on this Printer. For example: 1334 'unknown' 1335 'draft,normal,high' 1337 Note: Length overflow in values of this attribute MUST be handled by 1338 multiple instances of this attribute, i.e., individual 1339 comma-delimited list members MUST NOT be truncated. 1341 Values defined in IPP/1.1 [RFC2911] and recorded in the IANA IPP 1342 Registry [IANAIPP] include: 1344 'draft' 1345 'normal' 1346 'high' 1348 Note: The value 'unknown' MUST only be reported if the corresponding 1349 IPP attribute is not present, i.e., the value 'unknown' is an 1350 artifact of this LDAP mapping. 1352 4.26. printer-job-priority-supported 1354 ( 1.3.18.0.2.4.1110 1355 NAME 'printer-job-priority-supported' 1356 DESC 'Indicates the number of job priority levels supported by this 1357 Printer.' 1358 EQUALITY integerMatch 1359 ORDERING integerOrderingMatch 1360 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1361 SINGLE-VALUE 1362 ) 1364 An IPP/1.1 [RFC2911] conformant Printer, which supports job priority, 1365 always supports a full range of priorities from '1' to '100' (to 1366 ensure consistent behavior), therefore this attribute describes the 1367 'granularity' of priority supported. Values of this attribute are 1368 from '1' to '100'. 1370 4.27. printer-copies-supported 1372 ( 1.3.18.0.2.4.1118 1373 NAME 'printer-copies-supported' 1374 DESC 'The maximum number of copies of a document that can be printed 1375 as a single job on this Printer.' 1376 EQUALITY integerMatch 1377 ORDERING integerOrderingMatch 1378 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1379 SINGLE-VALUE 1380 ) 1382 A positive value indicates the maximum supported copies. A value of 1383 '0' indicates no maximum limit. A value of '-1' indicates 'unknown'. 1385 Note: The syntax and values for this attribute are aligned with the 1386 equivalent attribute in the 'service:printer:' v2.0 template 1387 [SLPPRT20]. 1389 4.28. printer-job-k-octets-supported 1391 ( 1.3.18.0.2.4.1111 1392 NAME 'printer-job-k-octets-supported' 1393 DESC 'The maximum size in kilobytes (1,024 octets actually) incoming 1394 print job that this Printer will accept.' 1395 EQUALITY integerMatch 1396 ORDERING integerOrderingMatch 1397 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1398 SINGLE-VALUE 1399 ) 1401 A positive value indicates the maximum supported job size. A value 1402 of '0' indicates no maximum limit. A value of '-1' indicates 1403 'unknown'. 1405 Note: The syntax and values for this attribute are aligned with the 1406 equivalent attribute in the 'service:printer:' v2.0 template 1407 [SLPPRT20]. 1409 4.29. printer-current-operator 1411 ( 1.3.18.0.2.4.1112 1412 NAME 'printer-current-operator' 1413 DESC 'The identity of the current human operator responsible for 1414 operating this Printer.' 1415 EQUALITY caseIgnoreMatch 1416 SUBSTR caseIgnoreSubstringsMatch 1417 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1418 SINGLE-VALUE 1419 ) 1421 The value of this attribute SHOULD include information that would 1422 enable other humans to reach the operator, such as a telephone 1423 number. 1425 Note: For interoperability and consistent text display, values of 1426 this attribute: (a) SHOULD be normalized as recommended in Unicode 1427 Format for Network Interchange [RFC5198]; (b) SHOULD NOT contain DEL 1428 or any C0 or C1 control characters except for HT, CR, and LF; and (c) 1429 SHOULD only contain CR and LF characters together (not as 1430 singletons). 1432 4.30. printer-service-person 1434 ( 1.3.18.0.2.4.1113 1435 NAME 'printer-service-person' 1436 DESC 'The identity of the current human service person responsible 1437 for servicing this Printer.' 1438 EQUALITY caseIgnoreMatch 1439 SUBSTR caseIgnoreSubstringsMatch 1440 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1441 SINGLE-VALUE 1442 ) 1443 The value of this attribute SHOULD include information that would 1444 enable other humans to reach the service person, such as a telephone 1445 number. 1447 Note: For interoperability and consistent text display, values of 1448 this attribute: (a) SHOULD be normalized as recommended in Unicode 1449 Format for Network Interchange [RFC5198]; (b) SHOULD NOT contain DEL 1450 or any C0 or C1 control characters except for HT, CR, and LF; and (c) 1451 SHOULD only contain CR and LF characters together (not as 1452 singletons). 1454 4.31. printer-delivery-orientation-supported 1456 ( 1.3.18.0.2.4.1114 1457 NAME 'printer-delivery-orientation-supported' 1458 DESC 'List of delivery orientations of pages as they are printed 1459 and ejected supported by this Printer.' 1460 EQUALITY caseIgnoreMatch 1461 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1462 ) 1464 Comma-delimited list of delivery orientations of pages as they are 1465 printed and ejected supported by this Printer. For example: 1467 'unknown' 1468 'face-up,face-down' 1470 Values defined in Printer MIB v2 [RFC3805] for 1471 prtOutputPageDeliveryOrientation are: 1473 'face-up' 1474 'face-down' 1476 Note: The value 'unknown' MUST only be reported if the corresponding 1477 Printer MIB attribute is not present, i.e., the value 'unknown' is an 1478 artifact of this LDAP mapping. 1480 Note: The syntax and values for this attribute are aligned with the 1481 equivalent attribute in the 'service:printer:' v2.0 template 1482 [SLPPRT20]. 1484 4.32. printer-stacking-order-supported 1486 ( 1.3.18.0.2.4.1115 1487 NAME 'printer-stacking-order-supported' 1488 DESC 'List of stacking orders of pages as they are printed and 1489 ejected supported by this Printer.' 1490 EQUALITY caseIgnoreMatch 1491 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1492 ) 1494 Comma-delimited list of stacking orders of pages as they are printed 1495 and ejected supported by this Printer. For example: 1497 'unknown' 1498 'first-to-last' 1499 'first-to-last,last-to-first' 1501 Values defined in Printer MIB v2 [RFC3805] for prtOutputStackingOrder 1502 are: 1504 'first-to-last' 1505 'last-to-first' 1507 Note: The value 'unknown' MUST only be reported if the corresponding 1508 Printer MIB attribute is not present, i.e., the value 'unknown' is an 1509 artifact of this LDAP mapping. 1511 Note: The syntax and values for this attribute are aligned with the 1512 equivalent attribute in the 'service:printer:' v2.0 template 1513 [SLPPRT20]. 1515 4.33. printer-output-features-supported 1517 ( 1.3.18.0.2.4.1116 1518 NAME 'printer-output-features-supported' 1519 DESC 'List of output features supported by this Printer.' 1520 EQUALITY caseIgnoreMatch 1521 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1522 ) 1524 Comma-delimited list of output features supported by this Printer. 1525 For example: 1527 'unknown' 1528 'bursting,decollating' 1529 'offset-stacking' 1531 Note: Length overflow in values of this attribute MUST be handled by 1532 multiple instances of this attribute, i.e., individual 1533 comma-delimited list members MUST NOT be truncated. 1535 Values defined in Printer MIB v2 [RFC3805] for prtOutputBursting, 1536 prtOutputDecollating, prtOutputPageCollated, and 1537 prtOutputOffsetStacking are: 1539 'bursting' 1540 'decollating' 1541 'page-collating' 1542 'offset-stacking' 1544 Note: The value 'unknown' MUST only be reported if the corresponding 1545 Printer MIB attributes are not present, i.e., the value 'unknown' is 1546 an artifact of this LDAP mapping. 1548 Note: The syntax and values for this attribute are aligned with the 1549 equivalent attribute in the 'service:printer:' v2.0 template 1550 [SLPPRT20]. 1552 Note: Implementations MAY support other values. 1554 4.34. printer-aliases 1556 ( 1.3.18.0.2.4.1108 1557 NAME 'printer-aliases' 1558 DESC 'One of the site-specific administrative names of this Printer 1559 in addition to the value specified for printer-name.' 1560 EQUALITY caseIgnoreMatch 1561 SUBSTR caseIgnoreSubstringsMatch 1562 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1563 ) 1565 Values of this attribute SHOULD be specified in the language 1566 specified in printer-natural-language-configured (for example, to 1567 support text-to-speech conversions), although the Printer's alias MAY 1568 be specified in any language. 1570 Note: Multiple values for this attribute are represented as multiple 1571 instances of this attribute. 1573 Note: For compatibility with IPP/1.1 [RFC2911], values of this 1574 attribute SHOULD NOT exceed 255 octets in length. 1576 Note: For interoperability, values of this attribute: (a) SHOULD be 1577 normalized as recommended in Unicode Format for Network Interchange 1578 [RFC5198]; and (b) SHOULD NOT contain DEL or any C0 or C1 control 1579 characters. 1581 4.35. printer-device-id 1583 ( 1.3.18.0.2.24.46.1.101 1584 NAME 'printer-device-id' 1585 DESC 'The IEEE 1284 Device ID for this Printer.' 1586 EQUALITY caseIgnoreMatch 1587 SUBSTR caseIgnoreSubstringsMatch 1588 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1589 SINGLE-VALUE 1590 ) 1592 Values of this attribute SHOULD conform to IEEE-ISTO PWG Command Set 1593 Format for IEEE 1284 Device ID [PWG5107.2]. 1595 Note: For compatibility with [PWG5100.14] and [PWG5107.2], values of 1596 this attribute SHOULD NOT exceed 1023 octets in length. 1598 4.36. printer-device-service-count 1600 ( 1.3.18.0.2.24.46.1.102 1601 NAME 'printer-device-service-count' 1602 DESC 'The number of Printer (Print Service) instances configured on 1603 this Imaging Device (host system).' 1604 EQUALITY integerMatch 1605 ORDERING integerOrderingMatch 1606 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1607 SINGLE-VALUE 1608 ) 1610 A positive value indicates the number of Printer (Print Service) 1611 instances configured on this Imaging Device (host system). A value 1612 of '-1' indicates 'unknown'. A value of '0' is not meaningful 1613 (because this attribute must be reported by some Printer instance). 1615 Note: The syntax and values for this attribute are aligned with the 1616 equivalent 'device-service-count' attribute defined in [PWG5100.13]. 1618 4.37. printer-uuid 1620 ( 1.3.18.0.2.24.46.1.104 1621 NAME 'printer-uuid' 1622 DESC 'A URN specifying UUID of this Printer (Print Service) instance 1623 on this Imaging Device (host system).' 1624 EQUALITY caseIgnoreMatch 1625 SUBSTR caseIgnoreSubstringsMatch 1626 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1627 SINGLE-VALUE 1628 ) 1630 The UUID of this Printer (Print Service) instance on this Imaging 1631 Device (host system). For example: 1633 'urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6' 1635 Values of this attribute MUST conform to the UUID URN namespace 1636 [RFC4122]. 1638 Note: For compatibility with [PWG5100.13] and [RFC4122], values of 1639 this attribute SHOULD NOT exceed 45 octets in length. 1641 Note: LDAP application clients SHOULD NOT attempt to use malformed 1642 URN values read from this attribute. LDAP administrative clients 1643 SHOULD not write malformed URN values into this attribute. 1645 Note: The syntax and values for this attribute are aligned with the 1646 equivalent 'printer-uuid' attribute defined in [PWG5100.13]. 1648 4.38. printer-charge-info 1650 ( 1.3.18.0.2.24.46.1.105 1651 NAME 'printer-charge-info' 1652 DESC 'Descriptive information about paid printing services for this 1653 Printer.' 1654 EQUALITY caseIgnoreMatch 1655 SUBSTR caseIgnoreSubstringsMatch 1656 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1657 SINGLE-VALUE 1658 ) 1660 For example: 1662 'This Printer can be used for paid printing at 2 cents/page.' 1664 Note: For compatibility with [PWG5100.13], values of this attribute 1665 SHOULD NOT exceed 1023 octets in length. 1667 Note: For interoperability and consistent text display, values of 1668 this attribute: (a) SHOULD be normalized as recommended in Unicode 1669 Format for Network Interchange [RFC5198]; (b) SHOULD NOT contain any 1670 C0 or C1 control characters except for HT, CR, and LF; and (c) SHOULD 1671 only contain CR and LF characters together (not as singletons). 1673 Note: The syntax and values for this attribute are aligned with the 1674 equivalent 'printer-charge-info' attribute defined in [PWG5100.13]. 1676 4.39. printer-charge-info-uri 1678 ( 1.3.18.0.2.24.46.1.106 1679 NAME 'printer-charge-info-uri' 1680 DESC 'A URI for a human-readable Web page for paid printing services 1681 for this Printer.' 1682 EQUALITY caseIgnoreMatch 1683 SUBSTR caseIgnoreSubstringsMatch 1684 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1685 SINGLE-VALUE 1686 ) 1688 For example: 1690 'http://example.com/charges' 1692 See [STD66] for details of URI syntax. 1694 Note: For compatibility with IPP/1.1 [RFC2911] and [PWG5100.13], 1695 values of this attribute SHOULD NOT exceed 1023 octets in length. 1697 Note: LDAP application clients SHOULD NOT attempt to use malformed 1698 URI values read from this attribute. LDAP administrative clients 1699 SHOULD not write malformed URI values into this attribute. 1701 Note: The syntax and values for this attribute are aligned with the 1702 equivalent 'printer-charge-info-uri' attribute defined in 1703 [PWG5100.13]. 1705 4.40. printer-geo-location 1707 ( 1.3.18.0.2.24.46.1.107 1708 NAME 'printer-geo-location' 1709 DESC 'A geo: URI specifying the geographic location of this Printer.' 1710 EQUALITY caseIgnoreMatch 1711 SUBSTR caseIgnoreSubstringsMatch 1712 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1713 SINGLE-VALUE 1714 ) 1716 For example: 1718 'geo:13.4125,103.8667' 1720 Values of this attribute MUST conform to the 'geo' URI scheme 1721 [RFC5870]. 1723 Note: For compatibility with IPP/1.1 [RFC2911] and [PWG5100.13], 1724 values of this attribute SHOULD NOT exceed 1023 octets in length. 1726 Note: LDAP application clients SHOULD NOT attempt to use malformed 1727 URI values read from this attribute. LDAP administrative clients 1728 SHOULD not write malformed URI values into this attribute. 1730 Note: The syntax and values for this attribute are aligned with the 1731 equivalent 'printer-geo-location' attribute defined in [PWG5100.13]. 1733 4.41. printer-ipp-features-supported 1735 ( 1.3.18.0.2.24.46.1.108 1736 NAME 'printer-ipp-features-supported' 1737 DESC 'List of IPP protocol features that this Printer supports.' 1738 EQUALITY caseIgnoreMatch 1739 SUBSTR caseIgnoreSubstringsMatch 1740 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1741 ) 1743 Comma-delimited list of IPP protocol features that this Printer 1744 supports. For example: 1746 'none' 1747 'unknown' 1748 'proof-print' 1749 'ipp-everywhere,proof-print,job-save' 1751 Note: Length overflow in values of this attribute MUST be handled by 1752 multiple instances of this attribute, i.e., individual 1753 comma-delimited list members MUST NOT be truncated. 1755 Values of this attribute SHOULD specify only IANA-registered keywords 1756 for the 'ipp-features-supported' attribute defined in [PWG5100.13] or 1757 other standards track IETF or IEEE-ISTO PWG specifications if this 1758 Printer implementation meets all of the IPP feature-specific 1759 conformance requirements. 1761 IANA-registered values include: 1763 'none' (No extension features are supported) 1764 'document-object' (Document object defined in [PWG5100.5]) 1765 'job-save' (Job save defined in [PWG5100.11]) 1766 'ipp-everywhere' (IPP Everywhere defined in [PWG5100.14]) 1767 'page-overrides' (Page overrides defined in [PWG5100.6]) 1768 'proof-print' (Proof print defined in [PWG5100.11]) 1769 'subscription-object' (Subscription object defined in [RFC3995]) 1771 Note: The value 'unknown' MUST only be reported if the corresponding 1772 IPP Printer attribute is not present, i.e., the value 'unknown' is an 1773 artifact of this LDAP mapping. 1775 Note: The syntax and values for this attribute are aligned with the 1776 equivalent 'printer-ipp-features-supported' attribute defined in 1777 [PWG5100.13]. 1779 5. Definition of Syntaxes 1781 No new attribute syntaxes are defined by this document. 1783 The attribute types defined in Section 4 of this document reference 1784 syntax OIDs defined in Section 3 of [RFC4517], which are summarized 1785 below: 1787 Syntax OID Syntax Description 1788 ------------------------------ ------------------ 1789 1.3.6.1.4.1.1466.115.121.1.7 Boolean 1790 1.3.6.1.4.1.1466.115.121.1.15 DirectoryString (UTF-8 [STD63]) 1791 1.3.6.1.4.1.1466.115.121.1.27 Integer 1793 6. Definition of Matching Rules 1795 No new matching rules are defined by this document. 1797 The attribute types defined in Section 4 of this document reference 1798 matching rules defined in Section 4 of [RFC4517], which are 1799 summarized below: 1801 Matching Rule OID Matching Rule Name Usage 1802 ------------------------------ ------------------ ----- 1803 2.5.13.13 booleanMatch EQUALITY 1804 2.5.13.2 caseIgnoreMatch EQUALITY 1805 2.5.13.14 integerMatch EQUALITY 1806 2.5.13.15 integerOrderingMatch ORDERING 1807 2.5.13.4 caseIgnoreSubstringsMatch SUBSTR 1809 7. IANA Considerations 1811 This document does not define any new syntaxes or matching rules. 1813 This document does define the following Object Identifier 1814 Descriptors, most of which were previously registered by IANA when 1815 RFC 3712 was published and a few of which are new and should be 1816 registered by IANA when this document is published. 1818 7.1. Existing Object Classes 1820 The following table lists the Object Class OIDs that were previously 1821 assigned by IBM and registered by IANA when RFC 3712 was published. 1823 Object Class OID 1824 ------------------------------------ ----------------------- 1825 slpServicePrinter 1.3.18.0.2.6.254 1826 printerAbstract 1.3.18.0.2.6.258 1827 printerService 1.3.18.0.2.6.255 1828 printerServiceAuxClass 1.3.18.0.2.6.257 1829 printerIPP 1.3.18.0.2.6.256 1830 printerLPR 1.3.18.0.2.6.253 1832 7.2. Existing Attribute Types 1834 The following table lists the Attribute Type OIDs that were 1835 previously assigned by IBM and registered by IANA when RFC 3712 was 1836 published. 1838 Attribute Type OID 1839 ------------------------------------ ----------------------- 1840 printer-uri 1.3.18.0.2.4.1140 1841 printer-xri-supported 1.3.18.0.2.4.1107 1842 printer-name 1.3.18.0.2.4.1135 1843 printer-natural-language-configured 1.3.18.0.2.4.1119 1844 printer-location 1.3.18.0.2.4.1136 1845 printer-info 1.3.18.0.2.4.1139 1846 printer-more-info 1.3.18.0.2.4.1134 1847 printer-make-and-model 1.3.18.0.2.4.1138 1848 printer-ipp-versions-supported 1.3.18.0.2.4.1133 1849 printer-multiple-document-jobs-supported 1.3.18.0.2.4.1132 1850 printer-charset-configured 1.3.18.0.2.4.1109 1851 printer-charset-supported 1.3.18.0.2.4.1131 1852 printer-generated-natural-language-supported 1.3.18.0.2.4.1137 1853 printer-document-format-supported 1.3.18.0.2.4.1130 1854 printer-color-supported 1.3.18.0.2.4.1129 1855 printer-compression-supported 1.3.18.0.2.4.1128 1856 printer-pages-per-minute 1.3.18.0.2.4.1127 1857 printer-pages-per-minute-color 1.3.18.0.2.4.1126 1858 printer-finishings-supported 1.3.18.0.2.4.1125 1859 printer-number-up-supported 1.3.18.0.2.4.1124 1860 printer-sides-supported 1.3.18.0.2.4.1123 1861 printer-media-supported 1.3.18.0.2.4.1122 1862 printer-media-local-supported 1.3.18.0.2.4.1117 1863 printer-resolution-supported 1.3.18.0.2.4.1121 1864 printer-print-quality-supported 1.3.18.0.2.4.1120 1865 printer-job-priority-supported 1.3.18.0.2.4.1110 1866 printer-copies-supported 1.3.18.0.2.4.1118 1867 printer-job-k-octets-supported 1.3.18.0.2.4.1111 1868 printer-current-operator 1.3.18.0.2.4.1112 1869 printer-service-person 1.3.18.0.2.4.1113 1870 printer-delivery-orientation-supported 1.3.18.0.2.4.1114 1871 printer-stacking-order-supported 1.3.18.0.2.4.1115 1872 printer-output-features-supported 1.3.18.0.2.4.1116 1873 printer-aliases 1.3.18.0.2.4.1108 1875 7.3. Registration of Attribute Types 1877 The following registration lists the new Attribute Type OIDs that 1878 were assigned by IEEE-IST0 PWG and should be registered by IANA when 1879 this document is published. 1881 Subject: Request for LDAP Descriptor Registration 1883 Descriptor (short name): see table below 1885 Object Identifier: see table below 1887 Person & email address to contact for further information: see below 1889 Usage: attribute type 1891 Specification: RFCnnnn [ [RFC Editor: to be assigned] ] 1893 Author/Change Controller: 1895 Ira McDonald 1896 High North Inc 1897 221 Ridge Ave 1898 Grand Marais, MI 49839 1899 USA 1900 Phone: +1 906-494-2434 1901 Email: blueroofmusic@gmail.com 1903 Comments: 1905 Attribute Type OID 1906 ------------------------------------ ----------------------- 1907 printer-device-id 1.3.18.0.2.24.46.1.101 1908 printer-device-service-count 1.3.18.0.2.24.46.1.102 1909 printer-uuid 1.3.18.0.2.24.46.1.104 1910 printer-charge-info 1.3.18.0.2.24.46.1.105 1911 printer-charge-info-uri 1.3.18.0.2.24.46.1.106 1912 printer-geo-location 1.3.18.0.2.24.46.1.107 1913 printer-ipp-features-supported 1.3.18.0.2.24.46.1.108 1915 8. Internationalization Considerations 1917 All text string attributes defined in this document of syntax 1918 'DirectoryString' [RFC4517] have values that are encoded in UTF-8 1919 [STD63], as required by [RFC4517]. 1921 A language tag [BCP47] for all of the text string attributes defined 1922 in this document is contained in the 1923 printer-natural-language-configured attribute. 1925 Therefore, all object classes defined in this document conform to the 1926 IETF Policy on Character Sets and Languages [BCP18]. 1928 Note: For interoperability and consistent text display, values of 1929 attributes defined in this document: (a) SHOULD be normalized as 1930 recommended in Unicode Format for Network Interchange [RFC5198]; (b) 1931 SHOULD NOT contain DEL or any C0 or C1 control characters except for 1932 HT, CR, and LF; (c) SHOULD only contain CR and LF characters together 1933 (not as singletons); and SHOULD NOT contain HT, CR, or LF characters 1934 in names, e.g., printer-name and printer-aliases. 1936 9. Security Considerations 1938 See [RFC4513] for detailed guidance on authentication methods for 1939 LDAP and the use of TLS/1.2 [RFC5246] to supply connection 1940 confidentiality and data integrity for LDAP sessions. 1942 As with any LDAP schema, it is important to protect specific entries 1943 and attributes with the appropriate access control. It is 1944 particularly important that only administrators can modify entries 1945 defined in this LDAP Printer schema. Otherwise, an LDAP client might 1946 be fooled into diverting print service requests from the original 1947 Printer (or spooler) to a malicious intruder's host system, thus 1948 exposing the information in printed documents. 1950 Note: Security vulnerabilities can arise if DEL or any C0 or C1 1951 control characters are included in names, e.g., printer-name or 1952 printer-aliases. 1954 For additional security considerations of deploying Printers in an 1955 IPP environment, see Section 8 of [RFC2911]. 1957 10. References 1959 10.1. Normative References 1961 [BCP47] A. Phillips, Ed., M. Davis, Ed. Tags for Identifying 1962 Languages, BCP 47, RFC 5646, September 2009. 1964 [IANACHAR] Internet Assigned Numbers Authority (IANA) Registry 1965 "Character Sets" 1966 1968 [IANAIPP] Internet Assigned Numbers Authority (IANA) Registry 1969 "Internet Printing Protocol" 1970 1972 [IANAMIME] Internet Assigned Numbers Authority (IANA) Registry "MIME 1973 Media Types" 1974 1976 [IPPSURI] McDonald, I., and M. Sweet. IPP over HTTPS Transport 1977 Binding and 'ipps' URI Scheme, draft-mcdonald-ipps-uri-scheme-xx.txt, 1978 work-in-progress. 1980 [PWG5100.5] Carney, D., Hastings, T., and P. Zehler. Internet 1981 Printing Protocol (IPP): Document Object, PWG 5100.5, October 2003. 1982 1985 [PWG5100.6] Zehler, P., Herriot, R., and K. Ocke. Internet Printing 1986 Protocol (IPP): Page Overrides, October 2003. 1987 1990 [PWG5100.12] Bergman, R., McDonald, I., and M. Sweet. Internet 1991 Printing Protocol Version 2.0 Second Edition (IPP/2.0 SE), PWG 1992 5100.12, February 2011. 1993 1996 [PWG5100.13] Sweet, M., and I. McDonald. IEEE-ISTO PWG IPP Job and 1997 Printer Extensions - Set 3, PWG 5100.13, July 2012. 1998 2001 [PWG5100.14] Sweet, M., and I. McDonald. IEEE-ISTO PWG IPP 2002 Everywhere, January 2013. 2004 2007 [PWG5101.1] Bergman, R., Hastings, T., and M. Sweet. IEEE-ISTO PWG 2008 Media Standardized Names 2.0, PWG 5101.1, March 2013. 2009 2012 [PWG5107.2] I. McDonald. IEEE-ISTO PWG Command Set for IEEE 1284 2013 Device ID, PWG 5107.2, May 2010. 2014 2017 [RFC2119] S. Bradner. Key words for use in RFCs to Indicate 2018 Requirement Levels, RFC 2119 / BCP 14, March 1997. 2020 [RFC2617] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., 2021 Leach, P., Luotonen, A., and L. Stewart. HTTP Authentication: Basic 2022 and Digest Access Authentication, RFC 2617, June 1999. 2024 [RFC2911] T. Hastings, Ed., Herriot, R., Isaacson, S., and P. Powell. 2025 Internet Printing Protocol/1.1: Model and Semantics, RFC 2911, 2026 September 2000. 2028 [RFC2926] Kempf, J., Moats, R., and P. St. Pierre. Conversion of 2029 LDAP Schemas to and from SLP Templates, RFC 2926, September 2000. 2031 [RFC3510] Herriot, R., and I. McDonald. Internet Printing Protocol 2032 1.1: IPP URL Scheme, RFC 3510, April 2003. 2034 [RFC3987] Duerst, M., and M. Suignard. Internationalized Resource 2035 Identifiers (IRI), RFC 3987, January 2005. 2037 [RFC3995] Herriot, R., and T. Hastings. Internet Printing Protocol 2038 (IPP): Event Notifications and Subscriptions, RFC 3995, March 2005. 2040 [RFC4122] Leach, P., Mealling, M., and R. Salz. A Universally Unique 2041 IDentifier (UUID) URN Namespace, RFC 4122, July 2005. 2043 [RFC4510] K. Zeilenga, Ed. Lightweight Directory Access Protocol 2044 (LDAP): Technical Specification Road Map, RFC 4510, June 2006. 2046 [RFC4513] R. Harrison, Ed. Lightweight Directory Access Protocol 2047 (LDAP): Authentication Methods and Security Mechanisms, RFC 4513, 2048 June 2006. 2050 [RFC4517] S. Legg, Ed. Lightweight Directory Access Protocol (LDAP): 2051 Syntaxes and Matching Rules, RFC 4517, June 2006. 2053 [RFC4519] A. Sciberras, Ed. Lightweight Directory Access Protocol 2054 (LDAP): Schema for User Applications, RFC 4519, June 2006. 2056 [RFC4524] K. Zeilenga, Ed. COSINE LDAP/X.500 Schema, RFC 4524, June 2057 2006. 2059 [RFC5198] Klensin, J., and M. Padlipsky. Unicode Format for Network 2060 Interchange, RFC 5198, March 2008. 2062 [RFC5246] Dierks, T., and E. Rescorla. The Transport Layer Security 2063 (TLS) Protocol Version 1.2, RFC 5246, August 2008. 2065 [RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S., 2066 Housley, R., and W. Polk. Internet X.509 Public Key Infrastructure 2067 Certificate and Certificate Revocation List (CRL) Profile, RFC 5280, 2068 May 2008. 2070 [RFC5870] Mayrhofer, A., and C. Spanring. A Uniform Resource 2071 Identifier for Geographic Locations ('geo' URI), RFC 5870, June 2010. 2073 [RFC6818] P. Yee. Updates to the Internet X.509 Public Key 2074 Infrastructure Certificate and Certificate Revocation List (CRL) 2075 Profile, RFC 6818, January 2013. 2077 [RFC7235] Fielding, R., and J. Reschke. Hypertext Transfer Protocol 2078 (HTTP/1.1): Authentication, RFC 7235, June 2014. 2080 [STD63] F. Yergeau. UTF-8, a Transformation Format of ISO 10646, STD 2081 63, RFC 3629, November 2003. 2083 [STD66] Berners-Lee, T., Fielding, R., and L. Masinter. Uniform 2084 Resource Identifier (URI): Generic Syntax, STD 66, RFC 3986, January 2085 2005. 2087 10.2. Informative References 2089 [BCP13] Freed, N., Klensin, J., and T. Hansen. Media Type 2090 Specifications and Registration Procedures, BCP 13, RFC 6838, January 2091 2013. 2093 [BCP18] H. Alvestrand. IETF Policy on Character Sets and Languages, 2094 BCP 18, RFC 2277, January 1998. 2096 [BCP19] Freed, N., and J. Postel. IANA Charset Registration 2097 Procedures, BCP 19, RFC 2978, October 2000. 2099 [BCP35] Hansen, T., Hardie, T., and L. Masinter. Guidelines and 2100 Registration Procedures for New URI Schemes, BCP 35, RFC 4395, 2101 February 2006. 2103 [IANASLP] Internet Assigned Numbers Authority (IANA) Registry 2104 "Service Location Protocol, Version 2 (SLPv2) Templates" 2105 2107 [PWG] IEEE-ISTO Printer Working Group (PWG) 2108 2110 [PWGIPP] IEEE-ISTO PWG Internet Printing Protocol Working Group 2111 2113 [RFC1179] L. McLaughlin. Line Printer Daemon Protocol, RFC 1179, 2114 August 1990. 2116 [RFC1951] P. Deutsch. DEFLATE Compressed Data Format Specification 2117 Version 1.3, RFC 1951, May 1996. 2119 [RFC1952] P. Deutsch. GZIP File Format Specification Version 4.3, 2120 RFC 1952, May 1996. 2122 [RFC1977] V. Schryver. PPP BSD Compression Protocol, RFC 1977, 2123 August 1996. 2125 [RFC2079] M. Smith. Definition of an X.500 Attribute Type and an 2126 Object Class to Hold Uniform Resource Identifiers (URIs), RFC 2079, 2127 January 1997. 2129 [RFC2566] deBry, R., Hastings, T., Herriot, R., Isaacson, S., and 2130 P. Powell. Internet Printing Protocol/1.0: Model and Semantics, RFC 2131 2566, April 1999. 2133 [RFC2608] Guttman, E., Perkins, C., Veizades, J., and M. Day. 2134 Service Location Protocol v2, RFC 2608, June 1999. 2136 [RFC2609] Guttman, E., Perkins, C., and J. Kempf. Service Templates 2137 and Service: Schemes, RFC 2609, June 1999. 2139 [RFC3712] Fleming, P., and I. McDonald. Lightweight Directory Access 2140 Protocol (LDAP): Schema for Printer Services, RFC 3712, February 2141 2004. 2143 [RFC4559] Jaganathan, K., Zhu, L., and J. Brezak. SPNEGO-based 2144 Kerberos and NTLM HTTP Authentication in Microsoft Windows, RFC 4559, 2145 June 2006. 2147 [SLPPRT20] St. Pierre, P., Isaacson, S., and I. McDonald. Definition 2148 of of the PrinterAbstract Service Type v2.0, May 2000. 2149 Reviewed and approved by IETF SLP Designated Expert, according to 2150 Section 5 'IANA Considerations' in [RFC2609]. 2151 Archived in [IANASLP] as "printer.2.0.en". 2153 11. Acknowledgments 2155 The editors wish to acknowledge significant contributions from Ken 2156 Jones and Harry Lewis and excellent comments from Patrik Faltstrom, 2157 Ryan Moats, Robert Moore, Lee Rafalow, Kimberly Reger, and Kurt 2158 Zeilenga during the development of the original LDAP Printer schema 2159 [RFC3712]. 2161 The editors wish to acknowledge excellent comments from Nevil 2162 Brownlee, Barry Leiba, Alexey Melnikov, Tom Petch, and Mike Sweet 2163 during the development of the current version of the LDAP Printer 2164 schema. 2166 Thanks to the members of the IEEE-ISTO PWG IPP Working Group, for 2167 their review comments and help in preparing this document. 2169 12. Appendix A - Changes since RFC 3712 2171 1) Added many editorial corrections and clarifications 2172 - corrected typos, missing words, and ambiguous sentences; 2173 - replaced lowercase 'printer' with titlecase 'Printer' for 2174 readability and consistency with IETF and IEEE-ISTO PWG IPP 2175 standards usage; 2176 - added implementation notes; 2177 - updated and added references. 2179 2) Deleted length restrictions from formal definitions of 2180 DirectoryString syntax attributes 2181 - replaced with notes recommending length restrictions for 2182 compatibility with existing implementations of [RFC3712] and 2183 underlying string length limits in [RFC2707], [RFC2911], 2184 [RFC3805], [PWG5107.2], [PWG5100.13], and [PWG5100.14]. 2186 3) Added new Printer attributes defined in [PWG5107.2], 2187 [PWG5100.13], and [PWG5100.14]. 2188 - see the table of Printer attributes and source documents in 2189 section 4 'Definition of Attribute Types' in this document; 2190 - added support for IEEE-ISTO PWG IPP Everywhere [PWG5100.14] 2191 project. 2193 4) Added implementation note to section 4 about string encodings 2194 - added discussion of 'List of xxx' and and 'One of xxx' 2195 encodings; 2196 - stated that any of these attributes can be represented as 2197 multiple instances (i.e., to avoid length overflow). 2199 5) Improved comma-delimited examples of string attributes 2200 - added both single-valued and multi-valued examples. 2202 6) Clarified use of printer-xri-supported attribute 2203 - added examples to show optional *trailing* whitespace after '<' 2204 delimiters. 2206 7) Clarified section 8 'Internationalization Considerations' 2207 - added note about Network Unicode [RFC5198] and avoiding use of 2208 C0 and C1 control characters. 2210 8) Clarified section 9 'Security Considerations' 2211 - added note about security vulnerabilities caused by use of DEL 2212 or any C0 or C1 control characters in names. 2214 9) Clarified terms and abbreviations 2215 - added 'Appendix B - Abbreviations' for acronyms. 2217 13. Appendix B - Abbreviations Used in this Document 2219 This document makes use of the following abbreviations (given with 2220 their expanded forms and references for further reading): 2222 IANA - Internet Assigned Numbers Authority 2223 2225 IEEE - Institute of Electrical and Electronics Engineers 2226 2228 IPP - Internet Printing Protocol [RFC2911] and [PWG5100.12] 2229 2231 ISTO - IEEE Industry Standards and Technology Organization 2232 2234 PWG - IEEE-ISTO Printer Working Group 2235 2237 RFC - Request for Comments 2238 2240 TLS - Transport Layer Security [RFC5246] 2242 URI - Uniform Resource Identifier [STD66] 2244 URL - Uniform Resource Locator [STD66] 2245 UTF-8 - Unicode Transformation Format - 8-bit [STD63] 2247 14. Appendix X - Change History 2249 [ [RFC Editor: This section to be deleted before RFC publication] ] 2251 29 January 2015 - draft-mcdonald-ldap-printer-schema-10.txt 2252 Editorial - Updated copyright year to 2015. 2253 Editorial - revised sections 4.1 printer-uri, 4.2 2254 printer-xri-supported, 4.7 printer-more-info, and 4.39 2255 printer-charge-info-uri to simply refer to [STD66] for details of URI 2256 syntax (and be silent about conflicting RFC 6874 for IPv6 addresses) 2257 per advice of Alexey Melnikov on 16 December 2014 and clarifications 2258 from Mike Sweet on 29 January 2015. 2259 Editorial - revised section 4.2 printer-xri-supported to clarify that 2260 the 'certificate' value refers to the IPP Client certificate 2261 extracted from the TLS session, per advice of Alexey Melnikov on 16 2262 December 2014. 2263 Editorial - revised section 4.3 printer-name to change "MAY" to "can" 2264 throughout the second Note paragraph, per advice of Alexey Melnikov 2265 on 16 December 2014. 2266 Editorial - revised section 4.13 2267 printer-generated-natural-language-supported to change example of 2268 from "fr-fr" to "fr-ca" (French as spoken in Canada) as a better 2269 illustration, per advice of Alexey Melnikov on 16 December 2014. 2270 Editorial - revised section 7 IANA Considerations to make clear which 2271 OIDs were already previously assigned by IBM and IANA-registered by 2272 RFC 3712, per advice of Nevil Brownlee on 18 December 2014. 2273 Editorial - revised section 12 Appendix A - Changes since RFC 3712 to 2274 delete erroneous change from Informational to Standards-Track. 2276 28 September 2014 - draft-mcdonald-ldap-printer-schema-09.txt 2277 Editorial - Changed "Intended Status" as "Informational", per advice 2278 of Barry Leiba on 18 August 2014. 2279 Editorial - Revised Abstract, Boilerplate, and Introduction to state 2280 that this document is an Independent Submission to the RFC Editor 2281 Stream, per advice of Barry Leiba on 18 August 2014. 2283 3 July 2014 - draft-mcdonald-ldap-printer-schema-08.txt 2284 Working draft - for IEEE-ISTO PWG IPP Everywhere project 2285 Editorial - revised sections 4.2 and 10.1 to add [RFC7235] normative 2286 reference, update for [RFC2617], per PWG IPP WG review. 2287 Editorial - revised sections 4.2 and 10.1 to add [RFC6818] normative 2288 reference, update for [RFC5280], per PWG IPP WG review. 2289 Editorial - revised section 10.1 to update [PWG5101.1] normative 2290 reference to v2.0 (March 2013), per PWG IPP WG review. 2292 13 March 2014 - draft-mcdonald-ldap-printer-schema-07.txt 2293 Working draft - for IEEE-ISTO PWG IPP Everywhere project 2294 Global - updated publication and expiration dates in copyright, 2295 header, footer, and boilerplate. 2296 Editorial - revised sections 4, 4.2, and 4.24 to add implementation 2297 notes about different field delimiters in printer-xri-supported and 2298 printer-resolution-supported (for compatibility with SLP template), 2299 per PWG IPP WG. 2300 Editorial - revised appendix A 'Changes since RFC 3712' to correct 2301 typos and expand PWG IPP Everywhere reference, per PWG IPP WG. 2303 3 March 2014 - draft-mcdonald-ldap-printer-schema-06.txt 2304 Working draft - for IEEE-ISTO PWG IPP Everywhere project 2305 Global - updated publication and expiration dates in copyright, 2306 header, footer, and boilerplate. 2307 Global - replaced 'SHOULD not' w/ 'SHOULD NOT' for RFC 2911 2308 compliance, per Alexey Melnikov. 2309 Editorial - revised Abstract and section 1 Introduction to clarify 2310 that this document is an individual submission to the IETF by the IPP 2311 WG of the IEEE-ISTO PWG, per Tom Petch and IPP WG review. 2312 Editorial - revised Abstract and section 1 Introduction to clarify 2313 that this document obsoletes [RFC3712], per Alexey Melnikov. 2314 Editorial - added section 1.1 'Relationship to SLP Printer Service' 2315 and section 1.2 'Source of LDAP Printer Attributes' for clarity. 2316 Editorial - added section 1.3 'Sources of LDAP Printer Schema OIDs' 2317 to describe permanent delegation of "1.3.18.0.2.24.46" to the 2318 IEEE-ISTO PWG by IBM in October 2011, per Alexey Melnikov. 2319 Editorial - added section 1.4 'Rationale for Design Choices' for 2320 clarity. 2321 Editorial - revised sections 3.1, 3.4, 3.5, and 3.6 to delete 2322 erroneous SHOULD references to structural classes, per Alexey 2323 Melnikov. 2324 Editorial - revised section 4 to clarify reference to section 4 of 2325 [RFC4517] and forward reference to section 6 of LDAP Printer Schema, 2326 per Alexey Melnikov. 2327 Editorial - revised section 4 to add implementation note about 2328 compatibility with existing implementations of [RFC3712] and 2329 underlying string length limits in [RFC2707], [RFC2911], [RFC3805], 2330 [PWG5107.2], [PWG5100.13], and [PWG5100.14], per Alexey Melnikov. 2331 Editorial - revised section 4.4 to change SHOULD to MUST for 2332 conformance to [BCP47] for natural language tags, per Alexey 2333 Melnikov. 2334 Editorial - revised section 4.4 printer-natural-language-configured 2335 and section 4.13 printer-generated-natural-language-supported 2336 definitions to clarify that they refer to LDAP Printer in syntax 2337 DirectoryString (UTF-8), per Alexey Melnikov. 2338 Editorial - revised section 4.11 printer-charset-configured and 2339 section 4.12 printer-charset-supported definitions to clarify that 2340 they refer to IPP protocol values and that corresponding LDAP Printer 2341 attributes are always in syntax DirectoryString (UTF-8), per Alexey 2342 Melnikov. 2344 Editorial - revised section 4.20 printer-number-up-supported and 2345 section 4.35 printer-device-id definitions to add missing 2346 SINGLE-VALUE clause, per Alexey Melnikov. 2347 Editorial - revised section 4.35 printer-device-id to delete 2348 confusing and redundant note about ordering of key/value pairs within 2349 LDAP attribute values (since this is clearly explained in 2350 [PWG5107.2]), per Alexey Melnikov. 2351 Editorial - revised section 4 syntaxes of printer-uri, 2352 printer-xri-supported, printer-name, 2353 printer-natural-language-configured, printer-location, printer-info, 2354 printer-more-info, printer-make-and-model, 2355 printer-ipp-versions-supported, printer-charset-configured, 2356 printer-charset-supported, 2357 printer-generated-natural-language-supported, 2358 printer-document-format-supported, printer-compression-supported, 2359 printer-finishings-supported, printer-sides-supported, 2360 printer-media-supported, printer-media-local-supported, 2361 printer-resolution-supported, printer-current-operator, 2362 printer-service-person, printer-delivery-orientation-supported, 2363 printer-stacking-order-supported, printer-output-features-supported, 2364 printer-aliases, printer-device-id, printer-uuid, 2365 printer-charge-info, printer-charge-info-uri, printer-geo-location, 2366 printer-ipp-features-supported, to remove length restrictions in 2367 syntax and add textual notes instead about IPP compatibility (where 2368 applicable), per Alexey Melnikov. 2369 Editorial - added appendix A 'Changes since RFC 3712', per Alexey 2370 Melnikov. 2371 Editorial - added missing informative reference to [RFC3712]. 2373 19 September 2013 - draft-mcdonald-ldap-printer-schema-05.txt 2374 Working draft - for IEEE-ISTO PWG IPP Everywhere project 2375 Global - updated publication and expiration dates in copyright, 2376 header, footer, and boilerplate. 2377 Global - updated references, per IEEE-ISTO PWG IPP WG review. 2379 17 May 2013 - draft-mcdonald-ldap-printer-schema-04.txt 2380 Working draft - for IEEE-ISTO PWG IPP Everywhere project 2381 Global - updated publication and expiration dates in copyright, 2382 header, footer, and boilerplate. 2383 Global - added references to IPP Everywhere, per IEEE-ISTO PWG IPP WG 2384 review. 2385 Editorial - revised section 4.41 printer-ipp-features-supported to 2386 show 'ipp-everywhere' defined in PWG 5100.14, per IEEE-ISTO PWG IPP 2387 WG review. 2389 18 November 2012 - draft-mcdonald-ldap-printer-schema-03.txt 2390 Working draft - for IEEE-ISTO PWG IPP Everywhere project 2391 Global - updated publication and expiration dates in copyright, 2392 header, footer, and boilerplate. 2394 Global - updated contact info for Pat Fleming. 2395 Global - updated various references. 2396 Global - added references to IEEE-ISTO PWG and IEEE-ISTO PWG IPP WG, 2397 per IEEE-ISTO PWG IPP WG review. 2398 Global - deleted all references to PWG IPP Everywhere and values 2399 defined in that specification, per IEEE-ISTO PWG IPP WG review. 2400 Global - deleted 'printer-device-uuid' attribute, per IEEE-ISTO PWG 2401 IPP WG review. 2402 Global - revised all 'One of' attributes to add implementation note 2403 that multiple values are represented as multiple instances, per 2404 IEEE-ISTO PWG IPP WG review. 2405 Global - revised all 'List of' attributes to add implementation note 2406 that length overflow is handled by multiple instances, per IEEE-ISTO 2407 PWG IPP WG review. 2408 Global - revised many DESC clauses to correct truncation due to 2409 no-fill formatting, per IEEE-ISTO PWG IPP WG review. 2410 Editorial - revised section 4 Definition of Attribute Types to add 2411 implementation note recommending use of Network Unicode [RFC5198], 2412 recommending against the use of DEL or any C0 or C1 control 2413 characters (except HT, CR, and LF), and recommending against HT, CR, 2414 and LF in names (e.g., printer-name or printer-aliases), per 2415 IEEE-ISTO PWG IPP WG review. 2416 Editorial - revised section 4 Definition of Attribute Types to add 2417 implementation note contrasting 'List of xxx' and 'One of xxx' and 2418 stating that any of these attributes can be represented as multiple 2419 instances (i.e., to avoid length overflow), per IEEE-ISTO PWG IPP WG 2420 review. 2421 Global - revised all comma-delimited examples to include both single- 2422 and multi-valued examples, per IEEE-ISTO PWG IPP WG review. 2423 Editorial - revised section 4.2 printer-xri-supported text and 2424 examples to show optional *trailing* whitespace after '<' delimiters, 2425 per IEEE-ISTO PWG IPP WG review. 2426 Editorial - revised section 4.3 printer-name to break recommendations 2427 into separate implementation notes, per IEEE-ISTO PWG IPP WG review. 2428 Editorial - revised section 4.20 printer-number-up-supported to add 2429 note explaining that this differs from the corresponding IPP 2430 attribute and is mapped from the largest reported value in IPP, per 2431 IEEE-ISTO PWG IPP WG review. 2432 Editorial - revised section 4.22 printer-media-supported to separate 2433 examples of media sizes, types, and colors, per IEEE-ISTO PWG IPP WG 2434 review. 2435 Editorial - revised section 4.24 printer-resolution-supported text 2436 and examples to show optional *trailing* whitespace after '>' 2437 delimiters, per IEEE-ISTO PWG IPP WG review. 2438 Editorial - revised section 4.34 printer-aliases to add Network 2439 Unicode note like printer-name, per IEEE-ISTO PWG IPP WG review. 2440 Editorial - revised section 4.35 printer-device-id to explicitly list 2441 the required key/value pairs as in PWG IPP Everywhere, per IEEE-ISTO 2442 PWG IPP WG review. 2443 Editorial - revised section 4.37 printer-uuid to add example of a 2444 valid UUID per [RFC4122], per IEEE-ISTO PWG IPP WG review. 2446 Editorial - revised section 4.36 printer-device-service-count to add 2447 example, per IEEE-ISTO PWG IPP WG review. 2448 Editorial - revised section 4.39 printer-charge-info-uri to add 2449 example, per IEEE-ISTO PWG IPP WG review. 2450 Editorial - revised section 4.40 printer-geo-location to add example 2451 of a value 'geo:' URI per [RFC5870], per IEEE-ISTO PWG IPP WG review. 2452 Editorial - revised section 4.41 printer-ipp-features-supported to 2453 delete 'ipp-everywhere' and add 'unknown' (with explanation), per 2454 IEEE-ISTO PWG IPP WG review. 2455 Editorial - revised section 7 IANA Considerations to correct 2456 truncation of some OIDs, per IEEE-ISTO PWG IPP WG review. 2457 Editorial - revised section 7.2 Registration of Attribute Types to 2458 delete issue for OID assignments, per IEEE-ISTO PWG IPP WG review. 2459 Editorial - revised section 8 Internationalization Considerations to 2460 add detailed note about Network Unicode [RFC5198] and avoiding use of 2461 C0 and C1 control characters, per IEEE-ISTO PWG IPP WG review. 2462 Editorial - revised section 9 Security Considerations to add note 2463 about security vulnerabilities caused by use of DEL or any C0 or C1 2464 control characters in names, per IEEE-ISTO PWG IPP WG review. 2465 Editorial - added appendix B Abbreviations, per IEEE-ISTO PWG IPP WG 2466 review. 2468 20 May 2012 - draft-mcdonald-ldap-printer-schema-02.txt 2469 Working draft - for IEEE-ISTO PWG IPP Everywhere project 2470 Cover - changed intended category to Standards Track for consistency 2471 w/ recent LDAP schema specs and IPP Everywhere recommendations. 2472 Global - replace 'must' w/ 'MUST', 'should' w/ 'SHOULD', and 'may' w/ 2473 'can' or 'MAY' (as appropriate) for Standards Track document. 2474 Global - updated publication and expiration dates in copyright, 2475 header, footer, and boilerplate. 2476 Global - replaced [RFC1759] references (obsolete) w/ [RFC3805], per 2477 IEEE-ISTO PWG IPP WG review. 2478 Global - replaced lowercase 'printer' with titlecase 'Printer' for 2479 readability and consistency with IPP standards usage. 2480 Revised section 1, to correct format of reference to IPP JPS3, per 2481 IEEE-ISTO PWG IPP WG review. 2482 Revised section 3.5, section 4.1, and section 4.2 to add references 2483 to IPP and IPPS URI scheme specs, per IEEE-ISTO PWG IPP WG review. 2484 Revised section 4.2 to correct reference for 'digest' and add 2485 reference for 'certificate' to [RFC5280], per IEEE-ISTO PWG IPP WG 2486 review. 2487 Revised sections 4.5, 4.6, 4.8, 4.29, 4.30, and 4.36 to add note 2488 about use of Network Unicode [RFC5198] and prohibition against all C0 2489 and C1 control characters except HT, CR, and LF, per IEEE-ISTO PWG 2490 IPP WG review. 2491 Revised section 4.9 to enumerate all known IPP versions (noting that 2492 IPP/1.0 is OBSOLETE) and refer to IANA IPP Registry, per IEEE-ISTO 2493 PWG IPP WG review. 2494 Revised section 4.22 to replace legacy examples w/ examples of media 2495 size names, media types, and media colors defined in [PWG5101.1], per 2496 IEEE-ISTO PWG IPP WG review. 2498 Revised section 4.24 to delete obscure note about delimiter, per 2499 IEEE-ISTO PWG IPP WG review. 2500 Revised sections 4.25, 4.31, 4.32, and 4.33 to add note about use of 2501 'unknown' (out-of-band value) ONLY when the correspond IPP or Printer 2502 MIB attributes are not present (i.e., artifact of LDAP mapping), per 2503 IEEE-ISTO PWG IPP WG review. 2504 Revised section 4.39 to add exhaustive list of feature keywords from 2505 [PWG5100.JPS3] and [PWG5100.EVE], per IEEE-ISTO PWG IPP WG review. 2506 Added section 4.x 'printer-device-service-count' aligned w/ 2507 "device-service-count" in [PWG5100.JPS3], per IEEE-ISTO PWG IPP WG 2508 review. 2509 Added section 4.x 'printer-device-uuid' aligned w/ "device-uuid" in 2510 [PWG5100.JPS3], per IEEE-ISTO PWG IPP WG review. 2511 Revised sections 4.x to add length restrictions to unbounded strings 2512 (text, URI, and UUID) w/ maximum 255 octets (consistent w/ RFC 3712), 2513 verify attribute lengths (per source IPP attribute), and clarify 2514 "list of" (comma-delimited) versus "one of" (simple multi-valued) for 2515 all 'printer-xxx-supported' attributes, per IEEE-ISTO PWG IPP WG 2516 review. 2517 Revised section 7.2 to assign new OIDs for the LDAP Printer Schema 2518 new attributes, per IEEE-ISTO PWG IPP WG review. 2519 Revised section 10.1 to add BCP 14 to [RFC2119] definition, per 2520 IEEE-ISTO PWG IPP WG review. 2521 Revised section 10.1 and section 10.2 to move [RFC2617], [RFC3987], 2522 [RFC4122], [RFC5198], [RFC5246], [RFC5280], [RFC5870], [STD63] from 2523 informative to normative references, per IEEE-ISTO PWG IPP WG review. 2525 3 April 2012 - draft-mcdonald-ldap-printer-schema-01.txt 2526 Working draft - for IEEE-ISTO PWG IPP Everywhere project 2527 Global - changed [IPPEVE1] to [PWG5100.EVE] and [IPPJPS3] to 2528 [PWG5100.JPS3], per IEEE-ISTO PWG IPP WG review. 2529 Revised section 1.1, to add printer-charge-info-uri and printer-uuid 2530 to discussion of URI syntax, per IEEE-ISTO PWG IPP WG review. 2531 Revised section 1.2 and section 1.3, to add printer-device-id to 2532 discussions of equality and substring matching, per IEEE-ISTO PWG IPP 2533 WG review. 2534 Revised section 3.2, section 4, and section 7.2, to delete redundant 2535 printer-organization and printer-organizational-unit (already covered 2536 by 'O' and 'OU'), per IEEE-ISTO PWG IPP WG review. 2537 Revised section 3.2, section 4, and section 7.2, to add missing 2538 printer-charge-info, per IEEE-ISTO PWG IPP WG review. 2539 Revised section 3.5, section 4, and section 7.2, to rename 2540 printer-ipp-extensions-supported to printer-ipp-features-supported, 2541 per IEEE-ISTO PWG IPP WG review. 2542 Revised numerous section 4 subsections, to add references to 2543 [IANAIPP] or [RFC3805] as appropriate for enumerations and keywords, 2544 per IEEE-ISTO PWG IPP WG review. 2545 Revised section 4.2, to add 'negotiate' as value for 'auth' and 2546 references to [PWG5100.JPS3], [RFC4559], and [IANAIPP], per IEEE-ISTO 2547 PWG IPP WG review. 2549 Revised section 4.2, to use 'example.com' for all DNS names, per 2550 IEEE-ISTO PWG IPP WG review. 2551 Revised section 4.22 and section 4.23, to add normative reference to 2552 PWG Media Standardized Names [PWG5101.1], per IEEE-ISTO PWG IPP WG 2553 review. 2554 Revised section 4.24, to divide notes into two separate paragraphs, 2555 per IEEE-ISTO PWG IPP WG review. 2556 Revised section 4.31, section 4.32, and section 4.33, to change 2557 'Values ... include' to 'Values ... are' (i.e., closed set), per 2558 IEEE-ISTO PWG IPP WG review. 2559 Revised section 4.35 printer-device-id, to add warning about ordering 2560 of required key/value pairs (first) and truncation only at key/value 2561 pair boundaries for interoperability, per IEEE-ISTO PWG IPP WG 2562 review. 2563 Revised section 4, to add printer-charge-info from [PWG5100.JPS3], 2564 per IEEE-ISTO PWG IPP WG review. 2565 Revised section 4.38 printer-geo-location, to change 'should' to 2566 'must' for conformance to [RFC5870], per IEEE-ISTO PWG IPP WG review. 2567 Revised section 4.39, to change printer-ipp-extensions-supported to 2568 printer-ipp-features-supported per [PWG5100.JPS3] and add examples, 2569 per IEEE-ISTO PWG IPP WG review. 2570 Revised section 4 subsection printer-uuid, to change 'should' to 2571 'must' for conformance to [RFC4122], per IEEE-ISTO PWG IPP WG review. 2572 Revised section 10 References, to update out-of-date references. 2574 2 October 2011 - draft-mcdonald-ldap-printer-schema-00.txt 2575 Working draft - for IEEE-ISTO PWG IPP Everywhere project 2576 Revised document to add current I-D individual submission 2577 boilerplate. 2578 Revised Abstract and section 1 Introduction, to cite [PWG5107.2] and 2579 [PWG5100.JPS3] new attribute sources. 2580 Revised section 3.2 printerAbstract, to add new attributes from 2581 [PWG5107.2] and [IPPJPS3]. 2582 Revised section 3.5, to add new attributes from [IPPJPS3]. 2583 Revised section 4 Definition of Attribute Types, to add new 2584 attributes from [PWG5107.2] and [IPPJPS3] to table and later specific 2585 definitions. 2586 Revised section 7.2 Registration of Attribute Types, to add new 2587 attributes from [PWG5107.2] and [IPPJPS3] - new OIDs needed. 2588 Revised section 10 References, to update out-of-date references. 2590 15. Authors' Addresses 2592 Please send comments to the authors at the addresses listed below. 2594 Pat Fleming 2595 Independent 2596 51796 171 Ave 2597 Pine Island, MN 55963 2598 USA 2599 Phone: +1 507-356-8277 2600 Email: patfleminghtc@gmail.com 2602 Ira McDonald 2603 High North Inc 2604 221 Ridge Ave 2605 Grand Marais, MI 49839 2606 USA 2607 Phone: +1 906-494-2434 2608 Email: blueroofmusic@gmail.com