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