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