1 2 3 4 5 6 7Network Working Group P. Fleming 8Request for Comments: 3712 IBM 9Category: Informational I. McDonald 10 High North 11 February 2004 12 13 14 Lightweight Directory Access Protocol (LDAP): 15 Schema for Printer Services 16 17Status of this Memo 18 19 This memo provides information for the Internet community. It does 20 not specify an Internet standard of any kind. Distribution of this 21 memo is unlimited. 22 23Copyright Notice 24 25 Copyright (C) The Internet Society (2004). All Rights Reserved. 26 27Abstract 28 29 This document defines a schema, object classes and attributes, for 30 printers and printer services, for use with directories that support 31 Lightweight Directory Access Protocol v3 (LDAP-TS). This document is 32 based on the printer attributes listed in Appendix E of Internet 33 Printing Protocol/1.1 (IPP) (RFC 2911). A few additional printer 34 attributes are based on definitions in the Printer MIB (RFC 1759). 35 36Table of Contents 37 38 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 39 1.1. Rationale for using DirectoryString Syntax . . . . . . . 3 40 1.2. Rationale for using caseIgnoreMatch. . . . . . . . . . . 4 41 1.3. Rationale for using caseIgnoreSubstringsMatch. . . . . . 5 42 2. Terminology and Conventions. . . . . . . . . . . . . . . . . . 5 43 3. Definition of Object Classes . . . . . . . . . . . . . . . . . 6 44 3.1. slpServicePrinter. . . . . . . . . . . . . . . . . . . . 6 45 3.2. printerAbstract. . . . . . . . . . . . . . . . . . . . . 7 46 3.3. printerService . . . . . . . . . . . . . . . . . . . . . 8 47 3.4. printerServiceAuxClass . . . . . . . . . . . . . . . . . 8 48 3.5. printerIPP . . . . . . . . . . . . . . . . . . . . . . . 8 49 3.6. printerLPR . . . . . . . . . . . . . . . . . . . . . . . 9 50 4. Definition of Attribute Types. . . . . . . . . . . . . . . . . 9 51 4.1. printer-uri. . . . . . . . . . . . . . . . . . . . . . . 11 52 4.2. printer-xri-supported. . . . . . . . . . . . . . . . . . 11 53 4.3. printer-name . . . . . . . . . . . . . . . . . . . . . . 13 54 4.4. printer-natural-language-configured. . . . . . . . . . . 13 55 56 57 58Fleming & McDonald Informational [Page 1] 59 60RFC 3712 LDAP Schema for Printer Services February 2004 61 62 63 4.5. printer-location . . . . . . . . . . . . . . . . . . . . 14 64 4.6. printer-info . . . . . . . . . . . . . . . . . . . . . . 14 65 4.7. printer-more-info. . . . . . . . . . . . . . . . . . . . 14 66 4.8. printer-make-and-model . . . . . . . . . . . . . . . . . 15 67 4.9. printer-ipp-versions-supported . . . . . . . . . . . . . 15 68 4.10. printer-multiple-document-jobs-supported . . . . . . . . 16 69 4.11. printer-charset-configured . . . . . . . . . . . . . . . 16 70 4.12. printer-charset-supported. . . . . . . . . . . . . . . . 16 71 4.13. printer-generated-natural-language-supported . . . . . . 17 72 4.14. printer-document-format-supported. . . . . . . . . . . . 17 73 4.15. printer-color-supported. . . . . . . . . . . . . . . . . 18 74 4.16. printer-compression-supported. . . . . . . . . . . . . . 18 75 4.17. printer-pages-per-minute . . . . . . . . . . . . . . . . 18 76 4.18. printer-pages-per-minute-color . . . . . . . . . . . . . 19 77 4.19. printer-finishings-supported . . . . . . . . . . . . . . 19 78 4.20. printer-number-up-supported. . . . . . . . . . . . . . . 19 79 4.21. printer-sides-supported. . . . . . . . . . . . . . . . . 20 80 4.22. printer-media-supported. . . . . . . . . . . . . . . . . 20 81 4.23. printer-media-local-supported. . . . . . . . . . . . . . 20 82 4.24. printer-resolution-supported . . . . . . . . . . . . . . 21 83 4.25. printer-print-quality-supported. . . . . . . . . . . . . 22 84 4.26. printer-job-priority-supported . . . . . . . . . . . . . 22 85 4.27. printer-copies-supported . . . . . . . . . . . . . . . . 22 86 4.28. printer-job-k-octets-supported . . . . . . . . . . . . . 23 87 4.29. printer-current-operator . . . . . . . . . . . . . . . . 23 88 4.30. printer-service-person . . . . . . . . . . . . . . . . . 24 89 4.31. printer-delivery-orientation-supported . . . . . . . . . 24 90 4.32. printer-stacking-order-supported . . . . . . . . . . . . 24 91 4.33. printer-output-features-supported. . . . . . . . . . . . 25 92 4.34. printer-aliases. . . . . . . . . . . . . . . . . . . . . 25 93 5. Definition of Syntaxes . . . . . . . . . . . . . . . . . . . . 26 94 6. Definition of Matching Rules . . . . . . . . . . . . . . . . . 26 95 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26 96 7.1. Registration of Object Classes . . . . . . . . . . . . . 26 97 7.2. Registration of Attribute Types. . . . . . . . . . . . . 27 98 8. Internationalization Considerations. . . . . . . . . . . . . . 28 99 9. Security Considerations. . . . . . . . . . . . . . . . . . . . 29 100 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29 101 10.1. Normative References . . . . . . . . . . . . . . . . . . 29 102 10.2. Informative References . . . . . . . . . . . . . . . . . 30 103 11. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . 32 104 12. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 32 105 13. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 33 106 107 108 109 110 111 112 113 114Fleming & McDonald Informational [Page 2] 115 116RFC 3712 LDAP Schema for Printer Services February 2004 117 118 1191. Introduction 120 121 This document defines several object classes to provide Lightweight 122 Directory Access Protocol v3 [LDAP-TS] applications with flexible 123 options in defining printer information using LDAP schema. Classes 124 are provided for defining directory entries with common printer 125 information as well as for extending existing directory entries with 126 SLPv2 [RFC2608], IPP/1.1 [RFC2911], and LPR [RFC1179] specific 127 information. 128 129 The schema defined in this document is based on the printer 130 attributes listed in Appendix E 'Generic Directory Schema' of 131 Internet Printing Protocol/1.1 (IPP) [RFC2911]. A few additional 132 printer attributes are based on definitions in the Printer MIB 133 [RFC1759]. 134 135 The schema defined in this document is technically aligned with the 136 stable IANA-registered 'service:printer:' v2.0 template [SLP-PRT], 137 for compatibility with already deployed Service Location Protocol 138 (SLPv2) [RFC2608] service advertising and discovery infrastructure. 139 The attribute syntaxes are technically aligned with the 140 'service:printer:' v2.0 template - therefore simpler types are 141 sometimes used (for example, 'DirectoryString' [RFC2252] rather than 142 'labeledURI' [RFC2079] for the 'printer-uri' attribute). 143 144 Please send comments directly to the authors at the addresses listed 145 in Section 13 "Authors' Addresses". 146 1471.1. Rationale for using DirectoryString Syntax 148 149 The attribute syntax 'DirectoryString' (UTF-8 [RFC2279]) defined in 150 [RFC2252] is specified for several groups of string attributes that 151 are defined in this document: 152 153 1) URI 154 - printer-uri, printer-xri-supported, printer-more-info 155 156 The UTF-8 encoding is forward compatible with any future 157 deployment of (UTF-8 based) IRI (Internationalized Resource 158 Identifiers) [W3C-IRI] currently being developed by the W3C 159 Internationalization Working Group. 160 161 2) Description 162 - printer-name, printer-location, printer-info, 163 printer-make-and-model 164 165 166 167 168 169 170Fleming & McDonald Informational [Page 3] 171 172RFC 3712 LDAP Schema for Printer Services February 2004 173 174 175 The UTF-8 encoding supports descriptions in any language, 176 conformant with the "IETF Policy on Character Sets and Languages" 177 [RFC2277]. 178 179 Note: The printer-natural-language-configured attribute contains 180 a language tag [RFC3066] for these description attributes (for 181 example, to support text-to-speech conversions). 182 183 3) Keyword 184 - printer-compression-supported, printer-finishings-supported, 185 printer-media-supported, printer-media-local-supported, 186 printer-print-quality-supported 187 188 The UTF-8 encoding is compatible with the current IPP/1.1 189 [RFC2911] definition of the equivalent attributes, most of which 190 have the IPP/1.1 union syntax 'keyword or name'. The keyword 191 attributes defined in this document are extensible by 192 site-specific or vendor-specific 'names' which behave like new 193 'keywords' 194 195 Note: In IPP/1.1, each value is strongly typed over-the-wire as 196 either 'keyword' or 'name'. This union selector is not preserved 197 in the definitions of these equivalent LDAP attributes. 198 1991.2. Rationale for using caseIgnoreMatch 200 201 The EQUALITY matching rule 'caseIgnoreMatch' defined in [RFC2252] is 202 specified for several groups of string attributes that are defined in 203 this document: 204 205 1) URI 206 207 These URI attributes specify EQUALITY matching with 208 'caseIgnoreMatch' (rather than with 'caseExactMatch') in order to 209 conform to the spirit of [RFC2396], which requires case 210 insensitive matching on the host part of a URI versus case 211 sensitive matching on the remainder of a URI. 212 213 These URI attributes follow existing practice of supporting case 214 insensitive equality matching for host names in the 215 associatedDomain attribute defined in [RFC1274]. 216 217 Either equality matching rule choice would be a compromise: 218 a) case sensitive whole URI matching may lead to false negative 219 matches and has been shown to be fragile (given deployed client 220 applications that 'pretty up' host names displayed and 221 transferred in URI); 222 223 224 225 226Fleming & McDonald Informational [Page 4] 227 228RFC 3712 LDAP Schema for Printer Services February 2004 229 230 231 b) case insensitive whole URI matching may lead to false positive 232 matches, although it is a dangerous practice to publish URI that 233 differ only by case (for example, in the path elements). 234 235 2) Description 236 237 Case insensitive equality matching is more user-friendly for 238 description attributes. 239 240 3) Keyword 241 242 Case insensitive equality matching is more user-friendly for 243 keyword attributes. 244 2451.3. Rationale for using caseIgnoreSubstringsMatch 246 247 The SUBSTR matching rule 'caseIgnoreSubstringsMatch' defined in 248 [RFC2252] is specified for several groups of string attributes that 249 are defined in this document: 250 251 1) URI 252 253 These URI attributes follow existing practice of supporting case 254 insensitive equality matching for host names in the 255 associatedDomain attribute defined in [RFC1274]. 256 257 2) Description 258 259 Support for case insensitive substring matching is more 260 user-friendly for description attributes. 261 262 3) Keyword 263 264 Support for case insensitive substring matching is more 265 user-friendly for keyword attributes. 266 2672. Terminology and Conventions 268 269 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 270 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 271 document are to be interpreted as described in BCP 14 [RFC2119]. 272 273 Schema definitions are provided using LDAPv3 [LDAP-TS] description 274 formats. Definitions provided here are formatted (line wrapped) for 275 readability. 276 277 278 279 280 281 282Fleming & McDonald Informational [Page 5] 283 284RFC 3712 LDAP Schema for Printer Services February 2004 285 286 2873. Definition of Object Classes 288 289 We define the following LDAP object classes for use with both generic 290 printer related information and services specific to SLPv2 [RFC2608], 291 IPP/1.1 [RFC2911], and LPR [RFC1179]. 292 293 slpServicePrinter - auxiliary class for SLP registered printers 294 printerAbstract - abstract class for all printer classes 295 printerService - structural class for printers 296 printerServiceAuxClass - auxiliary class for printers 297 printerIPP - auxiliary class for IPP printers 298 printerLPR - auxiliary class for LPR printers 299 300 The following are some examples of how applications may choose to use 301 these classes when creating directory entries: 302 303 1) Use printerService for directory entries containing common 304 printer information. 305 306 2) Use both printerService and slpServicePrinter for directory 307 entries containing common printer information for SLP registered 308 printers. 309 310 3) Use printerService, printerLPR and printerIPP for directory 311 entries containing common printer information for printers that 312 support both LPR and IPP. 313 314 4) Use printerServiceAuxClass and object classes not defined by this 315 document for directory entries containing common printer 316 information. In this example, printerServiceAuxClass is used for 317 extending other structural classes defining printer information 318 with common printer information defined in this document. 319 320 Refer to Section 4 for definition of attribute types referenced by 321 these object classes. We use attribute names instead of OIDs in 322 object class definitions for clarity. Some attribute names described 323 in [RFC2911] have been prefixed with 'printer-' as recommended in 324 [RFC2926] and [SLP-PRT]. 325 3263.1. slpServicePrinter 327 328 ( 1.3.18.0.2.6.254 329 NAME 'slpServicePrinter' 330 DESC 'Service Location Protocol (SLP) information.' 331 AUXILIARY 332 SUP slpService 333 ) 334 335 336 337 338Fleming & McDonald Informational [Page 6] 339 340RFC 3712 LDAP Schema for Printer Services February 2004 341 342 343 This auxiliary class defines Service Location Protocol (SLPv2) 344 [RFC2608] specific information. It should be used with a structural 345 class such as printerService. It may be used to create new or extend 346 existing directory entries with SLP 'service:printer' abstract 347 service type information as defined in [SLP-PRT]. This object class 348 is derived from 'slpService', the parent class for all SLP services, 349 defined in [RFC2926]. 350 3513.2. printerAbstract 352 353 ( 1.3.18.0.2.6.258 354 NAME 'printerAbstract' 355 DESC 'Printer related information.' 356 ABSTRACT 357 SUP top 358 MAY ( printer-name $ 359 printer-natural-language-configured $ 360 printer-location $ printer-info $ printer-more-info $ 361 printer-make-and-model $ 362 printer-multiple-document-jobs-supported $ 363 printer-charset-configured $ printer-charset-supported $ 364 printer-generated-natural-language-supported $ 365 printer-document-format-supported $ printer-color-supported $ 366 printer-compression-supported $ printer-pages-per-minute $ 367 printer-pages-per-minute-color $ 368 printer-finishings-supported $ printer-number-up-supported $ 369 printer-sides-supported $ printer-media-supported $ 370 printer-media-local-supported $ 371 printer-resolution-supported $ 372 printer-print-quality-supported $ 373 printer-job-priority-supported $ printer-copies-supported $ 374 printer-job-k-octets-supported $ printer-current-operator $ 375 printer-service-person $ 376 printer-delivery-orientation-supported $ 377 printer-stacking-order-supported $ 378 printer-output-features-supported ) 379 ) 380 381 This abstract class defines printer information. It is a base class 382 for deriving other printer related classes, such as, but not limited 383 to, classes defined in this document. It defines a common set of 384 printer attributes that are not specific to any one type of service, 385 protocol or operating system. 386 387 388 389 390 391 392 393 394Fleming & McDonald Informational [Page 7] 395 396RFC 3712 LDAP Schema for Printer Services February 2004 397 398 3993.3. printerService 400 401 ( 1.3.18.0.2.6.255 402 NAME 'printerService' 403 DESC 'Printer information.' 404 STRUCTURAL 405 SUP printerAbstract 406 MAY ( printer-uri $ printer-xri-supported ) 407 ) 408 409 This structural class defines printer information. It is derived 410 from class printerAbstract and thus inherits common printer 411 attributes. This class can be used with or without auxiliary classes 412 to define printer information. Auxiliary classes can be used to 413 extend the common printer information with protocol, service or 414 operating system specific information. 415 416 Note: When extending other structural classes with auxiliary 417 classes, printerService should not be used. 418 4193.4. printerServiceAuxClass 420 421 ( 1.3.18.0.2.6.257 422 NAME 'printerServiceAuxClass' 423 DESC 'Printer information.' 424 AUXILIARY 425 SUP printerAbstract 426 MAY ( printer-uri $ printer-xri-supported ) 427 ) 428 429 This auxiliary class defines printer information. It is derived from 430 class printerAbstract and thus inherits common printer attributes. 431 This class should be used with a structural class. 432 4333.5. printerIPP 434 435 ( 1.3.18.0.2.6.256 436 NAME 'printerIPP' 437 DESC 'Internet Printing Protocol (IPP) information.' 438 AUXILIARY 439 SUP top 440 MAY ( printer-ipp-versions-supported $ 441 printer-multiple-document-jobs-supported ) 442 ) 443 444 445 446 447 448 449 450Fleming & McDonald Informational [Page 8] 451 452RFC 3712 LDAP Schema for Printer Services February 2004 453 454 455 This auxiliary class defines Internet Printing Protocol (IPP/1.1) 456 [RFC2911] information. It should be used with a structural class 457 such as printerService. It is used to extend structural classes with 458 IPP specific printer information. 459 4603.6. printerLPR 461 462 ( 1.3.18.0.2.6.253 463 NAME 'printerLPR' 464 DESC 'LPR information.' 465 AUXILIARY 466 SUP top 467 MUST ( printer-name ) 468 MAY ( printer-aliases) 469 ) 470 471 This auxiliary class defines LPR [RFC1179] information. It should be 472 used with a structural class such as printerService. It is used to 473 identify directory entries that support LPR. 474 4754. Definition of Attribute Types 476 477 The following attribute types are referenced by the object classes 478 defined in Section 3. 479 480 The following attribute types reference syntax OIDs defined in 481 Section 6 of [RFC2252] (see Section 5 'Definition of Syntaxes' 482 below). 483 484 The following attribute types reference matching rule names (instead 485 of OIDs) for clarity (see Section 6 below). For optional attributes, 486 if the printer information is not known, the attribute value should 487 not be set. In the following definitions, referenced matching rules 488 are defined in Section 8 of [RFC2252] and/or Section 2 of [RFC3698] 489 (see Section 6 'Definition of Matching Rules' below). 490 491 The following table is a summary of the attribute names defined by 492 this document and their corresponding names from [RFC2911]. Some 493 attribute names described in [RFC2911] have been prefixed with 494 'printer-' as recommended in [RFC2926], to address the flat namespace 495 for LDAP identifiers. 496 497 498 499 500 501 502 503 504 505 506Fleming & McDonald Informational [Page 9] 507 508RFC 3712 LDAP Schema for Printer Services February 2004 509 510 511 LDAP & SLP Printer Schema IPP Model [RFC2911] 512 ------------------------------ ------------------------------------- 513 printer-uri 514 printer-xri-supported 515 [IPP printer-uri-supported] 516 [IPP uri-authentication-supported] 517 [IPP uri-security-supported] 518 printer-name printer-name 519 printer-natural-language-configured 520 natural-language-configured 521 printer-location printer-location 522 printer-info printer-info 523 printer-more-info printer-more-info 524 printer-make-and-model printer-make-and-model 525 printer-ipp-versions-supported ipp-versions-supported 526 printer-multiple-document-jobs-supported 527 multiple-document-jobs-supported 528 printer-charset-configured charset-configured 529 printer-charset-supported charset-supported 530 printer-generated-natural-language-supported 531 generated-natural-language-supported 532 printer-document-format-supported 533 document-format-supported 534 printer-color-supported color-supported 535 printer-compression-supported compression-supported 536 printer-pages-per-minute pages-per-minute 537 printer-pages-per-minute-color pages-per-minute-color 538 printer-finishings-supported finishings-supported 539 printer-number-up-supported number-up-supported 540 printer-sides-supported sides-supported 541 printer-media-supported media-supported 542 printer-media-local-supported [site names from IPP media-supported] 543 printer-resolution-supported printer-resolution-supported 544 printer-print-quality-supported print-quality-supported 545 printer-job-priority-supported job-priority-supported 546 printer-copies-supported copies-supported 547 printer-job-k-octets-supported job-k-octets-supported 548 printer-current-operator 549 printer-service-person 550 printer-delivery-orientation-supported 551 printer-stacking-order-supported 552 printer-output-features-supported 553 printer-aliases 554 555 556 557 558 559 560 561 562Fleming & McDonald Informational [Page 10] 563 564RFC 3712 LDAP Schema for Printer Services February 2004 565 566 5674.1. printer-uri 568 569 ( 1.3.18.0.2.4.1140 570 NAME 'printer-uri' 571 DESC 'A URI supported by this printer.' 572 EQUALITY caseIgnoreMatch 573 SUBSTR caseIgnoreSubstringsMatch 574 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 575 SINGLE-VALUE 576 ) 577 578 If the printer-xri-supported LDAP attribute is implemented, then this 579 printer-uri value should be listed in printer-xri-supported. 580 581 Values of URI should conform to [RFC2396], although URI schemes may 582 be defined which do not conform to [RFC2396] (see [RFC2717] and 583 [RFC2718]). 584 585 Note: LDAP application clients should not attempt to use malformed 586 URI values read from this attribute. LDAP administrative clients 587 should not write malformed URI values into this attribute. 588 589 Note: For SLP registered printers, the LDAP printer-uri attribute 590 should be set to the value of the SLP-registered URL of the printer, 591 for interworking with SLPv2 [RFC2608] service discovery. 592 593 Note: See Sections 1.1, 1.2, and 1.3 for rationale for design 594 choices. 595 5964.2. printer-xri-supported 597 598 ( 1.3.18.0.2.4.1107 599 NAME 'printer-xri-supported' 600 DESC 'The unordered list of XRI (extended resource identifiers) 601 supported by this printer.' 602 EQUALITY caseIgnoreMatch 603 SUBSTR caseIgnoreSubstringsMatch 604 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 605 ) 606 607 A list of XRI (extended resource identifiers) supported by this 608 printer. Each value of this list should consist of a URI (uniform 609 resource identifier) followed by (optional) authentication and 610 security fields. 611 612 Values of URI should conform to [RFC2396], although URI schemes may 613 be defined which do not conform to [RFC2396] (see [RFC2717] and 614 [RFC2718]). 615 616 617 618Fleming & McDonald Informational [Page 11] 619 620RFC 3712 LDAP Schema for Printer Services February 2004 621 622 623 Note: LDAP application clients should not attempt to use malformed 624 URI values read from this attribute. LDAP administrative clients 625 should not write malformed URI values into this attribute. 626 627 Note: This attribute is based on 'printer-uri-supported', 'uri- 628 authentication-supported', and `'uri-security-supported' (called the 629 'Three Musketeers' because they are parallel ordered attributes) 630 defined in IPP/1.1 [RFC2911]. This attribute unfolds those IPP/1.1 631 attributes and thus avoids the ordering (and same number of values) 632 constraints of the IPP/1.1 separate attributes. 633 634 Defined keywords for fields include: 635 636 'uri' (IPP 'printer-uri-supported') 637 'auth' (IPP 'uri-authentication-supported') 638 'sec' (IPP 'uri-security-supported') 639 640 A missing 'auth' field should be interpreted to mean 'none'. Per 641 IPP/1.1 [RFC2911], defined values of the 'auth' field include: 642 643 'none' (no authentication for this URI) 644 'requesting-user-name' (from operation request) 645 'basic' (HTTP/1.1 Basic [RFC2617]) 646 'digest' (HTTP/1.1 Basic, [RFC2617]) 647 'certificate' (from certificate) 648 649 A missing 'sec' field should be interpreted to mean 'none'. Per 650 IPP/1.1 [RFC2911], defined values of the 'sec' field include: 651 652 'none' (no security for this URI) 653 'ssl3' (Netscape SSL3) 654 'tls' (IETF TLS/1.0, [RFC2246]) 655 656 Each XRI field should be delimited by '<'. For example: 657 658 'uri=ipp://foo.com< auth=digest< sec=tls<' 659 'uri=lpr://bar.com< auth=none< sec=none<' 660 'uri=mailto:printer@foobar.com< auth=none< sec=none<' 661 662 Note: The syntax and delimiter for this attribute are aligned with 663 the equivalent attribute in the 'service:printer:' v2.0 template 664 [SLP-PRT]. Whitespace is permitted after (but not before) the 665 delimiter '<'. Note that this delimiter differs from printer- 666 resolution-supported. 667 668 Note: See Sections 1.1, 1.2, and 1.3 for rationale for design 669 choices. 670 671 672 673 674Fleming & McDonald Informational [Page 12] 675 676RFC 3712 LDAP Schema for Printer Services February 2004 677 678 6794.3. printer-name 680 681 ( 1.3.18.0.2.4.1135 682 NAME 'printer-name' 683 DESC 'The site-specific administrative name of this printer.' 684 EQUALITY caseIgnoreMatch 685 SUBSTR caseIgnoreSubstringsMatch 686 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 687 SINGLE-VALUE 688 ) 689 690 Values of this attribute should be specified in the language 691 specified in printer-natural-language-configured (for example, to 692 support text-to-speech conversions), although the printer's name may 693 be specified in any language. This name may be the last part of the 694 printer's URI or it may be completely unrelated. This name may 695 contain characters that are not allowed in a conventional URI (see 696 [RFC2396]). 697 6984.4. printer-natural-language-configured 699 700 ( 1.3.18.0.2.4.1119 701 NAME 'printer-natural-language-configured' 702 DESC 'The configured natural language in which error and status 703 messages will be generated (by default) by this printer.' 704 EQUALITY caseIgnoreMatch 705 SUBSTR caseIgnoreSubstringsMatch 706 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 707 SINGLE-VALUE 708 ) 709 710 Also, a possible natural language for printer string attributes set 711 by operator, system administrator, or manufacturer. Also, the 712 (declared) natural language of the printer-name, printer-location, 713 printer-info, and printer-make-and-model attributes of this printer. 714 715 Values of language tags should conform to "Tags for the 716 Identification of Languages" [RFC3066]. For example: 717 718 'en-us' (English as spoken in the US) 719 'fr-fr' (French as spoken in France) 720 721 For consistency with IPP/1.1 [RFC2911], language tags in this 722 attribute should be lowercase normalized. 723 724 725 726 727 728 729 730Fleming & McDonald Informational [Page 13] 731 732RFC 3712 LDAP Schema for Printer Services February 2004 733 734 7354.5. printer-location 736 737 ( 1.3.18.0.2.4.1136 738 NAME 'printer-location' 739 DESC 'The physical location of this printer.' 740 EQUALITY caseIgnoreMatch 741 SUBSTR caseIgnoreSubstringsMatch 742 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 743 SINGLE-VALUE 744 ) 745 746 For example: 747 748 'Room 123A' 749 'Second floor of building XYZ' 750 7514.6. printer-info 752 753 ( 1.3.18.0.2.4.1139 754 NAME 'printer-info' 755 DESC 'Descriptive information about this printer.' 756 EQUALITY caseIgnoreMatch 757 SUBSTR caseIgnoreSubstringsMatch 758 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 759 SINGLE-VALUE 760 ) 761 762 For example: 763 764 'This printer can be used for printing color transparencies for 765 HR presentations' 766 'Out of courtesy for others, please print only small (1-5 page) 767 jobs at this printer' 768 'This printer is going away on July 1, 1997, please find a new 769 printer' 770 7714.7. printer-more-info 772 773 ( 1.3.18.0.2.4.1134 774 NAME 'printer-more-info' 775 DESC 'A URI for more information about this specific printer.' 776 EQUALITY caseIgnoreMatch 777 SUBSTR caseIgnoreSubstringsMatch 778 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 779 SINGLE-VALUE 780 ) 781 782 783 784 785 786Fleming & McDonald Informational [Page 14] 787 788RFC 3712 LDAP Schema for Printer Services February 2004 789 790 791 For example, this could be an HTTP type URI referencing an HTML page 792 accessible to a Web Browser. The information obtained from this URI 793 is intended for end user consumption. 794 795 Values of URI should conform to [RFC2396], although URI schemes may 796 be defined which do not conform to [RFC2396] (see [RFC2717] and 797 [RFC2718]). 798 799 Note: LDAP application clients should not attempt to use malformed 800 URI values read from this attribute. LDAP administrative clients 801 should not write malformed URI values into this attribute. 802 803 Note: See Sections 1.1, 1.2, and 1.3 for rationale for design 804 choices. 805 8064.8. printer-make-and-model 807 808 ( 1.3.18.0.2.4.1138 809 NAME 'printer-make-and-model' 810 DESC 'Make and model of this printer.' 811 EQUALITY caseIgnoreMatch 812 SUBSTR caseIgnoreSubstringsMatch 813 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 814 SINGLE-VALUE 815 ) 816 817 Note: The printer manufacturer may initially populate this 818 attribute. 819 8204.9. printer-ipp-versions-supported 821 822 ( 1.3.18.0.2.4.1133 823 NAME 'printer-ipp-versions-supported' 824 DESC 'IPP protocol version(s) that this printer supports.' 825 EQUALITY caseIgnoreMatch 826 SUBSTR caseIgnoreSubstringsMatch 827 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 828 ) 829 830 The IPP protocol version(s) should include major and minor versions, 831 i.e., the exact version numbers for which this Printer implementation 832 meets the IPP version-specific conformance requirements. 833 834 835 836 837 838 839 840 841 842Fleming & McDonald Informational [Page 15] 843 844RFC 3712 LDAP Schema for Printer Services February 2004 845 846 8474.10. printer-multiple-document-jobs-supported 848 849 ( 1.3.18.0.2.4.1132 850 NAME 'printer-multiple-document-jobs-supported' 851 DESC 'Indicates whether or not this printer supports more than one 852 document per job.' 853 EQUALITY booleanMatch 854 SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 855 SINGLE-VALUE 856 ) 857 8584.11. printer-charset-configured 859 860 ( 1.3.18.0.2.4.1109 861 NAME 'printer-charset-configured' 862 DESC 'The configured charset in which error and status messages will 863 be generated (by default) by this printer.' 864 EQUALITY caseIgnoreMatch 865 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{63} 866 SINGLE-VALUE 867 ) 868 869 Also, a possible charset for printer string attributes set by 870 operator, system administrator, or manufacturer. For example: 871 872 'utf-8' (ISO 10646/Unicode in UTF-8 transform [RFC2279]) 873 'iso-8859-1' (Latin1) 874 875 Values of charset tags should be defined in the IANA Registry of 876 Coded Character Sets [IANA-CHAR] (see also [RFC2978]) and the 877 '(preferred MIME name)' should be used as the charset tag in this 878 attribute. 879 880 For consistency with IPP/1.1 [RFC2911], charset tags in this 881 attribute should be lowercase normalized. 882 8834.12. printer-charset-supported 884 885 ( 1.3.18.0.2.4.1131 886 NAME 'printer-charset-supported' 887 DESC 'Set of charsets supported for the attribute values of syntax 888 DirectoryString for this directory entry.' 889 EQUALITY caseIgnoreMatch 890 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{63} 891 ) 892 893 894 895 896 897 898Fleming & McDonald Informational [Page 16] 899 900RFC 3712 LDAP Schema for Printer Services February 2004 901 902 903 For example: 904 905 'utf-8' (ISO 10646/Unicode in UTF-8 transform [RFC2279]) 906 'iso-8859-1' (Latin1) 907 908 Values of charset tags should be defined in the IANA Registry of 909 Coded Character Sets [IANA-CHAR] (see also [RFC2978]) and the 910 '(preferred MIME name)' should be used as the charset tag in this 911 attribute. 912 913 For consistency with IPP/1.1 [RFC2911], charset tags in this 914 attribute should be lowercase normalized. 915 9164.13. printer-generated-natural-language-supported 917 918 ( 1.3.18.0.2.4.1137 919 NAME 'printer-generated-natural-language-supported' 920 DESC 'Natural language(s) supported for this directory entry.' 921 EQUALITY caseIgnoreMatch 922 SUBSTR caseIgnoreSubstringsMatch 923 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{63} 924 ) 925 926 Values of language tags should conform to "Tags for the 927 Identification of Languages" [RFC3066]. For example: 928 929 'en-us' (English as spoken in the US) 930 'fr-fr' (French as spoken in France) 931 932 For consistency with IPP/1.1 [RFC2911], language tags in this 933 attribute should be lowercase normalized. 934 9354.14. printer-document-format-supported 936 937 ( 1.3.18.0.2.4.1130 938 NAME 'printer-document-format-supported' 939 DESC 'The possible source document formats which may be interpreted 940 and printed by this printer.' 941 EQUALITY caseIgnoreMatch 942 SUBSTR caseIgnoreSubstringsMatch 943 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 944 ) 945 946 Values of document formats should be MIME media types defined in the 947 IANA Registry of MIME Media Types [IANA-MIME] (see also [RFC2048]). 948 949 950 951 952 953 954Fleming & McDonald Informational [Page 17] 955 956RFC 3712 LDAP Schema for Printer Services February 2004 957 958 9594.15. printer-color-supported 960 961 ( 1.3.18.0.2.4.1129 962 NAME 'printer-color-supported' 963 DESC 'Indicates whether this printer is capable of any type of color 964 printing at all, including highlight color.' 965 EQUALITY booleanMatch 966 SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 967 SINGLE-VALUE 968 ) 969 9704.16. printer-compression-supported 971 972 ( 1.3.18.0.2.4.1128 973 NAME 'printer-compression-supported' 974 DESC 'Compression algorithms supported by this printer.' 975 EQUALITY caseIgnoreMatch 976 SUBSTR caseIgnoreSubstringsMatch 977 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{255} 978 ) 979 980 Values defined in IPP/1.1 [RFC2911] include: 981 982 'none' (no compression is used) 983 'deflate' (public domain ZIP described in [RFC1951]) 984 'gzip' (GNU ZIP described in [RFC1952]) 985 'compress' (UNIX compression described in [RFC1977]) 986 9874.17. printer-pages-per-minute 988 989 ( 1.3.18.0.2.4.1127 990 NAME 'printer-pages-per-minute' 991 DESC 'The nominal number of pages per minute which may be output by 992 this printer.' 993 EQUALITY integerMatch 994 ORDERING integerOrderingMatch 995 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 996 SINGLE-VALUE 997 ) 998 999 This attribute is informative, not a service guarantee. Typically, 1000 it is the value used in marketing literature to describe this 1001 printer. For example, the value for a simplex or black-and-white 1002 print mode. 1003 1004 1005 1006 1007 1008 1009 1010Fleming & McDonald Informational [Page 18] 1011 1012RFC 3712 LDAP Schema for Printer Services February 2004 1013 1014 10154.18. printer-pages-per-minute-color 1016 1017 ( 1.3.18.0.2.4.1126 1018 NAME 'printer-pages-per-minute-color' 1019 DESC 'The nominal number of color pages per minute which may be 1020 output by this printer.' 1021 EQUALITY integerMatch 1022 ORDERING integerOrderingMatch 1023 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1024 SINGLE-VALUE 1025 ) 1026 1027 This attribute is informative, not a service guarantee. Typically, 1028 it is the value used in marketing literature to describe this 1029 printer. 1030 1031 10324.19. printer-finishings-supported 1033 1034 ( 1.3.18.0.2.4.1125 1035 NAME 'printer-finishings-supported' 1036 DESC 'The possible finishing operations supported by this printer.' 1037 EQUALITY caseIgnoreMatch 1038 SUBSTR caseIgnoreSubstringsMatch 1039 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{255} 1040 ) 1041 1042 Values defined in IPP/1.1 [RFC2911] include: 'none', 'staple', 1043 'punch', 'cover', 'bind', 'saddle-stitch', 'edge-stitch', 1044 'staple-top-left', 'staple-bottom-left', 'staple-top-right', 1045 'staple-bottom-right', 'edge-stitch-left', 'edge-stitch-top', 1046 'edge-stitch-right', 'edge-stitch-bottom', 'staple-dual-left', 1047 'staple-dual-top', 'staple-dual-right', 'staple-dual-bottom'. 1048 1049 Note: Implementations may support other values. 1050 10514.20. printer-number-up-supported 1052 1053 ( 1.3.18.0.2.4.1124 1054 NAME 'printer-number-up-supported' 1055 DESC 'The possible numbers of print-stream pages to impose upon a 1056 single side of an instance of a selected medium.' 1057 EQUALITY integerMatch 1058 ORDERING integerOrderingMatch 1059 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1060 ) 1061 1062 1063 1064 1065 1066Fleming & McDonald Informational [Page 19] 1067 1068RFC 3712 LDAP Schema for Printer Services February 2004 1069 1070 1071 Values defined in IPP/1.1 [RFC2911] include: '1', '2', and '4'. 1072 1073 Note: Implementations may support other values. 1074 10754.21. printer-sides-supported 1076 1077 ( 1.3.18.0.2.4.1123 1078 NAME 'printer-sides-supported' 1079 DESC 'The number of impression sides (one or two) and the two-sided 1080 impression rotations supported by this printer.' 1081 EQUALITY caseIgnoreMatch 1082 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 1083 ) 1084 1085 Values defined in IPP/1.1 [RFC2911] include: 'one-sided', 'two- 1086 sided-long-edge', 'two-sided-short-edge'.' 1087 10884.22. printer-media-supported 1089 1090 ( 1.3.18.0.2.4.1122 1091 NAME 'printer-media-supported' 1092 DESC 'The standard names/types/sizes (and optional color suffixes) of 1093 the media supported by this printer.' 1094 EQUALITY caseIgnoreMatch 1095 SUBSTR caseIgnoreSubstringsMatch 1096 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{255} 1097 ) 1098 1099 Values are defined in IPP/1.1 [RFC2911] or any IANA registered 1100 extensions. For example: 1101 1102 'iso-a4' 1103 'envelope' 1104 'na-letter-white' 1105 11064.23. printer-media-local-supported 1107 1108 ( 1.3.18.0.2.4.1117 1109 NAME 'printer-media-local-supported' 1110 DESC 'Site-specific names of media supported by this printer.' 1111 EQUALITY caseIgnoreMatch 1112 SUBSTR caseIgnoreSubstringsMatch 1113 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{255} 1114 ) 1115 1116 Values should be in the natural language specified by printer- 1117 natural-language-configured. 1118 1119 1120 1121 1122Fleming & McDonald Informational [Page 20] 1123 1124RFC 3712 LDAP Schema for Printer Services February 2004 1125 1126 1127 For example: 1128 1129 'purchasing-form' (site-specific name) 1130 1131 as opposed to 'na-letter' (standard keyword from IPP/1.1 [RFC2911]) 1132 in the printer-media-supported attribute. 1133 11344.24. printer-resolution-supported 1135 1136 ( 1.3.18.0.2.4.1121 1137 NAME 'printer-resolution-supported' 1138 DESC 'List of resolutions supported for printing documents by this 1139 printer.' 1140 EQUALITY caseIgnoreMatch 1141 SUBSTR caseIgnoreSubstringsMatch 1142 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{255} 1143 ) 1144 1145 Each resolution value should be a string containing 3 fields: 1146 1) Cross feed direction resolution (positive integer); 1147 2) Feed direction resolution (positive integer); 1148 3) Unit - 'dpi' (dots per inch) or 'dpcm' (dots per centimeter). 1149 1150 Each resolution field should be delimited by '>'. For example: 1151 1152 '300> 300> dpi>' 1153 '600> 600> dpi>' 1154 1155 Note: This attribute is based on 'printer-resolution-supported' 1156 defined in IPP/1.1 [RFC2911] (which has a binary complex encoding) 1157 derived from 'prtMarkerAddressabilityFeedDir', 1158 'prtMarkerAddressabilityXFeedDir', and 'prtMarkerAddressabilityUnit' 1159 defined in the Printer MIB [RFC1759] (which have integer encodings). 1160 1161 Note: The syntax and delimiter for this attribute are aligned with 1162 the equivalent attribute in the 'service:printer:' v2.0 template 1163 [SLP-PRT]. Whitespace is permitted after (but not before) the 1164 delimiter '>'. Note that this delimiter differs from printer-xri- 1165 supported. 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178Fleming & McDonald Informational [Page 21] 1179 1180RFC 3712 LDAP Schema for Printer Services February 2004 1181 1182 11834.25. printer-print-quality-supported 1184 1185 ( 1.3.18.0.2.4.1120 1186 NAME 'printer-print-quality-supported' 1187 DESC 'List of print qualities supported for printing documents on 1188 this printer.' 1189 EQUALITY caseIgnoreMatch 1190 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 1191 ) 1192 1193 Values defined in IPP/1.1 [RFC2911] include: 1194 1195 'unknown' 1196 'draft' 1197 'normal' 1198 'high' 1199 12004.26. printer-job-priority-supported 1201 1202 ( 1.3.18.0.2.4.1110 1203 NAME 'printer-job-priority-supported' 1204 DESC 'Indicates the number of job priority levels supported by this 1205 printer.' 1206 EQUALITY integerMatch 1207 ORDERING integerOrderingMatch 1208 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1209 SINGLE-VALUE 1210 ) 1211 1212 An IPP/1.1 [RFC2911] conformant Printer, which supports job priority, 1213 always supports a full range of priorities from '1' to '100' (to 1214 ensure consistent behavior), therefore this attribute describes the 1215 'granularity' of priority supported. Values of this attribute are 1216 from '1' to '100'. 1217 12184.27. printer-copies-supported 1219 1220 ( 1.3.18.0.2.4.1118 1221 NAME 'printer-copies-supported' 1222 DESC 'The maximum number of copies of a document that may be printed 1223 as a single job on this printer.' 1224 EQUALITY integerMatch 1225 ORDERING integerOrderingMatch 1226 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1227 SINGLE-VALUE 1228 ) 1229 1230 1231 1232 1233 1234Fleming & McDonald Informational [Page 22] 1235 1236RFC 3712 LDAP Schema for Printer Services February 2004 1237 1238 1239 A positive value indicates the maximum supported copies. A value of 1240 '0' indicates no maximum limit. A value of '-1' indicates 'unknown'. 1241 1242 Note: The syntax and values for this attribute are aligned with the 1243 equivalent attribute in the 'service:printer:' v2.0 template [SLP- 1244 PRT]. 1245 12464.28. printer-job-k-octets-supported 1247 1248 ( 1.3.18.0.2.4.1111 1249 NAME 'printer-job-k-octets-supported' 1250 DESC 'The maximum size in kilobytes (1,024 octets actually) incoming 1251 print job that this printer will accept.' 1252 EQUALITY integerMatch 1253 ORDERING integerOrderingMatch 1254 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1255 SINGLE-VALUE 1256 ) 1257 1258 A positive value indicates the maximum supported job size. A value 1259 of '0' indicates no maximum limit. A value of '-1' indicates 1260 'unknown'. 1261 1262 Note: The syntax and values for this attribute are aligned with the 1263 equivalent attribute in the 'service:printer:' v2.0 template [SLP- 1264 PRT]. 1265 12664.29. printer-current-operator 1267 1268 ( 1.3.18.0.2.4.1112 1269 NAME 'printer-current-operator' 1270 DESC 'The identity of the current human operator responsible for 1271 operating this printer.' 1272 EQUALITY caseIgnoreMatch 1273 SUBSTR caseIgnoreSubstringsMatch 1274 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 1275 SINGLE-VALUE 1276 ) 1277 1278 The value of this attribute should include information that would 1279 enable other humans to reach the operator, such as a telephone 1280 number. 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290Fleming & McDonald Informational [Page 23] 1291 1292RFC 3712 LDAP Schema for Printer Services February 2004 1293 1294 12954.30. printer-service-person 1296 1297 ( 1.3.18.0.2.4.1113 1298 NAME 'printer-service-person' 1299 DESC 'The identity of the current human service person responsible 1300 for servicing this printer.' 1301 EQUALITY caseIgnoreMatch 1302 SUBSTR caseIgnoreSubstringsMatch 1303 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 1304 SINGLE-VALUE 1305 ) 1306 1307 The value of this attribute should include information that would 1308 enable other humans to reach the service person, such as a telephone 1309 number. 1310 13114.31. printer-delivery-orientation-supported 1312 1313 ( 1.3.18.0.2.4.1114 1314 NAME 'printer-delivery-orientation-supported' 1315 DESC 'The possible delivery orientations of pages as they are printed 1316 and ejected from this printer.' 1317 EQUALITY caseIgnoreMatch 1318 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 1319 ) 1320 1321 Values defined include: 1322 1323 'unknown' 1324 'face-up' 1325 'face-down' 1326 1327 Note: The syntax and values for this attribute are aligned with the 1328 equivalent attribute in the 'service:printer:' v2.0 template [SLP- 1329 PRT]. 1330 13314.32. printer-stacking-order-supported 1332 1333 ( 1.3.18.0.2.4.1115 1334 NAME 'printer-stacking-order-supported' 1335 DESC 'The possible stacking order of pages as they are printed and 1336 ejected from this printer.' 1337 EQUALITY caseIgnoreMatch 1338 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 1339 ) 1340 1341 1342 1343 1344 1345 1346Fleming & McDonald Informational [Page 24] 1347 1348RFC 3712 LDAP Schema for Printer Services February 2004 1349 1350 1351 Values defined include: 1352 1353 'unknown' 1354 'first-to-last' 1355 'last-to-first' 1356 1357 Note: The syntax and values for this attribute are aligned with the 1358 equivalent attribute in the 'service:printer:' v2.0 template [SLP- 1359 PRT]. 1360 13614.33. printer-output-features-supported 1362 1363 ( 1.3.18.0.2.4.1116 1364 NAME 'printer-output-features-supported' 1365 DESC 'The possible output features supported by this printer.' 1366 EQUALITY caseIgnoreMatch 1367 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 1368 ) 1369 1370 Values defined include: 1371 1372 'unknown' 1373 'bursting' 1374 'decollating' 1375 'page-collating' 1376 'offset-stacking' 1377 1378 Note: The syntax and values for this attribute are aligned with the 1379 equivalent attribute in the 'service:printer:' v2.0 template [SLP- 1380 PRT]. 1381 1382 Note: Implementations may support other values. 1383 13844.34. printer-aliases 1385 1386 ( 1.3.18.0.2.4.1108 1387 NAME 'printer-aliases' 1388 DESC 'List of site-specific administrative names of this printer in 1389 addition to the value specified for printer-name.' 1390 EQUALITY caseIgnoreMatch 1391 SUBSTR caseIgnoreSubstringsMatch 1392 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 1393 ) 1394 1395 Values of this attribute should be specified in the language 1396 specified in printer-natural-language-configured (for example, to 1397 support text-to-speech conversions), although the printer's alias may 1398 be specified in any language. 1399 1400 1401 1402Fleming & McDonald Informational [Page 25] 1403 1404RFC 3712 LDAP Schema for Printer Services February 2004 1405 1406 14075. Definition of Syntaxes 1408 1409 No new attribute syntaxes are defined by this document. 1410 1411 The attribute types defined in Section 4 of this document reference 1412 syntax OIDs defined in Section 6 of [RFC2252], which are summarized 1413 below: 1414 1415 Syntax OID Syntax Description 1416 ------------------------------ ------------------ 1417 1.3.6.1.4.1.1466.115.121.1.7 Boolean 1418 1.3.6.1.4.1.1466.115.121.1.15 DirectoryString (UTF-8 [RFC2279]) 1419 1.3.6.1.4.1.1466.115.121.1.27 Integer 1420 14216. Definition of Matching Rules 1422 1423 No new matching rules are defined by this document. 1424 1425 The attribute types defined in Section 4 of this document reference 1426 matching rules defined in Section 8 of [RFC2252] and/or Section 2 of 1427 [RFC3698], which are summarized below: 1428 1429 Matching Rule OID Matching Rule Name Usage 1430 ------------------------------ ------------------ ----- 1431 2.5.13.13 booleanMatch EQUALITY 1432 2.5.13.2 caseIgnoreMatch EQUALITY 1433 2.5.13.14 integerMatch EQUALITY 1434 2.5.13.15 integerOrderingMatch ORDERING 1435 2.5.13.4 caseIgnoreSubstringsMatch SUBSTR 1436 14377. IANA Considerations 1438 1439 This document does not define any new syntaxes or matching rules. 1440 1441 This document does define the following Object Identifier 1442 Descriptors. They have been registered by the IANA: 1443 14447.1. Registration of Object Classes 1445 1446 Subject: Request for LDAP Descriptor Registration 1447 1448 Descriptor (short name): see table below 1449 1450 Object Identifier: see table below 1451 1452 Person & email address to contact for further information: see below 1453 1454 Usage: object class 1455 1456 1457 1458Fleming & McDonald Informational [Page 26] 1459 1460RFC 3712 LDAP Schema for Printer Services February 2004 1461 1462 1463 Specification: RFC3712 1464 1465 Author/Change Controller: 1466 1467 Pat Fleming 1468 IBM 1469 Highway 52 N 1470 Rochester, MN 55901 1471 USA 1472 Phone: +1 507-253-7583 1473 EMail: flemingp@us.ibm.com 1474 1475 Comments: 1476 1477 Object Class OID 1478 ------------------------------------ --------------------- 1479 slpServicePrinter 1.3.18.0.2.6.254 1480 printerAbstract 1.3.18.0.2.6.258 1481 printerService 1.3.18.0.2.6.255 1482 printerServiceAuxClass 1.3.18.0.2.6.257 1483 printerIPP 1.3.18.0.2.6.256 1484 printerLPR 1.3.18.0.2.6.253 1485 14867.2. Registration of Attribute Types 1487 1488 Subject: Request for LDAP Descriptor Registration 1489 1490 Descriptor (short name): see table below 1491 1492 Object Identifier: see table below 1493 1494 Person & email address to contact for further information: see below 1495 1496 Usage: attribute type 1497 1498 Specification: RFC3712 1499 1500 Author/Change Controller: 1501 1502 Pat Fleming 1503 IBM 1504 Highway 52 N 1505 Rochester, MN 55901 1506 USA 1507 Phone: +1 507-253-7583 1508 EMail: flemingp@us.ibm.com 1509 1510 1511 1512 1513 1514Fleming & McDonald Informational [Page 27] 1515 1516RFC 3712 LDAP Schema for Printer Services February 2004 1517 1518 1519 Comments: 1520 1521 Attribute Type OID 1522 ------------------------------------ --------------------- 1523 printer-uri 1.3.18.0.2.4.1140 1524 printer-xri-supported 1.3.18.0.2.4.1107 1525 printer-name 1.3.18.0.2.4.1135 1526 printer-natural-language-configured 1.3.18.0.2.4.1119 1527 printer-location 1.3.18.0.2.4.1136 1528 printer-info 1.3.18.0.2.4.1139 1529 printer-more-info 1.3.18.0.2.4.1134 1530 printer-make-and-model 1.3.18.0.2.4.1138 1531 printer-ipp-versions-supported 1.3.18.0.2.4.1133 1532 printer-multiple-document-jobs-supported 1.3.18.0.2.4.1132 1533 printer-charset-configured 1.3.18.0.2.4.1109 1534 printer-charset-supported 1.3.18.0.2.4.1131 1535 printer-generated-natural-language-supported 1.3.18.0.2.4.1137 1536 printer-document-format-supported 1.3.18.0.2.4.1130 1537 printer-color-supported 1.3.18.0.2.4.1129 1538 printer-compression-supported 1.3.18.0.2.4.1128 1539 printer-pages-per-minute 1.3.18.0.2.4.1127 1540 printer-pages-per-minute-color 1.3.18.0.2.4.1126 1541 printer-finishings-supported 1.3.18.0.2.4.1125 1542 printer-number-up-supported 1.3.18.0.2.4.1124 1543 printer-sides-supported 1.3.18.0.2.4.1123 1544 printer-media-supported 1.3.18.0.2.4.1122 1545 printer-media-local-supported 1.3.18.0.2.4.1117 1546 printer-resolution-supported 1.3.18.0.2.4.1121 1547 printer-print-quality-supported 1.3.18.0.2.4.1120 1548 printer-job-priority-supported 1.3.18.0.2.4.1110 1549 printer-copies-supported 1.3.18.0.2.4.1118 1550 printer-job-k-octets-supported 1.3.18.0.2.4.1111 1551 printer-current-operator 1.3.18.0.2.4.1112 1552 printer-service-person 1.3.18.0.2.4.1113 1553 printer-delivery-orientation-supported 1.3.18.0.2.4.1114 1554 printer-stacking-order-supported 1.3.18.0.2.4.1115 1555 printer-output-features-supported 1.3.18.0.2.4.1116 1556 printer-aliases 1.3.18.0.2.4.1108 1557 15588. Internationalization Considerations 1559 1560 All text string attributes defined in this document of syntax 1561 [RFC2279], as required by [RFC2252]. 1562 1563 A language tag [RFC3066] for all of the text string attributes 1564 defined in this document is contained in the printer-natural- 1565 language-configured attribute. 1566 1567 1568 1569 1570Fleming & McDonald Informational [Page 28] 1571 1572RFC 3712 LDAP Schema for Printer Services February 2004 1573 1574 1575 Therefore, all object classes defined in this document conform to the 1576 "IETF Policy on Character Sets and Languages" [RFC2277]. 1577 15789. Security Considerations 1579 1580 See [RFC2829] for detailed guidance on authentication methods for 1581 LDAP. See [RFC2830] for detailed guidance of using TLS/1.0 [RFC2246] 1582 to supply connection confidentiality and data integrity for LDAP 1583 sessions. 1584 1585 As with any LDAP schema, it is important to protect specific entries 1586 and attributes with the appropriate access control. It is 1587 particularly important that only administrators can modify entries 1588 defined in this LDAP printer schema. Otherwise, an LDAP client might 1589 be fooled into diverting print service requests from the original 1590 printer (or spooler) to a malicious intruder's host system, thus 1591 exposing the information in printed documents. 1592 1593 For additional security considerations of deploying printers in an 1594 IPP environment, see Section 8 of [RFC2911]. 1595 159610. References 1597 159810.1. Normative References 1599 1600 [IANA-CHAR] IANA Registry of Character Sets 1601 http://www.iana.org/assignments/charset-reg/... 1602 1603 [IANA-MIME] IANA Registry of MIME Media Types 1604 http://www.iana.org/assignments/media-types/... 1605 1606 [LDAP-TS] Hodges, J. and R. Morgan, "Lightweight Directory Access 1607 Protocol (v3): Technical Specification", RFC 3377, 1608 September 2002. 1609 1610 [RFC1274] Barker, P. and S. Kille, "The COSINE and Internet X.500 1611 Schema", RFC 1274, November 1991. 1612 1613 [RFC1759] Smith, R., Wright, F., Hastings, T., Zilles, S. and J. 1614 Gyllenskog, "Printer MIB", RFC 1759, March 1995. 1615 1616 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1617 Requirement Levels", BCP 14, RFC 2119, March 1997. 1618 1619 [RFC2252] Wahl, M., Coulbeck, T., Howes, T. and S. Kille, 1620 "Lightweight Directory Access Protocol (v3): Attribute 1621 Syntax Definitions", RFC 2252, December 1997. 1622 1623 1624 1625 1626Fleming & McDonald Informational [Page 29] 1627 1628RFC 3712 LDAP Schema for Printer Services February 2004 1629 1630 1631 [RFC2396] Berners-Lee. T., Fielding, R. and L. Masinter, "URI 1632 Generic Syntax", RFC 2396, August 1998. 1633 1634 [RFC2829] Wahl, M., Alvestrand, H., Hodges, J. and R. Morgan, 1635 "Authentication Methods for LDAP", RFC 2829, May 2000. 1636 1637 [RFC2830] Hodges, J., Morgan, R. and M. Wahl, "Lightweight 1638 Directory Access Protocol (v3): Extension for Transport 1639 Layer Security", RFC 2830, May 2000. 1640 1641 [RFC2911] Hastings, T., Ed.., Herrito, R., deBry, R., Isaacson, S. 1642 and P. Powell, "Internet Printing Protocol/1.1: Model and 1643 Semantics", RFC 2911, September 2000. 1644 1645 [RFC2926] Kempf, J., Moats, R. and P. St. Pierre, "Conversion of 1646 LDAP Schemas to and from SLP Templates", RFC 2926, 1647 September 2000. 1648 1649 [RFC3066] Alvestrand, H., "Tags for the Identification of 1650 Languages", BCP 47, RFC 3066, January 2001. 1651 1652 [RFC3698] Zeilenga, K., Ed., "Lightweight Directory Access Protocol 1653 (LDAP): Additional Matching Rules", RFC 3698, February 1654 2004. 1655 165610.2. Informative References 1657 1658 [IANA-SLPT] IANA Registry of SLP Templates 1659 http://www.iana.org/assignments/svrloc-templates/... 1660 1661 [RFC1179] McLaughlin, L., "Line Printer Daemon Protocol", RFC 1179, 1662 August 1990. 1663 1664 [RFC1951] Deutsch, P., "DEFLATE Compressed Data Format 1665 Specification Version 1.3", RFC 1951, May 1996. 1666 1667 [RFC1952] Deutsch, P., "GZIP File Format Specification Version 1668 4.3", RFC 1952, May 1996. 1669 1670 [RFC1977] Schryver, V., "PPP BSD Compression Protocol", RFC 1977, 1671 August 1996. 1672 1673 [RFC2048] Freed, N., Klensin, J. and J. Postel, "Multipurpose 1674 Internet Mail Extensions (MIME) Part Four: Registration 1675 Procedures", BCP 13, RFC 2048, November 1996. 1676 1677 1678 1679 1680 1681 1682Fleming & McDonald Informational [Page 30] 1683 1684RFC 3712 LDAP Schema for Printer Services February 2004 1685 1686 1687 [RFC2079] Smith, M., "Definition of an X.500 Attribute Type and an 1688 Object Class to Hold Uniform Resource Identifiers 1689 (URIs)", RFC 2079, January 1997. 1690 1691 [RFC2246] Dierks, T. and C. Allen, "TLS Protocol Version 1.0", RFC 1692 2246, January 1999. 1693 1694 [RFC2277] Alvestrand, H., "IETF Policy on Character Sets and 1695 Languages", RFC 2277, January 1998. 1696 1697 [RFC2279] Yergeau, F., "UTF-8, a Transformation Format of ISO 1698 10646", RFC 2279, January 1998. 1699 1700 [RFC2608] Guttman, E., Perkins, C., Veizades, J. and M. Day, 1701 "Service Location Protocol v2", RFC 2608, June 1999. 1702 1703 [RFC2609] Guttman, E., Perkins, C. and J. Kempf, "Service Templates 1704 and Service: Schemes", RFC 2609, June 1999. 1705 1706 [RFC2617] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, 1707 S., Leach, P., Luotonen, A. and L. Stewart, "HTTP 1708 Authentication: Basic and Digest Access Authentication", 1709 RFC 2617, June 1999. 1710 1711 [RFC2717] Petke, R. and I. King, "Registration Procedures for URL 1712 Scheme Names", RFC 2717, November 1999. 1713 1714 [RFC2718] Masinter, L., Alvestrand, H., Zigmond, D. and R. Petke, 1715 "Guidelines for new URL Schemes", BCP 19, RFC 2718, 1716 November 1999. 1717 1718 [RFC2978] Freed, N. and J.Postel, "IANA Charset Registration 1719 Procedures", RFC2978, October 2000. 1720 1721 [SLP-PRT] St. Pierre, Isaacson, McDonald. Definition of the 1722 Printer Abstract Service Type v2.0, <durable URL below>, 1723 May 2000. Reviewed and approved by IETF SLP Designated 1724 Expert, according to Section 5 'IANA Considerations' in 1725 [RFC2609]. 1726 1727 Archived in the IANA Registry of SLP Templates [IANA- 1728 SLPT] at: http://www.iana.org/assignments/svrloc- 1729 templates/printer.2.0.en 1730 1731 [W3C-IRI] Duerst, Suignard, "Internationalized Resource Identifiers 1732 (IRI), Work in Progress. 1733 1734 1735 1736 1737 1738Fleming & McDonald Informational [Page 31] 1739 1740RFC 3712 LDAP Schema for Printer Services February 2004 1741 1742 174311. Acknowledgments 1744 1745 The editors wish to acknowledge the very significant contributions of 1746 Ken Jones (Bytemobile) and Harry Lewis (IBM) during the development 1747 of this document. 1748 1749 Thanks to Patrik Faltstrom (Cisco), Ryan Moats (Lemur Networks), 1750 Robert Moore (IBM), Lee Rafalow (IBM), Kimberly Reger (IBM), Kurt 1751 Zeilenga (OpenLDAP), and the members of the IETF IPP Working Group, 1752 for review comments and help in preparing this document. 1753 175412. Authors' Addresses 1755 1756 Please send comments to the authors at the addresses listed below. 1757 1758 Pat Fleming 1759 IBM 1760 Highway 52 N 1761 Rochester, MN 55901 1762 USA 1763 1764 Phone: +1 507-253-7583 1765 EMail: flemingp@us.ibm.com 1766 1767 1768 Ira McDonald 1769 High North Inc 1770 221 Ridge Ave 1771 Grand Marais, MI 49839 1772 USA 1773 1774 Phone: +1 906-494-2434 1775 Email: imcdonald@sharplabs.com 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794Fleming & McDonald Informational [Page 32] 1795 1796RFC 3712 LDAP Schema for Printer Services February 2004 1797 1798 179913. Full Copyright Statement 1800 1801 Copyright (C) The Internet Society (2004). This document is subject 1802 to the rights, licenses and restrictions contained in BCP 78 and 1803 except as set forth therein, the authors retain all their rights. 1804 1805 This document and the information contained herein are provided on an 1806 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 1807 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE 1808 INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR 1809 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1810 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1811 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1812 1813Intellectual Property 1814 1815 The IETF takes no position regarding the validity or scope of any 1816 Intellectual Property Rights or other rights that might be claimed 1817 to pertain to the implementation or use of the technology 1818 described in this document or the extent to which any license 1819 under such rights might or might not be available; nor does it 1820 represent that it has made any independent effort to identify any 1821 such rights. Information on the procedures with respect to 1822 rights in RFC documents can be found in BCP 78 and BCP 79. 1823 1824 Copies of IPR disclosures made to the IETF Secretariat and any 1825 assurances of licenses to be made available, or the result of an 1826 attempt made to obtain a general license or permission for the use 1827 of such proprietary rights by implementers or users of this 1828 specification can be obtained from the IETF on-line IPR repository 1829 at http://www.ietf.org/ipr. 1830 1831 The IETF invites any interested party to bring to its attention 1832 any copyrights, patents or patent applications, or other 1833 proprietary rights that may cover technology that may be required 1834 to implement this standard. Please address the information to the 1835 IETF at ietf-ipr@ietf.org. 1836 1837Acknowledgement 1838 1839 Funding for the RFC Editor function is currently provided by the 1840 Internet Society. 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850Fleming & McDonald Informational [Page 33] 1851 1852