idnits 2.17.1 draft-ietf-ipp-ldap-printer-schema-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([SLPLDAP], [IPPMOD], [SLPPRT]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 343 has weird spacing: '...pported ipp-v...' == Line 353 has weird spacing: '...pported comp...' == Line 355 has weird spacing: '...e-color pages...' == Line 356 has weird spacing: '...pported fin...' == Line 361 has weird spacing: '...pported pri...' == (3 more instances...) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (27 April 2000) is 8765 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC 2617' is mentioned on line 431, but not defined ** Obsolete undefined reference: RFC 2617 (Obsoleted by RFC 7235, RFC 7615, RFC 7616, RFC 7617) -- Looks like a reference, but probably isn't: '3' on line 431 == Unused Reference: 'RFC 1179' is defined on line 946, but no explicit reference was found in the text == Unused Reference: 'RFC 2307' is defined on line 971, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'IPPMOD' -- Possible downref: Non-RFC (?) normative reference: ref. 'SLPPRT' -- Possible downref: Non-RFC (?) normative reference: ref. 'SLPLDAP' ** Downref: Normative reference to an Informational RFC: RFC 1179 ** Obsolete normative reference: RFC 1766 (Obsoleted by RFC 3066, RFC 3282) ** Obsolete normative reference: RFC 2246 (Obsoleted by RFC 4346) ** Obsolete normative reference: RFC 2251 (Obsoleted by RFC 4510, RFC 4511, RFC 4512, RFC 4513) ** Obsolete normative reference: RFC 2252 (Obsoleted by RFC 4510, RFC 4512, RFC 4517, RFC 4523) ** Obsolete normative reference: RFC 2279 (Obsoleted by RFC 3629) ** Downref: Normative reference to an Experimental RFC: RFC 2307 ** Obsolete normative reference: RFC 2396 (Obsoleted by RFC 3986) Summary: 13 errors (**), 0 flaws (~~), 11 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Printing Protocol Working Group Pat Fleming 2 INTERNET DRAFT IBM 3 Expires 27 October 2000 Ken Jones 4 Sun Microsystems 5 Harry Lewis 6 IBM 7 Ira McDonald 8 High North Inc 9 27 April 2000 11 Internet Printing Protocol (IPP): 12 LDAP Schema for Printer Services 13 15 Copyright (C) The Internet Society (2000). All Rights Reserved. 17 Status of This Memo 19 This document is an Internet-Draft and is in full conformance with 20 all provisions of Section 10 of RFC 2026. Internet-Drafts are 21 working documents of the Internet Engineering Task Force (IETF), its 22 areas, and its working groups. Note that other groups may also 23 distribute working documents as Internet-Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 Abstract 38 This document defines a common printer schema for use with LDAP 39 directories (a directory service supporting the Lightweight Directory 40 Access Protocol (LDAP)). Using this common printer schema enables 41 client applications to use LDAP to search for printers using 42 application or user specified search criteria. Searches are defined 43 based on the entry's type and attributes independent of the LDAP 44 directory being used. 46 This document describes the LDAP schema, object classes and 47 attributes, for printers and printer services. This document uses 48 the printer attributes defined in Appendix E. of [IPPMOD], the 49 'printer:' service template defined in [SLPPRT], and the mapping 50 between SLP service advertisements and LDAP descriptions of services 51 defined in [SLPLDAP] to define an LDAP printer schema. 53 The goal of this document is to define a consistent schema to be used 54 by printers and print servers. The LDAP printer schema described in 55 this document MAY be used in part or whole. 57 Table of Contents 58 1. Introduction ............................................... 4 59 2. Terminology ................................................ 4 60 3. Definition of Object Classes ............................... 5 61 3.1. slpServicePrinter ...................................... 6 62 3.2. printerAbstract ........................................ 6 63 3.3. printerService ......................................... 7 64 3.4. printerServiceAuxClass ................................. 7 65 3.5. printerIPP ............................................. 8 66 3.6. printerLPR ............................................. 8 67 4. Definition of Attribute Types .............................. 9 68 4.1. printer-uri ............................................ 10 69 4.2. printer-xri-supported .................................. 10 70 4.3. printer-name ........................................... 11 71 4.4. printer-natural-language-configured .................... 12 72 4.5. printer-location ....................................... 12 73 4.6. printer-info ........................................... 12 74 4.7. printer-more-info ...................................... 13 75 4.8. printer-make-and-model ................................. 13 76 4.9. printer-ipp-versions-supported ......................... 13 77 4.10. printer-multiple-document-jobs-supported .............. 14 78 4.11. printer-charset-configured ............................ 14 79 4.12. printer-charset-supported ............................. 14 80 4.13. printer-generated-natural-language-supported .......... 15 81 4.14. printer-document-format-supported ..................... 15 82 4.15. printer-color-supported ............................... 15 83 4.16. printer-compression-supported ......................... 15 84 4.17. printer-pages-per-minute .............................. 16 85 4.18. printer-pages-per-minute-color ........................ 16 86 4.19. printer-finishings-supported .......................... 16 87 4.20. printer-number-up-supported ........................... 17 88 4.21. printer-sides-supported ............................... 17 89 4.22. printer-media-supported ............................... 17 90 4.23. printer-media-local-supported ......................... 17 91 4.24. printer-resolution-supported .......................... 18 92 4.25. printer-print-quality-supported ....................... 18 93 4.26. printer-job-priority-supported ........................ 18 94 4.27. printer-copies-supported .............................. 19 95 4.28. printer-job-k-octets-supported ........................ 19 96 4.29. printer-current-operator .............................. 19 97 4.30. printer-service-person ................................ 20 98 4.31. printer-delivery-orientation-supported ................ 20 99 4.32. printer-stacking-order-supported ...................... 20 100 4.33. printer-output-features-supported ..................... 20 101 5. Definition of Syntaxes ..................................... 22 102 6. IANA Considerations ........................................ 22 103 7. Internationalization Considerations ........................ 22 104 8. Security Considerations .................................... 22 105 9. References ................................................. 22 106 10. Acknowledgments ........................................... 23 107 11. Author's Addresses ........................................ 24 108 12. Full Copyright Statement .................................. 25 109 1. Introduction 111 The use of directory services based on the Lightweight Directory 112 Access Protocol [RFC 2251] is becoming increasingly popular for 113 distributed services. To ensure interoperability between vendor 114 implementations it is crucial to standardize the schemas which 115 describe these services. 117 Under the auspices of the IETF IPP Working Group the IPP protocol is 118 being developed to bring a standards based printing solution to the 119 Internet. 121 Section 16 of [IPPMOD] describes a list of attributes which should be 122 included in a general directory schema describing IPP print services. 123 The syntax for each of these attributes is described in detail in 124 [IPPMOD] and [SLPPRT]. This document will take these attributes and 125 map them to LDAP attributes and object classes. 127 This document defines several object classes to provide LDAP 128 applications with multiple options in defining printer information 129 using LDAP schema. Classes are provided for defining directory 130 entries with common printer information and for extending existing 131 directory entries with SLP, IPP, and LPR specific information. 133 2. Terminology 135 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 136 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 137 document are to be interpreted as described in [RFC 2119]. 139 3. Definition of Object Classes 141 We define the following LDAP object classes for use with both generic 142 printer related information and services specific to SLP, IPP, and 143 LPR. 145 slpServicePrinter - auxiliary class for SLP registered printers 146 printerAbstract - abstract class for all printer classes 147 printerService - structural class for printers 148 printerServiceAuxClass - auxiliary class for printers 149 printerIPP - auxiliary class for IPP printers 150 printerLPR - auxiliary class for LPR printers 152 The following are some examples of how applications MAY choose to use 153 these classes when creating directory entries: 155 1) Use printerService for directory entries containing common printer 156 information. 158 2) Use both printerService and slpServicePrinter for directory 159 entries containing common printer information for SLP registered 160 printers. 162 3) Use printerService, printerLPR and printerIPP for directory 163 entries containing common printer information for printers that 164 support both LPR and IPP. 166 4) Use printerServiceAuxClass and object classes not defined by this 167 document for directory entries containing common printer information. 168 In this example, printerServiceAuxClass is used for extending other 169 structural classes defining printer information with common printer 170 information defined in this document. 172 Note that specifying the abstract object class printerAbstract is 173 OPTIONAL when using printerService or printerServiceAuxClass to 174 create directory entries per [RFC 2251]. 176 Refer to section 4 for definition of attribute types referenced by 177 these object classes. We use names instead of OIDs in MUST and MAY 178 for clarity. Some attribute names described in [IPPMOD] have been 179 prefixed with 'printer-' as recommended in [SLPPRT] and [SLPLDAP]. 181 For the object classes defined in this section, schema developers MAY 182 add to the list of MAY OIDs, but MUST NOT modify the list of MUST 183 OIDs and MUST NOT remove OIDs from the list of MAY OIDs. Schema 184 developers MAY derive additional classes from the abstract and 185 structural classes defined in this section. Note, an object class 186 definition SHOULD NOT be changed without having a new name and OID 187 assigned to it. 189 3.1. slpServicePrinter 191 This auxiliary class defines Service Location Protocol (SLP) specific 192 information. It MUST be used with a structural class such as 193 printerService. It MAY be used to create new or extend existing 194 directory entries with SLP 'service:printer' abstract service type 195 information as defined in [SLPPRT]. This object class is derived 196 from 'slpService', the parent class for all SLP services, defined in 197 [SLPLDAP]. 199 ( .8 200 NAME 'slpServicePrinter' 201 DESC 'Service Location Protocol (SLP) information.' 202 SUP slpService 203 AUXILIARY 204 ) 206 3.2. printerAbstract 208 This abstract class defines printer information. It is a base class 209 for deriving other printer related classes, such as, but not limited 210 to, classes defined in this document. It defines a common set of 211 printer attributes that are not specific to any one type of service, 212 protocol or operating system. 214 ( .9 215 NAME 'printerAbstract' 216 DESC 'Printer related information.' 217 ABSTRACT 218 SUP top 219 MAY ( printer-name $ 220 printer-natural-language-configured $ 221 printer-location $ printer-info $ printer-more-info $ 222 printer-make-and-model $ 223 printer-multiple-document-jobs-supported $ 224 printer-charset-configured $ printer-charset-supported $ 225 printer-generated-natural-language-supported $ 226 printer-document-format-supported $ printer-color-supported $ 227 printer-compression-supported $ printer-pages-per-minute $ 228 printer-pages-per-minute-color $ 229 printer-finishings-supported $ printer-number-up-supported $ 230 printer-sides-supported $ printer-media-supported $ 231 printer-media-local-supported $ 232 printer-resolution-supported $ 233 printer-print-quality-supported $ 234 printer-job-priority-supported $ printer-copies-supported $ 235 printer-job-k-octets-supported $ printer-current-operator $ 236 printer-service-person $ 237 printer-delivery-orientation-supported $ 238 printer-stacking-order-supported $ 239 printer-output-features-supported ) 240 ) 242 3.3. printerService 244 This structural class defines printer information. It is derived 245 from class printerAbstract and thus inherits common printer 246 attributes. This class can be used with or without auxiliary classes 247 to define printer information. Auxiliary classes can be used to 248 extend the common printer information with protocol, service or 249 operating system specific information. Note that when extending 250 other structural classes with auxiliary classes, printerService MUST 251 NOT be used. 253 LDAP applications SHOULD use printer-uri as the naming attribute. 254 That is, when using printerService, printer-uri SHOULD be used as the 255 attribute type of the directory entry's relative distinguished name 256 (RDN). printer-uri uniquely identifies each of the printer services 257 for a given printer. Note that if the printer service changes 258 domains, printer-uri must be updated with the new domain name. 260 ( .10 261 NAME 'printerService' 262 DESC 'Printer information.' 263 SUP printerAbstract 264 MAY ( printer-uri $ printer-xri-supported ) 265 STRUCTURAL 266 ) 268 3.4. printerServiceAuxClass 270 This auxiliary class defines printer information. It is derived from 271 class printerAbstract and thus inherits common printer attributes. 272 This class MUST be used with a structural class. 274 LDAP applications SHOULD use printer-uri as the naming attribute. 275 That is, when using printerService, printer-uri SHOULD be used as the 276 attribute type of the directory entry's relative distinguished name 277 (RDN). printer-uri uniquely identifies each of the printer services 278 for a given printer. Note that if the printer service changes 279 domains, printer-uri must be updated with the new domain name. 281 ( .11 282 NAME 'printerServiceAuxClass' 283 DESC 'Printer information.' 284 SUP printerAbstract 285 MAY ( printer-uri $ printer-xri-supported ) 286 AUXILIARY 287 ) 289 3.5. printerIPP 291 This auxiliary class defines Internet Printing Protocol (IPP) 292 information. It MUST be used with a structural class such as 293 printerService. It is used to extend structural classes with IPP 294 specific printer information. 296 ( .12 297 NAME 'printerIPP' 298 DESC 'Internet Printing Protocol (IPP) information.' 299 SUP top 300 AUXILIARY 301 MAY ( printer-ipp-versions-supported $ 302 printer-multiple-document-jobs-supported ) 303 ) 305 3.6. printerLPR 307 This auxiliary class defines LPR information. It MUST be used with a 308 structural class such as printerService. It is used to identify 309 directory entries that support LPR. 311 ( .13 312 NAME 'printerLPR' 313 DESC 'LPR information.' 314 SUP top 315 AUXILIARY 316 ) 318 4. Definition of Attribute Types 320 The following attribute types are referenced by the object classes 321 defined in section 3. 323 The following table is a summary of the attribute names referenced by 324 this document and their corresponding names from [IPPMOD]. Some 325 attribute names described in [IPPMOD] have been prefixed with 326 'printer-' as recommended in [SLPLDAP], to address the flat namespace 327 for LDAP identifiers. 329 LDAP & SLP Printer Schema IPP Model [IPPMOD] 330 ------------------------------ ------------------------------------- 331 printer-uri 332 printer-xri-supported 333 [IPP printer-uri-supported] 334 [IPP uri-authentication-supported] 335 [IPP uri-security-supported] 336 printer-name printer-name 337 printer-natural-language-configured 338 natural-language-configured 339 printer-location printer-location 340 printer-info printer-info 341 printer-more-info printer-more-info 342 printer-make-and-model printer-make-and-model 343 printer-ipp-versions-supported ipp-versions-supported 344 printer-multiple-document-jobs-supported 345 multiple-document-jobs-supported 346 printer-charset-configured charset-configured 347 printer-charset-supported charset-supported 348 printer-generated-natural-language-supported 349 generated-natural-language-supported 350 printer-document-format-supported 351 document-format-supported 352 printer-color-supported color-supported 353 printer-compression-supported compression-supported 354 printer-pages-per-minute pages-per-minute 355 printer-pages-per-minute-color pages-per-minute-color 356 printer-finishings-supported finishings-supported 357 printer-number-up-supported number-up-supported 358 printer-sides-supported sides-supported 359 printer-media-supported media-supported 360 printer-media-local-supported [site names from IPP media-supported] 361 printer-resolution-supported printer-resolution-supported 362 printer-print-quality-supported print-quality-supported 363 printer-job-priority-supported job-priority-supported 364 printer-copies-supported copies-supported 365 printer-job-k-octets-supported job-k-octets-supported 366 printer-current-operator 367 printer-service-person 368 printer-delivery-orientation-supported 369 printer-stacking-order-supported 370 printer-output-features-supported 372 In the following definitions, we use matching rule names instead of 373 OIDs for clarity. Note that if the printer information is not known, 374 the attribute value is not set (for optional attributes). In the 375 following definitions, referenced matching rules are defined in 376 section 8 of [RFC 2252]. 378 The following definitions reference syntax OIDs as defined in [RFC 379 2252], which are summarized below: 380 Syntax OID Syntax Description 381 ----------------------------- ------------------ 382 1.3.6.1.4.1.1466.115.121.1.7 Boolean 383 1.3.6.1.4.1.1466.115.121.1.15 Directory String (UTF-8 [RFC 2279]) 384 1.3.6.1.4.1.1466.115.121.1.27 Integer 386 4.1. printer-uri 388 Note, that for SLP registered printers, the LDAP printer-uri 389 attribute should set to the value of the registered URL of the 390 printer. 392 ( .1 393 NAME 'printer-uri' 394 DESC 'The URI supported by this printer.' 395 EQUALITY caseIgnoreMatch 396 ORDERING caseIgnoreOrderingMatch 397 SUBSTR caseIgnoreSubstringMatch 398 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 399 SINGLE-VALUE 400 ) 402 4.2. printer-xri-supported 404 A list of XRI (extended resource identifiers) supported by this 405 printer. Each value of this list consists of a URI (uniform resource 406 identifier) followed by optional authentication and security 407 metaparameters. The keywords for URI and their metaparameters are: 408 'uri' == IPP 'printer-uri-supported' value 409 'auth' == IPP 'uri-authentication-supported' value 410 'sec' == IPP 'uri-security-supported' value 411 Legal values of the 'auth' metaparameter include 412 'none' (no authentication for this URI) 413 'requesting-user-name' (from operation request) 414 'basic' (HTTP/1.1 Basic [RFC 2617]) 415 'digest' (HTTP/1.1 Basic, [RFC 2617]) 416 'certificate' (from certificate) 417 per IPP Model [3] (extensions MAY also be used). A missing 'auth' 418 metaparameter SHALL mean 'none'. Legal values of the 'sec' 419 metaparameter include 420 'none' (no security for this URI) 421 'ssl3' (Netscape SSL3) 422 'tls' (IETF TLS/1.0, [RFC 2246]) 423 per IPP Model [3] (extensions MAY also be used). A missing 'sec' 424 metaparameter SHALL mean 'none'. Each metaparameter of a list member 425 is delimited by '<'. For example: 426 'uri=ipp://foo.com< auth=digest< sec=tls<' 427 'uri=lpr://bar.com< auth=none< sec=none<' 428 Registrations MAY consolidate values for metaparameters, as in the 429 following example: 430 'uri=ipp://foo.com< auth=basic,digest< sec=tls,ssl3<' 432 ( .2 433 NAME 'printer-xri-supported' 434 DESC 'The unordered list of XRI (extended resource identifiers) 435 supported by this printer. Each member of the list consists of 436 a URI (uniform resource identifier) followed by optional 437 authentication and security metaparameters.' 438 EQUALITY caseIgnoreMatch 439 ORDERING caseIgnoreOrderingMatch 440 SUBSTR caseIgnoreSubstringMatch 441 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 442 ) 444 4.3. printer-name 446 The site-specific administrative name of this printer. This value of 447 this attribute SHOULD be in the language specified in 448 'printer-natural-language-configured' (although the printer's name 449 may be in any language). This name MAY be the last part of the 450 printer's URI or it MAY be completely unrelated. This name MAY 451 contain characters that are not allowed in a conventional URI (which 452 conforms to [RFC 2396]). 454 ( .3 455 NAME 'printer-name' 456 DESC 'The site-specific administrative name of this printer, more 457 end-user friendly than a URI.' 458 EQUALITY caseIgnoreMatch 459 ORDERING caseIgnoreOrderingMatch 460 SUBSTR caseIgnoreSubstringMatch 461 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 462 SINGLE-VALUE 463 ) 465 4.4. printer-natural-language-configured 467 ( .4 468 NAME 'printer-generated-natural-language-configured' 469 DESC 'The configured language in which error and status messages will 470 be generated (by default) by this printer. Also, a possible 471 language for printer string attributes set by operator, system 472 administrator, or manufacturer. Also, the (declared) language 473 of the "printer-name", "printer-location", "printer-info", and 474 "printer-make-and-model" attributes of this printer. For 475 example: "en-us" (US English) or "fr-fr" (French in France) 476 Legal values of language tags conform to [RFC 1766] "Tags for 477 the Identification of Languages".' 478 EQUALITY caseIgnoreMatch 479 ORDERING caseIgnoreOrderingMatch 480 SUBSTR caseIgnoreSubstringMatch 481 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 482 SINGLE-VALUE 483 ) 485 4.5. printer-location 487 ( .5 488 NAME 'printer-location' 489 DESC 'Identifies the location of the printer. This could include 490 things like: "in Room 123A", "second floor of building XYZ".' 491 EQUALITY caseIgnoreMatch 492 ORDERING caseIgnoreOrderingMatch 493 SUBSTR caseIgnoreSubstringMatch 494 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 495 SINGLE-VALUE 496 ) 498 4.6. printer-info 500 ( .6 501 NAME 'printer-info' 502 DESC 'Identifies the descriptive information about this printer. 503 This could include things like: "This printer can be used for 504 printing color transparencies for HR presentations", or "Out 505 of courtesy for others, please print only small (1-5 page) jobs 506 at this printer", or even "This printer is going away on July 507 1, 1997, please find a new printer".' 508 EQUALITY caseIgnoreMatch 509 ORDERING caseIgnoreOrderingMatch 510 SUBSTR caseIgnoreSubstringMatch 511 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 512 SINGLE-VALUE 513 ) 515 4.7. printer-more-info 517 ( .7 518 NAME 'printer-more-info' 519 DESC 'A URI used to obtain more information about this specific 520 printer. For example, this could be an HTTP type URI 521 referencing an HTML page accessible to a Web Browser. The 522 information obtained from this URI is intended for end user 523 consumption.' 524 EQUALITY caseIgnoreMatch 525 ORDERING caseIgnoreOrderingMatch 526 SUBSTR caseIgnoreSubstringMatch 527 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 528 SINGLE-VALUE 529 ) 531 4.8. printer-make-and-model 533 ( .8 534 NAME 'printer-make-and-model' 535 DESC 'Identifies the make and model of the device. The device 536 manufacturer may initially populate this attribute.' 537 EQUALITY caseIgnoreMatch 538 ORDERING caseIgnoreOrderingMatch 539 SUBSTR caseIgnoreSubstringMatch 540 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 541 SINGLE-VALUE 542 ) 544 4.9. printer-ipp-versions-supported 546 ( .9 547 NAME 'printer-ipp-versions-supported' 548 DESC 'Identifies the IPP protocol version(s) that this printer 549 supports, including major and minor versions, i.e., the version 550 numbers for which this Printer implementation meets the 551 conformance requirements.' 552 EQUALITY caseIgnoreMatch 553 ORDERING caseIgnoreOrderingMatch 554 SUBSTR caseIgnoreSubstringMatch 555 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 556 ) 558 4.10. printer-multiple-document-jobs-supported 560 ( .10 561 NAME 'printer-multiple-document-jobs-supported' 562 DESC 'Indicates whether or not the printer supports more than one 563 document per job, i.e., more than one Send-Document or 564 Send-Data operation with document data.' 565 EQUALITY booleanMatch 566 SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 567 SINGLE-VALUE 568 ) 570 4.11. printer-charset-configured 572 ( .11 573 NAME 'printer-charset-configured' 574 DESC 'The configured charset in which error and status messages will 575 be generated (by default) by this printer. Also, a possible 576 charset for printer string attributes set by operator, system 577 administrator, or manufacturer. For example: "utf-8" (ISO 578 10646/Unicode) or "iso-8859-1" (Latin1). Legal values are 579 defined by the IANA Registry of Coded Character Sets and the 580 "(preferred MIME name)" SHALL be used as the tag. For 581 coherence with IPP Model, charset tags in this attribute SHALL 582 be lowercase normalized. This attribute SHOULD be static (time 583 of registration) and SHOULD NOT be dynamically refreshed 584 (subsequently).' 585 EQUALITY caseIgnoreMatch 586 SUBSTR caseIgnoreSubstringMatch 587 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{63} 588 SINGLE-VALUE 589 ) 591 4.12. printer-charset-supported 593 ( .12 594 NAME 'printer-charset-supported' 595 DESC 'Identifies the set of charsets supported for attribute type 596 values of type Directory String for this directory entry. For 597 example: "utf-8" (ISO 10646/Unicode) or "iso-8859-1" (Latin1). 598 Legal values are defined by the IANA Registry of Coded 599 Character Sets and the preferred MIME name.' 600 EQUALITY caseIgnoreMatch 601 SUBSTR caseIgnoreSubstringMatch 602 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{63} 603 ) 605 4.13. printer-generated-natural-language-supported 607 ( .13 608 NAME 'printer-generated-natural-language-supported' 609 DESC 'Identifies the natural language(s) supported for this directory 610 entry. For example: "en-us" (US English) or "fr-fr" (French in 611 France). Legal values conform to [RFC 1766], Tags for the 612 Identification of Languages.' 613 EQUALITY caseIgnoreMatch 614 ORDERING caseIgnoreOrderingMatch 615 SUBSTR caseIgnoreSubstringMatch 616 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{63} 617 ) 619 4.14. printer-document-format-supported 621 ( .14 622 NAME 'printer-document-format-supported' 623 DESC 'The possible document formats in which data may be interpreted 624 and printed by this printer. Legal values are MIME types come 625 from the IANA Registry of Internet Media Types.' 626 EQUALITY caseIgnoreMatch 627 SUBSTR caseIgnoreSubstringMatch 628 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 629 ) 631 4.15. printer-color-supported 633 ( .15 634 NAME 'printer-color-supported' 635 DESC 'Indicates whether this printer is capable of any type of color 636 printing at all, including highlight color.' 637 EQUALITY booleanMatch 638 SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 639 SINGLE-VALUE 640 ) 642 4.16. printer-compression-supported 644 ( .16 645 NAME 'printer-compression-supported' 646 DESC 'Compression algorithms supported by this printer. For example: 647 "deflate, gzip". Legal values include; "none", "deflate" 648 (public domain ZIP), "gzip" (GNU ZIP), "compress" (UNIX).' 649 EQUALITY caseIgnoreMatch 650 SUBSTR caseIgnoreSubstringMatch 651 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{255} 652 ) 654 4.17. printer-pages-per-minute 656 ( .17 657 NAME 'printer-pages-per-minute' 658 DESC 'The nominal number of pages per minute which may be output by 659 this printer (e.g., a simplex or black-and-white printer). 660 This attribute is informative, NOT a service guarantee. 661 Typically, it is the value used in marketing literature to 662 describe this printer.' 663 EQUALITY integerMatch 664 ORDERING integerOrderingMatch 665 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 666 SINGLE-VALUE 667 ) 669 4.18. printer-pages-per-minute-color 671 ( .18 672 NAME 'printer-pages-per-minute-color' 673 DESC 'The nominal number of color pages per minute which may be 674 output by this printer (e.g., a simplex or color printer). 675 This attribute is informative, NOT a service guarantee. 676 Typically, it is the value used in marketing literature to 677 describe this printer.' 678 EQUALITY integerMatch 679 ORDERING integerOrderingMatch 680 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 681 SINGLE-VALUE 682 ) 684 4.19. printer-finishings-supported 686 ( .19 687 NAME 'printer-finishings-supported' 688 DESC 'The possible finishing operations supported by this printer. 689 Legal values include; "none", "staple", "punch", "cover", 690 "bind", "saddle-stitch", "edge-stitch", "staple-top-left", 691 "staple-bottom-left", "staple-top-right", 692 "staple-bottom-right", "edge-stitch-left", "edge-stitch-top", 693 "edge-stitch-right", "edge-stitch-bottom", "staple-dual-left", 694 "staple-dual-top", "staple-dual-right", "staple-dual-bottom".' 695 EQUALITY caseIgnoreMatch 696 SUBSTR caseIgnoreSubstringMatch 697 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{255} 698 ) 700 4.20. printer-number-up-supported 702 ( .20 703 NAME 'printer-number-up-supported' 704 DESC 'The possible numbers of print-stream pages to impose upon a 705 single side of an instance of a selected medium. Legal values 706 include; 1, 2, and 4. Implementations may support other 707 values.' 708 EQUALITY integerMatch 709 ORDERING integerOrderingMatch 710 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 711 ) 713 4.21. printer-sides-supported 715 ( .21 716 NAME 'printer-sides-supported' 717 DESC 'The number of impression sides (one or two) and the two-sided 718 impression rotations supported by this printer. Legal values 719 include; "one-sided", "two-sided-long-edge", 720 "two-sided-short-edge".' 721 EQUALITY caseIgnoreMatch 722 SUBSTR caseIgnoreSubstringMatch 723 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 724 ) 726 4.22. printer-media-supported 728 ( .22 729 NAME 'printer-media-supported' 730 DESC 'The standard names/types/sizes (and optional color suffixes) of 731 the media supported by this printer. For example: "iso-a4", 732 "envelope", or "na-letter-white". Legal values conform to ISO 733 10175, Document Printing Application (DPA), and any IANA 734 registered extensions.' 735 EQUALITY caseIgnoreMatch 736 SUBSTR caseIgnoreSubstringMatch 737 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{255} 738 ) 740 4.23. printer-media-local-supported 742 ( .23 743 NAME 'printer-media-local-supported' 744 DESC 'Site-specific names of media supported by this printer, in the 745 language in "printer-generated-natural-language-configured". 747 For example: "purchasing-form" (site-specific name) as opposed 748 to (in "printer-media-supported"): "na-letter" (standard 749 keyword from ISO 10175).' 750 EQUALITY caseIgnoreMatch 751 SUBSTR caseIgnoreSubstringMatch 752 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{255} 753 ) 755 4.24. printer-resolution-supported 757 ( .24 758 NAME 'printer-resolution-supported' 759 DESC 'List of resolutions supported for printing documents by this 760 printer. Each resolution value is a string with 3 fields: 761 1) Cross feed direction resolution (positive integer), 2) Feed 762 direction resolution (positive integer), 3) Resolution unit. 763 Legal values are "dpi" (dots per inch) and "dpcm" (dots per 764 centimeter). Each resolution field is delimited by ">". For 765 example: "300> 300> dpi>".' 766 EQUALITY caseIgnoreMatch 767 SUBSTR caseIgnoreSubstringMatch 768 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{255} 769 ) 771 4.25. printer-print-quality-supported 773 ( .25 774 NAME 'printer-print-quality-supported' 775 DESC 'List of print qualities supported for printing documents on 776 this printer. For example: "draft, normal". Legal values 777 include; "unknown", "draft", "normal", "high".' 778 EQUALITY caseIgnoreMatch 779 SUBSTR caseIgnoreSubstringMatch 780 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 781 ) 783 4.26. printer-job-priority-supported 785 ( .26 786 NAME 'printer-job-priority-supported' 787 DESC 'Indicates the number of job priority levels supported. An IPP 788 conformant printer which supports job priority must always 789 support a full range of priorities from "1" to "100" (to ensure 790 consistent behavior), therefore this attribute describes the 791 "granularity". Legal values of this attribute are from "1" to 792 "100".' 793 EQUALITY integerMatch 794 ORDERING integerOrderingMatch 795 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 796 SINGLE-VALUE 797 ) 799 4.27. printer-copies-supported 801 ( .27 802 NAME 'printer-copies-supported' 803 DESC 'The maximum number of copies of a document that may be printed 804 as a single job. A value of "0" indicates no maximum limit. A 805 value of "-1" indicates unknown.' 806 EQUALITY integerMatch 807 ORDERING integerOrderingMatch 808 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 809 SINGLE-VALUE 810 ) 812 4.28. printer-job-k-octets-supported 814 ( .28 815 NAME 'printer-job-k-octets-supported' 816 DESC 'The maximum size in kilobytes (1,024 octets actually) incoming 817 print job that this printer will accept. A value of "0" 818 indicates no maximum limit. A value of "-1" indicates 819 unknown.' 820 EQUALITY integerMatch 821 ORDERING integerOrderingMatch 822 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 823 SINGLE-VALUE 824 ) 826 4.29. printer-current-operator 828 ( .29 829 NAME 'printer-current-operator' 830 DESC 'The name of the current human operator responsible for 831 operating this printer. It is suggested that this string 832 include information that would enable other humans to reach the 833 operator, such as a phone number.' 834 EQUALITY caseIgnoreMatch 835 ORDERING caseIgnoreOrderingMatch 836 SUBSTR caseIgnoreSubstringMatch 837 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 838 SINGLE-VALUE 839 ) 841 4.30. printer-service-person 843 ( .30 844 NAME 'printer-service-person' 845 DESC 'The name of the current human service person responsible for 846 servicing this printer. It is suggested that this string 847 include information that would enable other humans to reach the 848 service person, such as a phone number.' 849 EQUALITY caseIgnoreMatch 850 ORDERING caseIgnoreOrderingMatch 851 SUBSTR caseIgnoreSubstringMatch 852 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 853 SINGLE-VALUE 854 ) 856 4.31. printer-delivery-orientation-supported 858 ( .31 859 NAME 'printer-delivery-orientation-supported' 860 DESC 'The possible delivery orientations of pages as they are printed 861 and ejected from this printer. Legal values include; 862 "unknown", "face-up", and "face-down".' 863 EQUALITY caseIgnoreMatch 864 SUBSTR caseIgnoreSubstringMatch 865 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 866 ) 868 4.32. printer-stacking-order-supported 870 ( .32 871 NAME 'printer-stacking-order-supported' 872 DESC 'The possible stacking order of pages as they are printed and 873 ejected from this printer. Legal values include; "unknown", 874 "first-to-last", "last-to-first".' 875 EQUALITY caseIgnoreMatch 876 SUBSTR caseIgnoreSubstringMatch 877 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 878 ) 880 4.33. printer-output-features-supported 882 ( .33 883 NAME 'printer-output-features-supported' 884 DESC 'The possible output features supported by this printer. Legal 885 values include; "unknown", "bursting", "decollating", 886 "page-collating", "offset-stacking".' 888 EQUALITY caseIgnoreMatch 889 SUBSTR caseIgnoreSubstringMatch 890 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 891 ) 893 5. Definition of Syntaxes 895 No new syntaxes are defined by this document. 897 6. IANA Considerations 899 There are no IANA registration considerations defined by this 900 document. 902 7. Internationalization Considerations 904 All text string attribute values in objects of the printerService 905 class MUST be encoded in UTF-8 [RFC 2279] characters, as required by 906 the syntax 'Directory String' [RFC 2252]. Also, a language tag for 907 all of the text string attributes in objects of the printerService 908 class SHOULD be supplied in 'printer-natural-language-configured'. 909 Therefore, all objects of the printerService class conform to "IETF 910 Policy on Character Sets and Languages" [RFC 2277]. 912 8. Security Considerations 914 As with any LDAP schema, it is important to protect specific entries 915 and attributes with the appropriate access control. It is 916 particularly important that only administrators can modify entries 917 defined in this schema. For additional considerations of deploying 918 printers in an IPP environment the reader is referred to section 8 of 919 [IPPMOD]. 921 By advertising the security methods for each supported printer URL 922 the printer may expose information useful to attackers. Suitable 923 security methods SHOULD be used to authenticate any service 924 advertisements. 926 Obtaining a reference to an object and storing it in the directory 927 may make a handle to the object available to a wider audience. This 928 may have security implications. 930 9. References 932 [IPPMOD] deBry, Hastings, Herriot, Isaacson, Powell. Internet 933 Printing Protocol/1.1: Model and Semantics, 934 , (work in progress), March 2000. 936 [SLPPRT] St. Pierre, Isaacson, McDonald. Definition of the Printer 937 Abstract Service Type v2.0, 938 , (work in progress), March 939 2000. 941 [SLPLDAP] Kempf, Moats, St. Pierre. Conversion of LDAP Schemas to 942 and from SLP Templates, 943 , (work in progress), 944 October 1999. 946 [RFC 1179] McLaughlin. Line Printer Daemon Protocol, RFC 1179, 947 August 1990. 949 [RFC 1766] Alvestrand. Tags for the Identification of Languages, RFC 950 1766. March 1995. 952 [RFC 2119] Bradner. Key words for use in RFCs to Indicate 953 Requirement Levels, RFC 2119, March 1997. 955 [RFC 2246] Dierks, Allen. TLS Protocol Version 1.0, RFC 2246, 956 January 1999. 958 [RFC 2251] Wahl, Howes, Kille. Lightweight Directory Access Protocol 959 (v3), RFC 2251, December 1997. 961 [RFC 2252] Wahl, Coulbeck, Howes, Kille. Lightweight Directory 962 Access Protocol (v3): Attribute Syntax Definitions, RFC 2252, 963 December 1997. 965 [RFC 2277] Alvestrand. IETF Policy on Character Sets and Languages, 966 RFC 2277, January 1998. 968 [RFC 2279] Yergeau. UTF-8, a Transformation Format of ISO 10646, RFC 969 2279, January 1998. 971 [RFC 2307] Howard. An Approach for Using LDAP as a Network 972 Information Service, RFC 2307, March 1998. 974 [RFC 2396] Berners-Lee, Fielding, Masinter. URI Generic Syntax, RFC 975 2396, August 1998. 977 10. Acknowledgments 979 This document is a submission to the IPP Working group. 981 Thanks to Kimberly Reger (IBM), Robert Moore (IBM) and Lee Rafalow 982 (IBM) for their review comments and help in preparing this document. 984 11. Author's Addresses 986 Pat Fleming 987 IBM 988 Highway 52 N. 989 Rochester, MN 55901 990 USA 991 Phone: 507-253-7583 992 EMail: flemingp@us.ibm.com 994 Ken Jones 995 Sun Microsystems Inc. 996 17 Network Circle 997 Menlo Park, CA 94025 998 USA 999 Phone: +1 650 786 4164 1000 EMail: kenjones@eng.sun.com 1002 Harry Lewis 1003 IBM 1004 6300 Diagonal Hwy 1005 Boulder, CO 80301 1006 USA 1007 Phone: 303-924-5337 1008 EMail: harryl@us.ibm.com 1010 Ira McDonald 1011 High North Inc 1012 221 Ridge Ave 1013 Grand Marais, MI 49839 1014 USA 1015 Phone: 906-494-2434 (or 2697) 1016 Email: imcdonald@sharplabs.com 1017 Email: imcdonal@sdsp.mc.xerox.com 1019 12. Full Copyright Statement 1021 Copyright (C) The Internet Society (2000). All Rights Reserved. 1023 This document and translations of it may be copied and furnished to 1024 others, and derivative works that comment on or otherwise explain it 1025 or assist in its implementation may be prepared, copied, published 1026 and distributed, in whole or in part, without restriction of any 1027 kind, provided that the above copyright notice and this paragraph are 1028 included on all such copies and derivative works. However, this 1029 document itself may not be modified in any way, such as by removing 1030 the copyright notice or references to the Internet Society or other 1031 Internet organizations, except as needed for the purpose of 1032 developing Internet standards in which case the procedures for 1033 copyrights defined in the Internet Standards process must be 1034 followed, or as required to translate it into languages other than 1035 English. 1037 The limited permissions granted above are perpetual and will not be 1038 revoked by the Internet Society or its successors or assigns. 1040 This document and the information contained herein is provided on an 1041 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1042 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1043 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1044 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1045 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."