idnits 2.17.1 draft-fleming-ldap-printer-schema-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([RFC1179], [RFC2911]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 5 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 437 has weird spacing: '...pported ipp-v...' == Line 447 has weird spacing: '...pported comp...' == Line 449 has weird spacing: '...e-color pages...' == Line 450 has weird spacing: '...pported fin...' == Line 455 has weird spacing: '...pported pri...' == (2 more instances...) == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). == Unrecognized Status in '[Target Category: Informational]', assuming Proposed Standard (Expected one of 'Standards Track', 'Full Standard', 'Draft Standard', 'Proposed Standard', 'Best Current Practice', 'Informational', 'Experimental', 'Informational', 'Historic'.) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (30 June 2002) is 7971 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC1759' is mentioned on line 961, but not defined ** Obsolete undefined reference: RFC 1759 (Obsoleted by RFC 3805) == Missing Reference: 'ISO3066' is mentioned on line 157, but not defined -- Possible downref: Non-RFC (?) normative reference: ref. 'IANA-CHAR' -- Possible downref: Non-RFC (?) normative reference: ref. 'IANA-MIME' -- Possible downref: Non-RFC (?) normative reference: ref. 'LDAP-TS' -- Possible downref: Non-RFC (?) normative reference: ref. 'LDAP-USER' ** Obsolete normative reference: RFC 2252 (Obsoleted by RFC 4510, RFC 4512, RFC 4517, RFC 4523) ** Obsolete normative reference: RFC 2396 (Obsoleted by RFC 3986) ** Obsolete normative reference: RFC 2829 (Obsoleted by RFC 4510, RFC 4513) ** Obsolete normative reference: RFC 2830 (Obsoleted by RFC 4510, RFC 4511, RFC 4513) ** Obsolete normative reference: RFC 2911 (Obsoleted by RFC 8011) ** Downref: Normative reference to an Informational RFC: RFC 2926 ** Obsolete normative reference: RFC 3066 (Obsoleted by RFC 4646, RFC 4647) -- Obsolete informational reference (is this intentional?): RFC 2048 (Obsoleted by RFC 4288, RFC 4289) -- Obsolete informational reference (is this intentional?): RFC 2246 (Obsoleted by RFC 4346) -- Obsolete informational reference (is this intentional?): RFC 2279 (Obsoleted by RFC 3629) -- Obsolete informational reference (is this intentional?): RFC 2617 (Obsoleted by RFC 7235, RFC 7615, RFC 7616, RFC 7617) -- Obsolete informational reference (is this intentional?): RFC 2717 (Obsoleted by RFC 4395) -- Obsolete informational reference (is this intentional?): RFC 2718 (Obsoleted by RFC 4395) Summary: 13 errors (**), 0 flaws (~~), 12 warnings (==), 12 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET DRAFT Pat Fleming 3 IBM 4 [Target Category: Informational] Ira McDonald 5 Expires 30 December 2002 High North 6 30 June 2002 8 Lightweight Directory Access Protocol (LDAP): 9 Schema for Printer Services 10 12 Copyright (C) The Internet Society (2002). All Rights Reserved. 14 Status of This Memo 16 This document is an Internet-Draft and is in full conformance with 17 all provisions of Section 10 of RFC 2026. Internet-Drafts are 18 working documents of the Internet Engineering Task Force (IETF), its 19 areas, and its working groups. Note that other groups may also 20 distribute working documents as Internet-Drafts. 22 This document is an individual submission and is not the product of 23 an IETF working group. This document is intended to be, after 24 appropriate review and revision, submitted to the RFC Editor as an 25 Informational RFC. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 To view the list of Internet-Draft Shadow Directories, see 33 http://www.ietf.org/shadow.html. 35 Abstract 37 This document defines a schema, object classes and attributes, for 38 printers and printer services, for use with directories that support 39 Lightweight Directory Access Protocol v3 (LDAP-TS). This document is 40 based on the printer attributes listed in Appendix E of Internet 41 Printing Protocol/1.1 (IPP) (RFC 2911). A few additional printer 42 attributes are based on definitions in the Printer MIB (RFC 1759). 44 Table of Contents 46 1. Introduction ............................................... 4 47 1.1. Rationale for using DirectoryString Syntax ............. 4 48 1.2. Rationale for using caseIgnoreMatch .................... 5 49 1.3. Rationale for using caseIgnoreSubstringsMatch .......... 6 50 2. Terminology and Conventions ................................ 6 51 3. Definition of Object Classes ............................... 7 52 3.1. slpServicePrinter ...................................... 8 53 3.2. printerAbstract ........................................ 8 54 3.3. printerService ......................................... 9 55 3.4. printerServiceAuxClass ................................. 9 56 3.5. printerIPP ............................................. 9 57 3.6. printerLPR ............................................. 10 58 4. Definition of Attribute Types .............................. 11 59 4.1. printer-uri ............................................ 13 60 4.2. printer-xri-supported .................................. 13 61 4.3. printer-name ........................................... 15 62 4.4. printer-natural-language-configured .................... 15 63 4.5. printer-location ....................................... 16 64 4.6. printer-info ........................................... 16 65 4.7. printer-more-info ...................................... 16 66 4.8. printer-make-and-model ................................. 17 67 4.9. printer-ipp-versions-supported ......................... 17 68 4.10. printer-multiple-document-jobs-supported .............. 18 69 4.11. printer-charset-configured ............................ 18 70 4.12. printer-charset-supported ............................. 18 71 4.13. printer-generated-natural-language-supported .......... 19 72 4.14. printer-document-format-supported ..................... 19 73 4.15. printer-color-supported ............................... 20 74 4.16. printer-compression-supported ......................... 20 75 4.17. printer-pages-per-minute .............................. 20 76 4.18. printer-pages-per-minute-color ........................ 21 77 4.19. printer-finishings-supported .......................... 21 78 4.20. printer-number-up-supported ........................... 21 79 4.21. printer-sides-supported ............................... 22 80 4.22. printer-media-supported ............................... 22 81 4.23. printer-media-local-supported ......................... 22 82 4.24. printer-resolution-supported .......................... 23 83 4.25. printer-print-quality-supported ....................... 24 84 4.26. printer-job-priority-supported ........................ 24 85 4.27. printer-copies-supported .............................. 24 86 4.28. printer-job-k-octets-supported ........................ 25 87 4.29. printer-current-operator .............................. 25 88 4.30. printer-service-person ................................ 26 89 4.31. printer-delivery-orientation-supported ................ 26 90 4.32. printer-stacking-order-supported ...................... 26 91 4.33. printer-output-features-supported ..................... 27 92 4.34. printer-aliases ....................................... 27 93 5. Definition of Syntaxes ..................................... 29 94 6. Definition of Matching Rules ............................... 29 95 7. IANA Considerations ........................................ 30 96 7.1. Registration of Object Classes ......................... 30 97 7.2. Registration of Attribute Types ........................ 31 98 8. Internationalization Considerations ........................ 33 99 9. Security Considerations .................................... 33 100 10. Normative References ...................................... 34 101 11. Informative References .................................... 34 102 12. Acknowledgments ........................................... 36 103 13. Authors' Addresses ........................................ 36 104 14. Full Copyright Statement .................................. 37 105 15. Appendix X - Change History ............................... 38 106 1. Introduction 108 This document defines several object classes to provide Lightweight 109 Directory Access Protocol v3 [LDAP-TS] applications with flexible 110 options in defining printer information using LDAP schema. Classes 111 are provided for defining directory entries with common printer 112 information as well as for extending existing directory entries with 113 SLPv2 [RFC2608], IPP/1.1 [RFC2911], and LPR [RFC1179] specific 114 information. 116 The schema defined in this document is based on the printer 117 attributes listed in Appendix E 'Generic Directory Schema' of 118 Internet Printing Protocol/1.1 (IPP) [RFC2911]. A few additional 119 printer attributes are based on definitions in the Printer MIB 120 [RFC1759]. 122 The schema defined in this document is technically aligned with the 123 stable IANA-registered 'service:printer:' v2.0 template [SLP-PRT], 124 for compatibility with already deployed Service Location Protocol 125 (SLPv2) [RFC2608] service advertising and discovery infrastructure. 126 The attribute syntaxes are technically aligned with the 127 'service:printer:' v2.0 template - therefore simpler types are 128 sometimes used (for example, 'DirectoryString' [RFC2252] rather than 129 'labeledURI' [RFC2079] for the 'printer-uri' attribute). 131 Please send comments directly to the authors at the addresses listed 132 in Section 13 "Authors' Addresses". 134 1.1. Rationale for using DirectoryString Syntax 136 The attribute syntax 'DirectoryString' (UTF-8 [RFC2279]) defined in 137 [RFC2252] is specified for several groups of string attributes that 138 are defined in this document: 140 1) URI 141 - printer-uri, printer-xri-supported, printer-more-info 143 The UTF-8 encoding is forward compatible with any future 144 deployment of (UTF-8 based) IRI (Internationalized Resource 145 Identifiers) [W3C-IRI] currently being developed by the W3C 146 Internationalization Working Group. 148 2) Description 149 - printer-name, printer-location, printer-info, 150 printer-make-and-model 152 The UTF-8 encoding supports descriptions in any language, 153 conformant with the "IETF Policy on Character Sets and Languages" 154 [RFC2277]. 156 Note: The printer-natural-language-configured attribute contains 157 a language tag [ISO3066] for these description attributes (for 158 example, to support text-to-speech conversions). 160 3) Keyword 161 - printer-compression-supported, printer-finishings-supported, 162 printer-media-supported, printer-media-local-supported, 163 printer-print-quality-supported 165 The UTF-8 encoding is compatible with the current IPP/1.1 166 [RFC2911] definition of the equivalent attributes, most of which 167 have the IPP/1.1 union syntax 'keyword or name'. The keyword 168 attributes defined in this document are extensible by 169 site-specific or vendor-specific 'names' which behave like new 170 'keywords' 172 Note: In IPP/1.1, each value is strongly typed over-the-wire as 173 either 'keyword' or 'name'. This union selector is not preserved 174 in the definitions of these equivalent LDAP attributes. 176 1.2. Rationale for using caseIgnoreMatch 178 The EQUALITY matching rule 'caseIgnoreMatch' defined in [RFC2252] is 179 specified for several groups of string attributes that are defined in 180 this document: 182 1) URI 184 These URI attributes specify EQUALITY matching with 185 'caseIgnoreMatch' (rather than with 'caseExactMatch') in order to 186 conform to the spirit of [RFC2396], which requires case 187 insensitive matching on the host part of a URI versus case 188 sensitive matching on the remainder of a URI. 190 These URI attributes follow existing practice of supporting case 191 insensitive equality matching for host names in the 192 associatedDomain attribute defined in [LDAP-USER]. 194 Either equality matching rule choice would be a compromise: 195 a) case sensitive whole URI matching may lead to false negative 196 matches and has been shown to be fragile (given deployed client 197 applications that 'pretty up' host names displayed and 198 transferred in URI); 199 b) case insensitive whole URI matching may lead to false positive 200 matches, although it is a dangerous practice to publish URI that 201 differ only by case (for example, in the path elements). 203 2) Description 205 Case insensitive equality matching is more user-friendly for 206 description attributes. 208 3) Keyword 210 Case insensitive equality matching is more user-friendly for 211 keyword attributes. 213 1.3. Rationale for using caseIgnoreSubstringsMatch 215 The SUBSTR matching rule 'caseIgnoreSubstringsMatch' defined in 216 [RFC2252] is specified for several groups of string attributes that 217 are defined in this document: 219 1) URI 221 These URI attributes follow existing practice of supporting case 222 insensitive equality matching for host names in the 223 associatedDomain attribute defined in [LDAP-USER]. 225 2) Description 227 Support for case insensitive substring matching is more 228 user-friendly for description attributes. 230 3) Keyword 232 Support for case insensitive substring matching is more 233 user-friendly for keyword attributes. 235 2. Terminology and Conventions 237 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 238 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 239 document are to be interpreted as described in BCP 14 [RFC2119]. 241 Schema definitions are provided using LDAPv3 [LDAP-TS] description 242 formats. Definitions provided here are formatted (line wrapped) for 243 readability. 245 3. Definition of Object Classes 247 We define the following LDAP object classes for use with both generic 248 printer related information and services specific to SLPv2 [RFC2608], 249 IPP/1.1 [RFC2911], and LPR [RFC1179]. 251 slpServicePrinter - auxiliary class for SLP registered printers 252 printerAbstract - abstract class for all printer classes 253 printerService - structural class for printers 254 printerServiceAuxClass - auxiliary class for printers 255 printerIPP - auxiliary class for IPP printers 256 printerLPR - auxiliary class for LPR printers 258 The following are some examples of how applications may choose to use 259 these classes when creating directory entries: 261 1) Use printerService for directory entries containing common 262 printer information. 264 2) Use both printerService and slpServicePrinter for directory 265 entries containing common printer information for SLP registered 266 printers. 268 3) Use printerService, printerLPR and printerIPP for directory 269 entries containing common printer information for printers that 270 support both LPR and IPP. 272 4) Use printerServiceAuxClass and object classes not defined by this 273 document for directory entries containing common printer 274 information. In this example, printerServiceAuxClass is used for 275 extending other structural classes defining printer information 276 with common printer information defined in this document. 278 Refer to Section 4 for definition of attribute types referenced by 279 these object classes. We use attribute names instead of OIDs in 280 object class definitions for clarity. Some attribute names described 281 in [RFC2911] have been prefixed with 'printer-' as recommended in 282 [RFC2926] and [SLP-PRT]. 284 3.1. slpServicePrinter 286 ( 1.3.18.0.2.6.254 287 NAME 'slpServicePrinter' 288 DESC 'Service Location Protocol (SLP) information.' 289 AUXILIARY 290 SUP slpService 291 ) 293 This auxiliary class defines Service Location Protocol (SLPv2) 294 [RFC2608] specific information. It should be used with a structural 295 class such as printerService. It may be used to create new or extend 296 existing directory entries with SLP 'service:printer' abstract 297 service type information as defined in [SLP-PRT]. This object class 298 is derived from 'slpService', the parent class for all SLP services, 299 defined in [RFC2926]. 301 3.2. printerAbstract 303 ( 1.3.18.0.2.6.258 304 NAME 'printerAbstract' 305 DESC 'Printer related information.' 306 ABSTRACT 307 SUP top 308 MAY ( printer-name $ 309 printer-natural-language-configured $ 310 printer-location $ printer-info $ printer-more-info $ 311 printer-make-and-model $ 312 printer-multiple-document-jobs-supported $ 313 printer-charset-configured $ printer-charset-supported $ 314 printer-generated-natural-language-supported $ 315 printer-document-format-supported $ printer-color-supported $ 316 printer-compression-supported $ printer-pages-per-minute $ 317 printer-pages-per-minute-color $ 318 printer-finishings-supported $ printer-number-up-supported $ 319 printer-sides-supported $ printer-media-supported $ 320 printer-media-local-supported $ 321 printer-resolution-supported $ 322 printer-print-quality-supported $ 323 printer-job-priority-supported $ printer-copies-supported $ 324 printer-job-k-octets-supported $ printer-current-operator $ 325 printer-service-person $ 326 printer-delivery-orientation-supported $ 327 printer-stacking-order-supported $ 328 printer-output-features-supported ) 329 ) 330 This abstract class defines printer information. It is a base class 331 for deriving other printer related classes, such as, but not limited 332 to, classes defined in this document. It defines a common set of 333 printer attributes that are not specific to any one type of service, 334 protocol or operating system. 336 3.3. printerService 338 ( 1.3.18.0.2.6.255 339 NAME 'printerService' 340 DESC 'Printer information.' 341 STRUCTURAL 342 SUP printerAbstract 343 MAY ( printer-uri $ printer-xri-supported ) 344 ) 346 This structural class defines printer information. It is derived 347 from class printerAbstract and thus inherits common printer 348 attributes. This class can be used with or without auxiliary classes 349 to define printer information. Auxiliary classes can be used to 350 extend the common printer information with protocol, service or 351 operating system specific information. 353 Note: When extending other structural classes with auxiliary 354 classes, printerService should not be used. 356 3.4. printerServiceAuxClass 358 ( 1.3.18.0.2.6.257 359 NAME 'printerServiceAuxClass' 360 DESC 'Printer information.' 361 AUXILIARY 362 SUP printerAbstract 363 MAY ( printer-uri $ printer-xri-supported ) 364 ) 366 This auxiliary class defines printer information. It is derived from 367 class printerAbstract and thus inherits common printer attributes. 368 This class should be used with a structural class. 370 3.5. printerIPP 372 ( 1.3.18.0.2.6.256 373 NAME 'printerIPP' 374 DESC 'Internet Printing Protocol (IPP) information.' 375 AUXILIARY 376 SUP top 377 MAY ( printer-ipp-versions-supported $ 378 printer-multiple-document-jobs-supported ) 379 ) 381 This auxiliary class defines Internet Printing Protocol (IPP/1.1) 382 [RFC2911] information. It should be used with a structural class 383 such as printerService. It is used to extend structural classes with 384 IPP specific printer information. 386 3.6. printerLPR 388 ( 1.3.18.0.2.6.253 389 NAME 'printerLPR' 390 DESC 'LPR information.' 391 AUXILIARY 392 SUP top 393 MUST ( printer-name ) 394 MAY ( printer-aliases) 395 ) 397 This auxiliary class defines LPR [RFC1179] information. It should be 398 used with a structural class such as printerService. It is used to 399 identify directory entries that support LPR. 401 4. Definition of Attribute Types 403 The following attribute types are referenced by the object classes 404 defined in Section 3. 406 The following attribute types reference syntax OIDs defined in 407 Section 6 of [RFC2252] (see Section 5 'Definition of Syntaxes' 408 below). 410 The following attribute types reference matching rule names (instead 411 of OIDs) for clarity (see Section 6 below). For optional attributes, 412 if the printer information is not known, the attribute value should 413 not be set. In the following definitions, referenced matching rules 414 are defined in Section 8 of [RFC2252] and/or Section 2 of [LDAP-USER] 415 (see Section 6 'Definition of Matching Rules' below). 417 The following table is a summary of the attribute names defined by 418 this document and their corresponding names from [RFC2911]. Some 419 attribute names described in [RFC2911] have been prefixed with 420 'printer-' as recommended in [RFC2926], to address the flat namespace 421 for LDAP identifiers. 423 LDAP & SLP Printer Schema IPP Model [RFC2911] 424 ------------------------------ ------------------------------------- 425 printer-uri 426 printer-xri-supported 427 [IPP printer-uri-supported] 428 [IPP uri-authentication-supported] 429 [IPP uri-security-supported] 430 printer-name printer-name 431 printer-natural-language-configured 432 natural-language-configured 433 printer-location printer-location 434 printer-info printer-info 435 printer-more-info printer-more-info 436 printer-make-and-model printer-make-and-model 437 printer-ipp-versions-supported ipp-versions-supported 438 printer-multiple-document-jobs-supported 439 multiple-document-jobs-supported 440 printer-charset-configured charset-configured 441 printer-charset-supported charset-supported 442 printer-generated-natural-language-supported 443 generated-natural-language-supported 444 printer-document-format-supported 445 document-format-supported 446 printer-color-supported color-supported 447 printer-compression-supported compression-supported 448 printer-pages-per-minute pages-per-minute 449 printer-pages-per-minute-color pages-per-minute-color 450 printer-finishings-supported finishings-supported 451 printer-number-up-supported number-up-supported 452 printer-sides-supported sides-supported 453 printer-media-supported media-supported 454 printer-media-local-supported [site names from IPP media-supported] 455 printer-resolution-supported printer-resolution-supported 456 printer-print-quality-supported print-quality-supported 457 printer-job-priority-supported job-priority-supported 458 printer-copies-supported copies-supported 459 printer-job-k-octets-supported job-k-octets-supported 460 printer-current-operator 461 printer-service-person 462 printer-delivery-orientation-supported 463 printer-stacking-order-supported 464 printer-output-features-supported 465 printer-aliases 466 4.1. printer-uri 468 ( 1.3.18.0.2.4.1140 469 NAME 'printer-uri' 470 DESC 'A URI supported by this printer.' 471 EQUALITY caseIgnoreMatch 472 SUBSTR caseIgnoreSubstringsMatch 473 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 474 SINGLE-VALUE 475 ) 477 If the printer-xri-supported LDAP attribute is implemented, then this 478 printer-uri value should be listed in printer-xri-supported. 480 Values of URI should conform to [RFC2396], although URI schemes may 481 be defined which do not conform to [RFC2396] (see [RFC2717] and 482 [RFC2718]). 484 Note: LDAP application clients should not attempt to use malformed 485 URI values read from this attribute. LDAP administrative clients 486 should not write malformed URI values into this attribute. 488 Note: For SLP registered printers, the LDAP printer-uri attribute 489 should be set to the value of the SLP-registered URL of the printer, 490 for interworking with SLPv2 [RFC2608] service discovery. 492 Note: See Sections 1.1, 1.2, and 1.3 for rationale for design 493 choices. 495 4.2. printer-xri-supported 497 ( 1.3.18.0.2.4.1107 498 NAME 'printer-xri-supported' 499 DESC 'The unordered list of XRI (extended resource identifiers) 500 supported by this printer.' 501 EQUALITY caseIgnoreMatch 502 SUBSTR caseIgnoreSubstringsMatch 503 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 504 ) 506 A list of XRI (extended resource identifiers) supported by this 507 printer. Each value of this list should consist of a URI (uniform 508 resource identifier) followed by (optional) authentication and 509 security fields. 511 Values of URI should conform to [RFC2396], although URI schemes may 512 be defined which do not conform to [RFC2396] (see [RFC2717] and 514 [RFC2718]). 516 Note: LDAP application clients should not attempt to use malformed 517 URI values read from this attribute. LDAP administrative clients 518 should not write malformed URI values into this attribute. 520 Note: This attribute is based on 'printer-uri-supported', 521 'uri-authentication-supported', and 'uri-security-supported' (called 522 the 'Three Musketeers' because they are parallel ordered attributes) 523 defined in IPP/1.1 [RFC2911]. This attribute unfolds those IPP/1.1 524 attributes and thus avoids the ordering (and same number of values) 525 constraints of the IPP/1.1 separate attributes. 527 Defined keywords for fields include: 529 'uri' (IPP 'printer-uri-supported') 530 'auth' (IPP 'uri-authentication-supported') 531 'sec' (IPP 'uri-security-supported') 533 A missing 'auth' field should be interpreted to mean 'none'. Per 534 IPP/1.1 [RFC2911], defined values of the 'auth' field include: 536 'none' (no authentication for this URI) 537 'requesting-user-name' (from operation request) 538 'basic' (HTTP/1.1 Basic [RFC2617]) 539 'digest' (HTTP/1.1 Basic, [RFC2617]) 540 'certificate' (from certificate) 542 A missing 'sec' field should be interpreted to mean 'none'. Per 543 IPP/1.1 [RFC2911], defined values of the 'sec' field include: 545 'none' (no security for this URI) 546 'ssl3' (Netscape SSL3) 547 'tls' (IETF TLS/1.0, [RFC2246]) 549 Each XRI field should be delimited by '<'. For example: 551 'uri=ipp://foo.com< auth=digest< sec=tls<' 552 'uri=lpr://bar.com< auth=none< sec=none<' 553 'uri=mailto:printer@foobar.com< auth=none< sec=none<' 555 Note: The syntax and delimiter for this attribute are aligned with 556 the equivalent attribute in the 'service:printer:' v2.0 template 557 [SLP-PRT]. Whitespace is permitted after (but not before) the 558 delimiter '<'. Note that this delimiter differs from 559 printer-resolution-supported. 561 Note: See Sections 1.1, 1.2, and 1.3 for rationale for design 562 choices. 564 4.3. printer-name 566 ( 1.3.18.0.2.4.1135 567 NAME 'printer-name' 568 DESC 'The site-specific administrative name of this printer.' 569 EQUALITY caseIgnoreMatch 570 SUBSTR caseIgnoreSubstringsMatch 571 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 572 SINGLE-VALUE 573 ) 575 Values of this attribute should be specified in the language 576 specified in printer-natural-language-configured (for example, to 577 support text-to-speech conversions), although the printer's name may 578 be specified in any language. This name may be the last part of the 579 printer's URI or it may be completely unrelated. This name may 580 contain characters that are not allowed in a conventional URI (see 581 [RFC2396]). 583 4.4. printer-natural-language-configured 585 ( 1.3.18.0.2.4.1119 586 NAME 'printer-natural-language-configured' 587 DESC 'The configured natural language in which error and status 588 messages will be generated (by default) by this printer.' 589 EQUALITY caseIgnoreMatch 590 SUBSTR caseIgnoreSubstringsMatch 591 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 592 SINGLE-VALUE 593 ) 595 Also, a possible natural language for printer string attributes set 596 by operator, system administrator, or manufacturer. Also, the 597 (declared) natural language of the printer-name, printer-location, 598 printer-info, and printer-make-and-model attributes of this printer. 600 Values of language tags should conform to "Tags for the 601 Identification of Languages" [RFC3066]. For example: 603 'en-us' (English as spoken in the US) 604 'fr-fr' (French as spoken in France) 606 For consistency with IPP/1.1 [RFC2911], language tags in this 607 attribute should be lowercase normalized. 609 4.5. printer-location 611 ( 1.3.18.0.2.4.1136 612 NAME 'printer-location' 613 DESC 'The physical location of this printer.' 614 EQUALITY caseIgnoreMatch 615 SUBSTR caseIgnoreSubstringsMatch 616 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 617 SINGLE-VALUE 618 ) 620 For example: 622 'Room 123A' 623 'Second floor of building XYZ' 625 4.6. printer-info 627 ( 1.3.18.0.2.4.1139 628 NAME 'printer-info' 629 DESC 'Descriptive information about this printer.' 630 EQUALITY caseIgnoreMatch 631 SUBSTR caseIgnoreSubstringsMatch 632 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 633 SINGLE-VALUE 634 ) 636 For example: 638 'This printer can be used for printing color transparencies for 639 HR presentations' 640 'Out of courtesy for others, please print only small (1-5 page) 641 jobs at this printer' 642 'This printer is going away on July 1, 1997, please find a new 643 printer' 645 4.7. printer-more-info 647 ( 1.3.18.0.2.4.1134 648 NAME 'printer-more-info' 649 DESC 'A URI for more information about this specific printer.' 650 EQUALITY caseIgnoreMatch 651 SUBSTR caseIgnoreSubstringsMatch 652 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 653 SINGLE-VALUE 654 ) 656 For example, this could be an HTTP type URI referencing an HTML page 657 accessible to a Web Browser. The information obtained from this URI 658 is intended for end user consumption. 660 Values of URI should conform to [RFC2396], although URI schemes may 661 be defined which do not conform to [RFC2396] (see [RFC2717] and 662 [RFC2718]). 664 Note: LDAP application clients should not attempt to use malformed 665 URI values read from this attribute. LDAP administrative clients 666 should not write malformed URI values into this attribute. 668 Note: See Sections 1.1, 1.2, and 1.3 for rationale for design 669 choices. 671 4.8. printer-make-and-model 673 ( 1.3.18.0.2.4.1138 674 NAME 'printer-make-and-model' 675 DESC 'Make and model of this printer.' 676 EQUALITY caseIgnoreMatch 677 SUBSTR caseIgnoreSubstringsMatch 678 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 679 SINGLE-VALUE 680 ) 682 Note: The printer manufacturer may initially populate this 683 attribute. 685 4.9. printer-ipp-versions-supported 687 ( 1.3.18.0.2.4.1133 688 NAME 'printer-ipp-versions-supported' 689 DESC 'IPP protocol version(s) that this printer supports.' 690 EQUALITY caseIgnoreMatch 691 SUBSTR caseIgnoreSubstringsMatch 692 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 693 ) 695 The IPP protocol version(s) should include major and minor versions, 696 i.e., the exact version numbers for which this Printer implementation 697 meets the IPP version-specific conformance requirements. 699 4.10. printer-multiple-document-jobs-supported 701 ( 1.3.18.0.2.4.1132 702 NAME 'printer-multiple-document-jobs-supported' 703 DESC 'Indicates whether or not this printer supports more than one 704 document per job.' 705 EQUALITY booleanMatch 706 SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 707 SINGLE-VALUE 708 ) 710 4.11. printer-charset-configured 712 ( 1.3.18.0.2.4.1109 713 NAME 'printer-charset-configured' 714 DESC 'The configured charset in which error and status messages will 715 be generated (by default) by this printer.' 716 EQUALITY caseIgnoreMatch 717 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{63} 718 SINGLE-VALUE 719 ) 721 Also, a possible charset for printer string attributes set by 722 operator, system administrator, or manufacturer. For example: 724 'utf-8' (ISO 10646/Unicode in UTF-8 transform [RFC2279]) 725 'iso-8859-1' (Latin1) 727 Values of charset tags should be defined in the IANA Registry of 728 Coded Character Sets [IANA-CHAR] (see also [RFC2978]) and the 729 '(preferred MIME name)' should be used as the charset tag in this 730 attribute. 732 For consistency with IPP/1.1 [RFC2911], charset tags in this 733 attribute should be lowercase normalized. 735 4.12. printer-charset-supported 737 ( 1.3.18.0.2.4.1131 738 NAME 'printer-charset-supported' 739 DESC 'Set of charsets supported for the attribute values of syntax 740 DirectoryString for this directory entry.' 741 EQUALITY caseIgnoreMatch 742 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{63} 743 ) 744 For example: 746 'utf-8' (ISO 10646/Unicode in UTF-8 transform [RFC2279]) 747 'iso-8859-1' (Latin1) 749 Values of charset tags should be defined in the IANA Registry of 750 Coded Character Sets [IANA-CHAR] (see also [RFC2978]) and the 751 '(preferred MIME name)' should be used as the charset tag in this 752 attribute. 754 For consistency with IPP/1.1 [RFC2911], charset tags in this 755 attribute should be lowercase normalized. 757 4.13. printer-generated-natural-language-supported 759 ( 1.3.18.0.2.4.1137 760 NAME 'printer-generated-natural-language-supported' 761 DESC 'Natural language(s) supported for this directory entry.' 762 EQUALITY caseIgnoreMatch 763 SUBSTR caseIgnoreSubstringsMatch 764 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{63} 765 ) 767 Values of language tags should conform to "Tags for the 768 Identification of Languages" [RFC3066]. For example: 770 'en-us' (English as spoken in the US) 771 'fr-fr' (French as spoken in France) 773 For consistency with IPP/1.1 [RFC2911], language tags in this 774 attribute should be lowercase normalized. 776 4.14. printer-document-format-supported 778 ( 1.3.18.0.2.4.1130 779 NAME 'printer-document-format-supported' 780 DESC 'The possible source document formats which may be interpreted 781 and printed by this printer.' 782 EQUALITY caseIgnoreMatch 783 SUBSTR caseIgnoreSubstringsMatch 784 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 785 ) 787 Values of document formats should be MIME media types defined in the 788 IANA Registry of MIME Media Types [IANA-MIME] (see also [RFC2048]). 790 4.15. printer-color-supported 792 ( 1.3.18.0.2.4.1129 793 NAME 'printer-color-supported' 794 DESC 'Indicates whether this printer is capable of any type of color 795 printing at all, including highlight color.' 796 EQUALITY booleanMatch 797 SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 798 SINGLE-VALUE 799 ) 801 4.16. printer-compression-supported 803 ( 1.3.18.0.2.4.1128 804 NAME 'printer-compression-supported' 805 DESC 'Compression algorithms supported by this printer.' 806 EQUALITY caseIgnoreMatch 807 SUBSTR caseIgnoreSubstringsMatch 808 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{255} 809 ) 811 Values defined in IPP/1.1 [RFC2911] include: 813 'none' (no compression is used) 814 'deflate' (public domain ZIP described in [RFC1951]) 815 'gzip' (GNU ZIP described in [RFC1952]) 816 'compress' (UNIX compression described in [RFC1977]) 818 4.17. printer-pages-per-minute 820 ( 1.3.18.0.2.4.1127 821 NAME 'printer-pages-per-minute' 822 DESC 'The nominal number of pages per minute which may be output by 823 this printer.' 824 EQUALITY integerMatch 825 ORDERING integerOrderingMatch 826 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 827 SINGLE-VALUE 828 ) 830 This attribute is informative, not a service guarantee. Typically, 831 it is the value used in marketing literature to describe this 832 printer. For example, the value for a simplex or black-and-white 833 print mode. 835 4.18. printer-pages-per-minute-color 837 ( 1.3.18.0.2.4.1126 838 NAME 'printer-pages-per-minute-color' 839 DESC 'The nominal number of color pages per minute which may be 840 output by this printer.' 841 EQUALITY integerMatch 842 ORDERING integerOrderingMatch 843 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 844 SINGLE-VALUE 845 ) 847 This attribute is informative, not a service guarantee. Typically, 848 it is the value used in marketing literature to describe this 849 printer. 851 4.19. printer-finishings-supported 853 ( 1.3.18.0.2.4.1125 854 NAME 'printer-finishings-supported' 855 DESC 'The possible finishing operations supported by this printer.' 856 EQUALITY caseIgnoreMatch 857 SUBSTR caseIgnoreSubstringsMatch 858 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{255} 859 ) 861 Values defined in IPP/1.1 [RFC2911] include: 'none', 'staple', 862 'punch', 'cover', 'bind', 'saddle-stitch', 'edge-stitch', 863 'staple-top-left', 'staple-bottom-left', 'staple-top-right', 864 'staple-bottom-right', 'edge-stitch-left', 'edge-stitch-top', 865 'edge-stitch-right', 'edge-stitch-bottom', 'staple-dual-left', 866 'staple-dual-top', 'staple-dual-right', 'staple-dual-bottom'. 868 Note: Implementations may support other values. 870 4.20. printer-number-up-supported 872 ( 1.3.18.0.2.4.1124 873 NAME 'printer-number-up-supported' 874 DESC 'The possible numbers of print-stream pages to impose upon a 875 single side of an instance of a selected medium.' 876 EQUALITY integerMatch 877 ORDERING integerOrderingMatch 878 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 879 ) 881 Values defined in IPP/1.1 [RFC2911] include: '1', '2', and '4'. 883 Note: Implementations may support other values. 885 4.21. printer-sides-supported 887 ( 1.3.18.0.2.4.1123 888 NAME 'printer-sides-supported' 889 DESC 'The number of impression sides (one or two) and the two-sided 890 impression rotations supported by this printer.' 891 EQUALITY caseIgnoreMatch 892 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 893 ) 895 Values defined in IPP/1.1 [RFC2911] include: 'one-sided', 896 'two-sided-long-edge', 'two-sided-short-edge'.' 898 4.22. printer-media-supported 900 ( 1.3.18.0.2.4.1122 901 NAME 'printer-media-supported' 902 DESC 'The standard names/types/sizes (and optional color suffixes) of 903 the media supported by this printer.' 904 EQUALITY caseIgnoreMatch 905 SUBSTR caseIgnoreSubstringsMatch 906 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{255} 907 ) 909 Values are defined in IPP/1.1 [RFC2911] or any IANA registered 910 extensions. For example: 912 'iso-a4' 913 'envelope' 914 'na-letter-white' 916 4.23. printer-media-local-supported 918 ( 1.3.18.0.2.4.1117 919 NAME 'printer-media-local-supported' 920 DESC 'Site-specific names of media supported by this printer.' 921 EQUALITY caseIgnoreMatch 922 SUBSTR caseIgnoreSubstringsMatch 923 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{255} 924 ) 926 Values should be in the natural language specified by 927 printer-natural-language-configured. 929 For example: 931 'purchasing-form' (site-specific name) 933 as opposed to 'na-letter' (standard keyword from IPP/1.1 [RFC2911]) 934 in the printer-media-supported attribute. 936 4.24. printer-resolution-supported 938 ( 1.3.18.0.2.4.1121 939 NAME 'printer-resolution-supported' 940 DESC 'List of resolutions supported for printing documents by this 941 printer.' 942 EQUALITY caseIgnoreMatch 943 SUBSTR caseIgnoreSubstringsMatch 944 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{255} 945 ) 947 Each resolution value should be a string containing 3 fields: 948 1) Cross feed direction resolution (positive integer); 949 2) Feed direction resolution (positive integer); 950 3) Unit - 'dpi' (dots per inch) or 'dpcm' (dots per centimeter). 952 Each resolution field should be delimited by '>'. For example: 954 '300> 300> dpi>' 955 '600> 600> dpi>' 957 Note: This attribute is based on 'printer-resolution-supported' 958 defined in IPP/1.1 [RFC2911] (which has a binary complex encoding) 959 derived from 'prtMarkerAddressabilityFeedDir', 960 'prtMarkerAddressabilityXFeedDir', and 'prtMarkerAddressabilityUnit' 961 defined in the Printer MIB [RFC1759] (which have integer encodings). 963 Note: The syntax and delimiter for this attribute are aligned with 964 the equivalent attribute in the 'service:printer:' v2.0 template 965 [SLP-PRT]. Whitespace is permitted after (but not before) the 966 delimiter '>'. Note that this delimiter differs from 967 printer-xri-supported. 969 4.25. printer-print-quality-supported 971 ( 1.3.18.0.2.4.1120 972 NAME 'printer-print-quality-supported' 973 DESC 'List of print qualities supported for printing documents on 974 this printer.' 975 EQUALITY caseIgnoreMatch 976 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 977 ) 979 Values defined in IPP/1.1 [RFC2911] include: 981 'unknown' 982 'draft' 983 'normal' 984 'high' 986 4.26. printer-job-priority-supported 988 ( 1.3.18.0.2.4.1110 989 NAME 'printer-job-priority-supported' 990 DESC 'Indicates the number of job priority levels supported by this 991 printer.' 992 EQUALITY integerMatch 993 ORDERING integerOrderingMatch 994 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 995 SINGLE-VALUE 996 ) 998 An IPP/1.1 [RFC2911] conformant Printer, which supports job priority, 999 always supports a full range of priorities from '1' to '100' (to 1000 ensure consistent behavior), therefore this attribute describes the 1001 'granularity' of priority supported. Values of this attribute are 1002 from '1' to '100'. 1004 4.27. printer-copies-supported 1006 ( 1.3.18.0.2.4.1118 1007 NAME 'printer-copies-supported' 1008 DESC 'The maximum number of copies of a document that may be printed 1009 as a single job on 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 ) 1016 A positive value indicates the maximum supported copies. A value of 1017 '0' indicates no maximum limit. A value of '-1' indicates 'unknown'. 1019 Note: The syntax and values for this attribute are aligned with the 1020 equivalent attribute in the 'service:printer:' v2.0 template 1021 [SLP-PRT]. 1023 4.28. printer-job-k-octets-supported 1025 ( 1.3.18.0.2.4.1111 1026 NAME 'printer-job-k-octets-supported' 1027 DESC 'The maximum size in kilobytes (1,024 octets actually) incoming 1028 print job that this printer will accept.' 1029 EQUALITY integerMatch 1030 ORDERING integerOrderingMatch 1031 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1032 SINGLE-VALUE 1033 ) 1035 A positive value indicates the maximum supported job size. A value 1036 of '0' indicates no maximum limit. A value of '-1' indicates 1037 'unknown'. 1039 Note: The syntax and values for this attribute are aligned with the 1040 equivalent attribute in the 'service:printer:' v2.0 template 1041 [SLP-PRT]. 1043 4.29. printer-current-operator 1045 ( 1.3.18.0.2.4.1112 1046 NAME 'printer-current-operator' 1047 DESC 'The identity of the current human operator responsible for 1048 operating this printer.' 1049 EQUALITY caseIgnoreMatch 1050 SUBSTR caseIgnoreSubstringsMatch 1051 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 1052 SINGLE-VALUE 1053 ) 1055 The value of this attribute should include information that would 1056 enable other humans to reach the operator, such as a telephone 1057 number. 1059 4.30. printer-service-person 1061 ( 1.3.18.0.2.4.1113 1062 NAME 'printer-service-person' 1063 DESC 'The identity of the current human service person responsible 1064 for servicing this printer.' 1065 EQUALITY caseIgnoreMatch 1066 SUBSTR caseIgnoreSubstringsMatch 1067 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 1068 SINGLE-VALUE 1069 ) 1071 The value of this attribute should include information that would 1072 enable other humans to reach the service person, such as a telephone 1073 number. 1075 4.31. printer-delivery-orientation-supported 1077 ( 1.3.18.0.2.4.1114 1078 NAME 'printer-delivery-orientation-supported' 1079 DESC 'The possible delivery orientations of pages as they are printed 1080 and ejected from this printer.' 1081 EQUALITY caseIgnoreMatch 1082 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 1083 ) 1085 Values defined include: 1087 'unknown' 1088 'face-up' 1089 'face-down' 1091 Note: The syntax and values for this attribute are aligned with the 1092 equivalent attribute in the 'service:printer:' v2.0 template 1093 [SLP-PRT]. 1095 4.32. printer-stacking-order-supported 1097 ( 1.3.18.0.2.4.1115 1098 NAME 'printer-stacking-order-supported' 1099 DESC 'The possible stacking order of pages as they are printed and 1100 ejected from this printer.' 1101 EQUALITY caseIgnoreMatch 1102 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 1103 ) 1104 Values defined include: 1106 'unknown' 1107 'first-to-last' 1108 'last-to-first' 1110 Note: The syntax and values for this attribute are aligned with the 1111 equivalent attribute in the 'service:printer:' v2.0 template 1112 [SLP-PRT]. 1114 4.33. printer-output-features-supported 1116 ( 1.3.18.0.2.4.1116 1117 NAME 'printer-output-features-supported' 1118 DESC 'The possible output features supported by this printer.' 1119 EQUALITY caseIgnoreMatch 1120 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 1121 ) 1123 Values defined include: 1125 'unknown' 1126 'bursting' 1127 'decollating' 1128 'page-collating' 1129 'offset-stacking' 1131 Note: The syntax and values for this attribute are aligned with the 1132 equivalent attribute in the 'service:printer:' v2.0 template 1133 [SLP-PRT]. 1135 Note: Implementations may support other values. 1137 4.34. printer-aliases 1139 ( 1.3.18.0.2.4.1108 1140 NAME 'printer-aliases' 1141 DESC 'List of site-specific administrative names of this printer in 1142 addition to the value specified for printer-name.' 1143 EQUALITY caseIgnoreMatch 1144 SUBSTR caseIgnoreSubstringsMatch 1145 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} 1146 ) 1148 Values of this attribute should be specified in the language 1149 specified in printer-natural-language-configured (for example, to 1150 support text-to-speech conversions), although the printer's alias may 1151 be specified in any language. 1153 5. Definition of Syntaxes 1155 No new attribute syntaxes are defined by this document. 1157 The attribute types defined in Section 4 of this document reference 1158 syntax OIDs defined in Section 6 of [RFC2252], which are summarized 1159 below: 1161 Syntax OID Syntax Description 1162 ------------------------------ ------------------ 1163 1.3.6.1.4.1.1466.115.121.1.7 Boolean 1164 1.3.6.1.4.1.1466.115.121.1.15 DirectoryString (UTF-8 [RFC2279]) 1165 1.3.6.1.4.1.1466.115.121.1.27 Integer 1167 6. Definition of Matching Rules 1169 No new matching rules are defined by this document. 1171 The attribute types defined in Section 4 of this document reference 1172 matching rules defined in Section 8 of [RFC2252] and/or Section 2 of 1173 [LDAP-USER], which are summarized below: 1175 Matching Rule OID Matching Rule Name Usage 1176 ------------------------------ ------------------ ----- 1177 2.5.13.13 booleanMatch EQUALITY 1178 2.5.13.2 caseIgnoreMatch EQUALITY 1179 2.5.13.14 integerMatch EQUALITY 1180 2.5.13.15 integerOrderingMatch ORDERING 1181 2.5.13.4 caseIgnoreSubstringsMatch SUBSTR 1183 7. IANA Considerations 1185 This document does not define any new syntaxes or matching rules. 1187 This document does define the following Object Identifier 1188 Descriptors, for registration by IANA when this RFC is published: 1190 7.1. Registration of Object Classes 1192 Subject: Request for LDAP Descriptor Registration 1194 Descriptor (short name): see table below 1196 Object Identifier: see table below 1198 Person & email address to contact for further information: see below 1200 Usage: object class 1202 Specification: RFCnnnn [ [RFC Editor: to be assigned] ] 1204 Author/Change Controller: 1206 Pat Fleming 1207 IBM 1208 Highway 52 N 1209 Rochester, MN 55901 1210 USA 1211 Phone: +1 507-253-7583 1212 EMail: flemingp@us.ibm.com 1214 Comments: 1216 Object Class OID 1217 ------------------------------------ --------------------- 1218 slpServicePrinter 1.3.18.0.2.6.254 1219 printerAbstract 1.3.18.0.2.6.258 1220 printerService 1.3.18.0.2.6.255 1221 printerServiceAuxClass 1.3.18.0.2.6.257 1222 printerIPP 1.3.18.0.2.6.256 1223 printerLPR 1.3.18.0.2.6.253 1224 7.2. Registration of Attribute Types 1226 Subject: Request for LDAP Descriptor Registration 1228 Descriptor (short name): see table below 1230 Object Identifier: see table below 1232 Person & email address to contact for further information: see below 1234 Usage: attribute type 1236 Specification: RFCnnnn [ [RFC Editor: to be assigned] ] 1238 Author/Change Controller: 1240 Pat Fleming 1241 IBM 1242 Highway 52 N 1243 Rochester, MN 55901 1244 USA 1245 Phone: +1 507-253-7583 1246 EMail: flemingp@us.ibm.com 1248 Comments: 1250 Attribute Type OID 1251 ------------------------------------ --------------------- 1252 printer-uri 1.3.18.0.2.4.1140 1253 printer-xri-supported 1.3.18.0.2.4.1107 1254 printer-name 1.3.18.0.2.4.1135 1255 printer-natural-language-configured 1.3.18.0.2.4.1119 1256 printer-location 1.3.18.0.2.4.1136 1257 printer-info 1.3.18.0.2.4.1139 1258 printer-more-info 1.3.18.0.2.4.1134 1259 printer-make-and-model 1.3.18.0.2.4.1138 1260 printer-ipp-versions-supported 1.3.18.0.2.4.1133 1261 printer-multiple-document-jobs-supported 1.3.18.0.2.4.1132 1262 printer-charset-configured 1.3.18.0.2.4.1109 1263 printer-charset-supported 1.3.18.0.2.4.1131 1264 printer-generated-natural-language-supported 1.3.18.0.2.4.1137 1265 printer-document-format-supported 1.3.18.0.2.4.1130 1266 printer-color-supported 1.3.18.0.2.4.1129 1267 printer-compression-supported 1.3.18.0.2.4.1128 1268 printer-pages-per-minute 1.3.18.0.2.4.1127 1269 printer-pages-per-minute-color 1.3.18.0.2.4.1126 1270 printer-finishings-supported 1.3.18.0.2.4.1125 1271 printer-number-up-supported 1.3.18.0.2.4.1124 1272 printer-sides-supported 1.3.18.0.2.4.1123 1273 printer-media-supported 1.3.18.0.2.4.1122 1274 printer-media-local-supported 1.3.18.0.2.4.1117 1275 printer-resolution-supported 1.3.18.0.2.4.1121 1276 printer-print-quality-supported 1.3.18.0.2.4.1120 1277 printer-job-priority-supported 1.3.18.0.2.4.1110 1278 printer-copies-supported 1.3.18.0.2.4.1118 1279 printer-job-k-octets-supported 1.3.18.0.2.4.1111 1280 printer-current-operator 1.3.18.0.2.4.1112 1281 printer-service-person 1.3.18.0.2.4.1113 1282 printer-delivery-orientation-supported 1.3.18.0.2.4.1114 1283 printer-stacking-order-supported 1.3.18.0.2.4.1115 1284 printer-output-features-supported 1.3.18.0.2.4.1116 1285 printer-aliases 1.3.18.0.2.4.1108 1287 8. Internationalization Considerations 1289 All text string attributes defined in this document of syntax 1290 'DirectoryString' [RFC2252] have values that are encoded in UTF-8 1291 [RFC2279], as required by [RFC2252]. 1293 A language tag [RFC3066] for all of the text string attributes 1294 defined in this document is contained in the 1295 printer-natural-language-configured attribute. 1297 Therefore, all object classes defined in this document conform to the 1298 "IETF Policy on Character Sets and Languages" [RFC2277]. 1300 9. Security Considerations 1302 See [RFC2829] for detailed guidance on authentication methods for 1303 LDAP. See [RFC2830] for detailed guidance of using TLS/1.0 [RFC2246] 1304 to supply connection confidentiality and data integrity for LDAP 1305 sessions. 1307 As with any LDAP schema, it is important to protect specific entries 1308 and attributes with the appropriate access control. It is 1309 particularly important that only administrators can modify entries 1310 defined in this LDAP printer schema. Otherwise, an LDAP client might 1311 be fooled into diverting print service requests from the original 1312 printer (or spooler) to a malicious intruder's host system, thus 1313 exposing the information in printed documents. 1315 For additional security considerations of deploying printers in an 1316 IPP environment, see Section 8 of [RFC2911]. 1318 10. Normative References 1320 [IANA-CHAR] IANA Registry of Character Sets 1321 ftp://ftp.iana.org/assignments/charset-reg/... 1323 [IANA-MIME] IANA Registry of MIME Media Types 1324 ftp://ftp.iana.org/assignments/media-types/... 1326 [LDAP-TS] Hodges, Morgan. Lightweight Directory Access Protocol 1327 (v3): Technical Specification, 1328 , work-in-progress. 1330 [LDAP-USER] Zeilenga. LDAPv3: A Collection of User Schema, 1331 , work-in-progress. 1333 [RFC2119] Bradner. Key words for use in RFCs to Indicate Requirement 1334 Levels, RFC 2119, March 1997. 1336 [RFC2252] Wahl, Coulbeck, Howes, Kille. Lightweight Directory Access 1337 Protocol (v3): Attribute Syntax Definitions, RFC 2252, December 1997. 1339 [RFC2396] Berners-Lee, Fielding, Masinter. URI Generic Syntax, RFC 1340 2396, August 1998. 1342 [RFC2829] Wahl, Alvestrand, Hodges, Morgan. Authentication Methods 1343 for LDAP, RFC 2829, May 2000. 1345 [RFC2830] Hodges, Morgan, Wahl. Lightweight Directory Access 1346 Protocol (v3): Extension for Transport Layer Security, RFC 2830, May 1347 2000. 1349 [RFC2911] deBry, Hastings, Herriot, Isaacson, Powell. Internet 1350 Printing Protocol/1.1: Model and Semantics, RFC 2911, September 2000. 1352 [RFC2926] Kempf, Moats, St. Pierre. Conversion of LDAP Schemas to 1353 and from SLP Templates, RFC 2926, September 2000. 1355 [RFC3066] Alvestrand. Tags for the Identification of Languages, RFC 1356 3066, January 2001. 1358 11. Informative References 1360 [IANA-SLPT] IANA Registry of SLP Templates 1361 ftp://ftp.iana.org/assignments/svrloc-templates/... 1363 [RFC1179] McLaughlin. Line Printer Daemon Protocol, RFC 1179, August 1364 1990. 1366 [RFC1951] Deutsch. DEFLATE Compressed Data Format Specification 1367 Version 1.3, RFC 1951, May 1996. 1369 [RFC1952] Deutsch. GZIP File Format Specification Version 4.3, RFC 1370 1952, May 1996. 1372 [RFC1977] Rand. PPP BSD Compression Protocol, RFC 1977, August 1996. 1374 [RFC2048] Freed, Borenstein. Multipurpose Internet Mail Extensions 1375 (MIME) Part Four: Registration Procedures, RFC 2048, November 1996. 1377 [RFC2079] Smith. Definition of an X.500 Attribute Type and an Object 1378 Class to Hold Uniform Resource Identifiers (URIs), RFC 2079, January 1379 1997. 1381 [RFC2246] Dierks, Allen. TLS Protocol Version 1.0, RFC 2246, January 1382 1999. 1384 [RFC2277] Alvestrand. IETF Policy on Character Sets and Languages, 1385 RFC 2277, January 1998. 1387 [RFC2279] Yergeau. UTF-8, a Transformation Format of ISO 10646, RFC 1388 2279, January 1998. 1390 [RFC2608] Guttman, Perkins, Veizades, Day. Service Location Protocol 1391 v2, RFC 2608, June 1999. 1393 [RFC2609] Guttman, Perkins, Kempf. Service Templates and Service: 1394 Schemes, RFC 2609, June 1999. 1396 [RFC2617] Franks, Hallam-Baker, Hostetler, Lawrence, Leach, Luotonen, 1397 Stewart. HTTP Authentication: Basic and Digest Access 1398 Authentication, RFC 2617, June 1999. 1400 [RFC2717] Petke, King. Registration Procedures for URL Scheme Names, 1401 RFC 2717, November 1999. 1403 [RFC2718] Masinter, Alvestrand, Zigmond, Petke. Guidelines for new 1404 URL Schemes, RFC 2718, November 1999. 1406 [RFC2978] Freed, Postel. IANA Charset Registration Procedures, RFC 1407 2978, October 2000. 1409 [SLP-PRT] St. Pierre, Isaacson, McDonald. Definition of the Printer 1410 Abstract Service Type v2.0, , May 2000. 1411 Reviewed and approved by IETF SLP Designated Expert, according to 1412 Section 5 'IANA Considerations' in [RFC2609]. 1414 Archived in the IANA Registry of SLP Templates [IANA-SLPT] at: 1415 ftp://ftp.iana.org/assignments/svrloc-templates/printer.2.0.en 1417 [W3C-IRI] Duerst, Suignard. Internationalized Resource Identifiers 1418 (IRI), , work in progress. 1420 12. Acknowledgments 1422 The editors wish to acknowledge the very significant contributions of 1423 Ken Jones (Bytemobile) and Harry Lewis (IBM) during the development 1424 of this document. 1426 Thanks to Patrik Faltstrom (Cisco), Ryan Moats (Lemur Networks), 1427 Robert Moore (IBM), Lee Rafalow (IBM), Kimberly Reger (IBM), Kurt 1428 Zeilenga (OpenLDAP), and the members of the IETF IPP Working Group, 1429 for review comments and help in preparing this document. 1431 13. Authors' Addresses 1433 Please send comments to the authors at the addresses listed below. 1435 Pat Fleming 1436 IBM 1437 Highway 52 N 1438 Rochester, MN 55901 1439 USA 1440 Phone: +1 507-253-7583 1441 EMail: flemingp@us.ibm.com 1443 Ira McDonald 1444 High North Inc 1445 221 Ridge Ave 1446 Grand Marais, MI 49839 1447 USA 1448 Phone: +1 906-494-2434 1449 Email: imcdonald@sharplabs.com 1451 14. Full Copyright Statement 1453 Copyright (C) The Internet Society (2002). All Rights Reserved. 1455 This document and translations of it may be copied and furnished to 1456 others, and derivative works that comment on or otherwise explain it 1457 or assist in its implementation may be prepared, copied, published 1458 and distributed, in whole or in part, without restriction of any 1459 kind, provided that the above copyright notice and this paragraph are 1460 included on all such copies and derivative works. However, this 1461 document itself may not be modified in any way, such as by removing 1462 the copyright notice or references to the Internet Society or other 1463 Internet organizations, except as needed for the purpose of 1464 developing Internet standards in which case the procedures for 1465 copyrights defined in the Internet Standards process must be 1466 followed, or as required to translate it into languages other than 1467 English. 1469 The limited permissions granted above are perpetual and will not be 1470 revoked by the Internet Society or its successors or assigns. 1472 This document and the information contained herein is provided on an 1473 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1474 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1475 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1476 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1477 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." 1479 15. Appendix X - Change History 1481 [ [RFC Editor: This section to be deleted before RFC publication] ] 1483 30 June 2002 - draft-fleming-ldap-printer-schema-02.txt 1484 - Final edits after IESG 'last call'; 1485 - Revised title page and section 12 'Acknowledgments' to acknowledge 1486 Ken Jones and Harry Lewis as major contributors (rather than as 1487 current editors), per new RFC Editor policies; 1488 - Rewrote and simplified Abstract and section 1 Introduction, per 1489 comments from Kurt Zeilenga; 1490 - Added section 1.1 'Rationale for using DirectoryString syntax', per 1491 comments from Kurt Zeilenga; 1492 - Added section 1.2 'Rationale for using caseIgnoreMatch', per 1493 comments from Kurt Zeilenga; 1494 - Added section 1.3 'Rationale for using caseIgnoreSubstringsMatch', 1495 per comments from Kurt Zeilenga; 1496 - Renamed section 2 to 'Terminology and Conventions' and added schema 1497 definition format reference, per comments from Kurt Zeilenga; 1498 - Revised section 3 and section 4 to remove (erroneous) guidance on 1499 adding new attributes to existing classes and discussion of RDN for 1500 auxiliary classes, per comments from Kurt Zeilenga and Ryan Moats; 1501 - Revised section 4 'Definition of Attribute Types' to remove 1502 (erroneous) guidance on support of matching rules, per comments 1503 from Kurt Zeilenga; 1504 - Revised section 4 'Definition of Attribute Types' to remove 1505 normative/lengthy descriptions from the DESC clauses and place them 1506 _below_ each formal attribute definition, per comments from Kurt 1507 Zeilenga; 1508 - Revised section 4 'Definition of Attribute Types', removing all 1509 ORDERING clauses using 'caseIgnoreOrderingMatch', per comments from 1510 Kurt Zeilenga; 1511 - Revised sections 4.x printer-uri, printer-xri-supported, and 1512 printer-more-info, to provide guidance on application handling of 1513 malformed URI and reference new sections 1.1, 1.2, and 1.3, per 1514 comments from Kurt Zeilenga; 1515 - Revised section 6 'Definition of Matching Rules' to remove 1516 (erroneous) guidance on support of matching rules, per comments 1517 from Kurt Zeilenga; 1518 - Revised section 7 'IANA Considerations' to include completed 1519 templates for IANA registration of new object classes and attribute 1520 types, defined in this document; 1521 - Revised section 9 'Security Considerations' to reference RFC 2829 1522 (for authentication methods) and RFC 2830 (for TLS confidentiality 1523 and integrity), per comments from Kurt Zeilenga; 1524 - Revised (former) section 10 'References', to separate normative and 1525 informative references, per comments from Kurt Zeilenga; 1526 - Corrected author contact info. 1528 15 February 2002 - draft-fleming-ldap-printer-schema-01.txt 1529 - Technical content entirely unchanged from previous version; 1530 - Corrected author contact info. 1532 15 January 2002 - draft-fleming-ldap-printer-schema-00.txt 1533 - Reissued as individual contribution after withdrawing this document 1534 as an IETF IPP WG product; 1535 - Technical content entirely unchanged from previous version; 1536 - Corrected author contact info. 1538 28 August 2001 - draft-ietf-ipp-ldap-printer-schema-05.txt 1539 - Changed target Category to Informational (from Proposed Standard), 1540 per comments from Kurt Zeilenga and Patrik Faltstrom; 1541 - Added section 6 'Definition of Matching Rules'; 1542 - Corrected minor typos; 1543 - Corrected various RFC and IANA references. 1545 20 December 2000 - draft-ietf-ipp-ldap-printer-schema-04.txt 1546 - Assigned complete OIDs (in IBM managed LDAP OID tree) to all new 1547 LDAP schema and LDAP attribute types defined in this document; 1548 - Corrected author contact info; 1549 - Corrected various RFC references. 1551 4 August 2000 - draft-ietf-ipp-ldap-printer-schema-03.txt 1552 - Minor changes from IETF IPP WG review. 1554 29 June 2000 - draft-ietf-ipp-ldap-printer-schema-02.txt 1555 - Minor changes from IETF IPP WG review. 1557 27 April 2000 - draft-ietf-ipp-ldap-printer-schema-01.txt 1558 - Minor changes from IETF IPP WG review and feedback from IETF 47. 1560 8 March 2000 - draft-ietf-ipp-ldap-printer-schema-00.txt 1561 - Initial version - translated from SLP 'service:printer:' v2.0, 1562 following guidelines in RFC 2926.