5. Definition of Syntaxes No new attribute syntaxes are defined by this document. The attribute types defined in Section 4 of this document reference syntax OIDs defined in Section 3 of [RFC4517], which are summarized below: Syntax OID Syntax Description ------------------------------ ------------------------------- 188.8.131.52.4.1.14184.108.40.206.7 Boolean 220.127.116.11.4.1.1418.104.22.168.15 DirectoryString (UTF-8 [STD63]) 22.214.171.124.4.1.14126.96.36.199.27 Integer 6. Definition of Matching Rules No new matching rules are defined by this document. The attribute types defined in Section 4 of this document reference matching rules defined in Section 4 of [RFC4517], which are summarized below: Matching Rule OID Matching Rule Name Usage ----------------------------- ------------------ -------- 188.8.131.52 booleanMatch EQUALITY 184.108.40.206 caseIgnoreMatch EQUALITY 220.127.116.11 integerMatch EQUALITY 18.104.22.168 integerOrderingMatch ORDERING 22.214.171.124 caseIgnoreSubstringsMatch SUBSTR 7. IANA Considerations This document does not define any new syntaxes or matching rules. This document defines a few new attribute types that have been registered by IANA per this document (see Section 7.1 below). All of the object classes and most of the attribute types described in this document were registered by IANA when RFC 3712 was published (see Section 7.2 below).
7.1. Registration of Attribute Types The following Attribute Type OIDs have been assigned by the IEEE-ISTO PWG (see Section 1.3.2) and have been registered by IANA. Subject: Request for Object Identifier Descriptor Registration Descriptor (short name): see table below Object Identifier: see table below Person & email address to contact for further information: see below Usage: attribute type Specification: RFC 7612 (this document) Author/Change Controller: Ira McDonald High North Inc. 221 Ridge Ave. Grand Marais, MI 49839 United States Phone: +1 906-494-2434 Email: firstname.lastname@example.org Comments: Attribute Type OID ------------------------------------ ---------------------- printer-device-id 126.96.36.199.188.8.131.52.101 printer-device-service-count 184.108.40.206.220.127.116.11.102 printer-uuid 18.104.22.168.22.214.171.124.104 printer-charge-info 126.96.36.199.188.8.131.52.105 printer-charge-info-uri 184.108.40.206.220.127.116.11.106 printer-geo-location 18.104.22.168.22.214.171.124.107 printer-ipp-features-supported 126.96.36.199.188.8.131.52.108
7.2. Object Classes and Attribute Types from RFC 3712 This section is strictly informative. None of the LDAP OIDs listed in this section have been re-registered by IANA. The following Object Class OIDs were assigned by IBM (see Section 1.3.1) and were already registered by IANA when RFC 3712 was published. Object Class OID ------------------------------------ ---------------- slpServicePrinter 184.108.40.206.2.6.254 printerAbstract 220.127.116.11.2.6.258 printerService 18.104.22.168.2.6.255 printerServiceAuxClass 22.214.171.124.2.6.257 printerIPP 126.96.36.199.2.6.256 printerLPR 188.8.131.52.2.6.253 The following Attribute Type OIDs were assigned by IBM (see Section 1.3.1) and were already registered by IANA when RFC 3712 was published. Attribute Type OID ------------------------------------ ----------------- printer-uri 184.108.40.206.2.4.1140 printer-xri-supported 220.127.116.11.2.4.1107 printer-name 18.104.22.168.2.4.1135 printer-natural-language-configured 22.214.171.124.2.4.1119 printer-location 126.96.36.199.2.4.1136 printer-info 188.8.131.52.2.4.1139 printer-more-info 184.108.40.206.2.4.1134 printer-make-and-model 220.127.116.11.2.4.1138 printer-ipp-versions-supported 18.104.22.168.2.4.1133 printer-multiple-document-jobs-supported 22.214.171.124.2.4.1132 printer-charset-configured 126.96.36.199.2.4.1109 printer-charset-supported 188.8.131.52.2.4.1131 printer-generated-natural-language-supported 184.108.40.206.2.4.1137 printer-document-format-supported 220.127.116.11.2.4.1130 printer-color-supported 18.104.22.168.2.4.1129 printer-compression-supported 22.214.171.124.2.4.1128 printer-pages-per-minute 126.96.36.199.2.4.1127 printer-pages-per-minute-color 188.8.131.52.2.4.1126 printer-finishings-supported 184.108.40.206.2.4.1125 printer-number-up-supported 220.127.116.11.2.4.1124 printer-sides-supported 18.104.22.168.2.4.1123 printer-media-supported 22.214.171.124.2.4.1122 printer-media-local-supported 126.96.36.199.2.4.1117 printer-resolution-supported 188.8.131.52.2.4.1121
printer-print-quality-supported 184.108.40.206.2.4.1120 printer-job-priority-supported 220.127.116.11.2.4.1110 printer-copies-supported 18.104.22.168.2.4.1118 printer-job-k-octets-supported 22.214.171.124.2.4.1111 printer-current-operator 126.96.36.199.2.4.1112 printer-service-person 188.8.131.52.2.4.1113 printer-delivery-orientation-supported 184.108.40.206.2.4.1114 printer-stacking-order-supported 220.127.116.11.2.4.1115 printer-output-features-supported 18.104.22.168.2.4.1116 printer-aliases 22.214.171.124.2.4.1108 8. Internationalization Considerations All text string attributes defined in this document of syntax 'DirectoryString' [RFC4517] have values that are encoded in UTF-8 [STD63], as required by [RFC4517]. A language tag [BCP47] for all of the text string attributes defined in this document is contained in the printer-natural-language-configured attribute. Therefore, all object classes defined in this document conform to the IETF Policy on Character Sets and Languages [BCP18]. Note: For interoperability and consistent text display, values of attributes defined in this document (a) SHOULD be normalized as recommended in "Unicode Format for Network Interchange" [RFC5198]; (b) SHOULD NOT contain DEL or any C0 or C1 control characters except for HT, CR, and LF; (c) SHOULD only contain CR and LF characters together (not as singletons); and (d) SHOULD NOT contain HT, CR, or LF characters in names, e.g., printer-name and printer-aliases. 9. Security Considerations See [RFC4513] for detailed guidance on authentication methods for LDAP and the use of TLS/1.2 [RFC5246] to supply connection confidentiality and data integrity for LDAP sessions. As with any LDAP schema, it is important to protect specific entries and attributes with the appropriate access control. It is particularly important that only administrators can modify entries defined in this LDAP Printer schema. Otherwise, an LDAP client might be fooled into diverting print service requests from the original Printer (or spooler) to a malicious intruder's host system, thus exposing the information in printed documents.
Note: Security vulnerabilities can arise if DEL or any C0 or C1 control characters are included in names, e.g., printer-name or printer-aliases. For additional security considerations regarding deploying Printers in an IPP environment, see Section 8 of [RFC2911]. 10. References 10.1. Normative References [BCP47] Phillips, A. and M. Davis, "Matching of Language Tags", BCP 47, RFC 4647, September 2006. Phillips, A., Ed., and M. Davis, Ed., "Tags for Identifying Languages", BCP 47, RFC 5646, September 2009. <http://www.rfc-editor.org/info/bcp47> [IANACHAR] Internet Assigned Numbers Authority (IANA) registry "Character Sets", <http://www.iana.org/assignments/character-sets>. [IANAIPP] Internet Assigned Numbers Authority (IANA) registry "Internet Printing Protocol (IPP) Registrations", <http://www.iana.org/assignments/ipp-registrations>. [IANAMIME] Internet Assigned Numbers Authority (IANA) registry "Media Types", <http://www.iana.org/assignments/ media-types/index.html>. [PWG5100.5] Carney, D., Hastings, T., and P. Zehler, "IPP Document Object", PWG 5100.5-2003, October 2003, <http://www.pwg.org/standards.html>. [PWG5100.6] Zehler, P., Herriot, R., and K. Ocke, "IPP Page Overrides", PWG 5100.6-2003, October 2003, <http://www.pwg.org/standards.html>. [PWG5100.11] Hastings, T. and D. Fullman, "IPP Job and Printer Extensions - Set 2 (JPS2)", PWG 5100.11-2010, October 2010, <http://www.pwg.org/standards.html>. [PWG5100.12] Bergman, R., Lewis, H., McDonald, I., and M. Sweet, "IPP Version 2.0 Second Edition (IPP/2.0 SE)", PWG 5100.12-2011, February 2011, <http://www.pwg.org/standards.html>.
[PWG5100.13] Sweet, M., McDonald, I., and P. Zehler, "IPP Job and Printer Extensions - Set 3 (JPS3)", PWG 5100.13-2012, July 2012, <http://www.pwg.org/standards.html>. [PWG5100.14] Sweet, M., McDonald, I., Mitchell, A., and J. Hutchings, "IPP Everywhere", PWG 5100.14-2013, January 2013, <http://www.pwg.org/standards.html>. [PWG5101.1] Sweet, M., Bergman, R., and T. Hastings, "PWG Media Standardized Names 2.0 (MSN2)", PWG 5101.1-2013, March 2013, <http://www.pwg.org/standards.html>. [PWG5107.2] McDonald, I., "PWG Command Set Format for IEEE 1284 Device ID v1.0", PWG 5107.2-2010, May 2010, <http://www.pwg.org/standards.html>. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <http://www.rfc-editor.org/info/rfc2119>. [RFC2617] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., Leach, P., Luotonen, A., and L. Stewart, "HTTP Authentication: Basic and Digest Access Authentication", RFC 2617, DOI 10.17487/RFC2617, June 1999, <http://www.rfc-editor.org/info/rfc2617>. [RFC2707] Bergman, R., Hastings, T., Isaacson, S., and H. Lewis, "Job Monitoring MIB - V1.0", RFC 2707, DOI 10.17487/RFC2707, November 1999, <http://www.rfc-editor.org/info/rfc2707>. [RFC2911] Hastings, T., Ed., Herriot, R., deBry, R., Isaacson, S., and P. Powell, "Internet Printing Protocol/1.1: Model and Semantics", RFC 2911, DOI 10.17487/RFC2911, September 2000, <http://www.rfc-editor.org/info/rfc2911>. [RFC2926] Kempf, J., Moats, R., and P. St. Pierre, "Conversion of LDAP Schemas to and from SLP Templates", RFC 2926, DOI 10.17487/RFC2926, September 2000, <http://www.rfc-editor.org/info/rfc2926>. [RFC3510] Herriot, R. and I. McDonald, "Internet Printing Protocol/1.1: IPP URL Scheme", RFC 3510, DOI 10.17487/RFC3510, April 2003, <http://www.rfc-editor.org/info/rfc3510>.
[RFC3805] Bergman, R., Lewis, H., and I. McDonald, "Printer MIB v2", RFC 3805, DOI 10.17487/RFC3805, June 2004, <http://www.rfc-editor.org/info/rfc3805>. [RFC3987] Duerst, M. and M. Suignard, "Internationalized Resource Identifiers (IRIs)", RFC 3987, DOI 10.17487/RFC3987, January 2005, <http://www.rfc-editor.org/info/rfc3987>. [RFC3995] Herriot, R. and T. Hastings, "Internet Printing Protocol (IPP): Event Notifications and Subscriptions", RFC 3995, DOI 10.17487/RFC3995, March 2005, <http://www.rfc-editor.org/info/rfc3995>. [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally Unique IDentifier (UUID) URN Namespace", RFC 4122, DOI 10.17487/RFC4122, July 2005, <http://www.rfc-editor.org/info/rfc4122>. [RFC4510] Zeilenga, K., Ed., "Lightweight Directory Access Protocol (LDAP): Technical Specification Road Map", RFC 4510, DOI 10.17487/RFC4510, June 2006, <http://www.rfc-editor.org/info/rfc4510>. [RFC4513] Harrison, R., Ed., "Lightweight Directory Access Protocol (LDAP): Authentication Methods and Security Mechanisms", RFC 4513, DOI 10.17487/RFC4513, June 2006, <http://www.rfc-editor.org/info/rfc4513>. [RFC4517] Legg, S., Ed., "Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching Rules", RFC 4517, DOI 10.17487/RFC4517, June 2006, <http://www.rfc-editor.org/info/rfc4517>. [RFC4524] Zeilenga, K., Ed., "COSINE LDAP/X.500 Schema", RFC 4524, DOI 10.17487/RFC4524, June 2006, <http://www.rfc-editor.org/info/rfc4524>. [RFC5198] Klensin, J. and M. Padlipsky, "Unicode Format for Network Interchange", RFC 5198, DOI 10.17487/RFC5198, March 2008, <http://www.rfc-editor.org/info/rfc5198>. [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security (TLS) Protocol Version 1.2", RFC 5246, DOI 10.17487/RFC5246, August 2008, <http://www.rfc-editor.org/info/rfc5246>.
[RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S., Housley, R., and W. Polk, "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile", RFC 5280, DOI 10.17487/RFC5280, May 2008, <http://www.rfc-editor.org/info/rfc5280>. [RFC5870] Mayrhofer, A. and C. Spanring, "A Uniform Resource Identifier for Geographic Locations ('geo' URI)", RFC 5870, DOI 10.17487/RFC5870, June 2010, <http://www.rfc-editor.org/info/rfc5870>. [RFC6818] Yee, P., "Updates to the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile", RFC 6818, DOI 10.17487/RFC6818, January 2013, <http://www.rfc-editor.org/info/rfc6818>. [RFC7235] Fielding, R., Ed., and J. Reschke, Ed., "Hypertext Transfer Protocol (HTTP/1.1): Authentication", RFC 7235, DOI 10.17487/RFC7235, June 2014, <http://www.rfc-editor.org/info/rfc7235>. [RFC7472] McDonald, I. and M. Sweet, "Internet Printing Protocol (IPP) over HTTPS Transport Binding and the 'ipps' URI Scheme", RFC 7472, DOI 10.17487/RFC7472, March 2015, <http://www.rfc-editor.org/info/rfc7472>. [STD63] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, November 2003, <http://www.rfc-editor.org/info/std63>. [STD66] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005, <http://www.rfc-editor.org/info/std66>.
10.2. Informative References [BCP13] Freed, N. and J. Klensin, "Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures", BCP 13, RFC 4289, December 2005. Freed, N., Klensin, J., and T. Hansen, "Media Type Specifications and Registration Procedures", BCP 13, RFC 6838, January 2013. <http://www.rfc-editor.org/info/bcp13> [BCP18] Alvestrand, H., "IETF Policy on Character Sets and Languages", BCP 18, RFC 2277, January 1998, <http://www.rfc-editor.org/info/bcp18>. [BCP19] Freed, N. and J. Postel, "IANA Charset Registration Procedures", BCP 19, RFC 2978, October 2000, <http://www.rfc-editor.org/info/bcp19>. [RFC1179] McLaughlin, L., "Line printer daemon protocol", RFC 1179, DOI 10.17487/RFC1179, August 1990, <http://www.rfc-editor.org/info/rfc1179>. [RFC1951] Deutsch, P., "DEFLATE Compressed Data Format Specification version 1.3", RFC 1951, DOI 10.17487/RFC1951, May 1996, <http://www.rfc-editor.org/info/rfc1951>. [RFC1952] Deutsch, P., "GZIP file format specification version 4.3", RFC 1952, DOI 10.17487/RFC1952, May 1996, <http://www.rfc-editor.org/info/rfc1952>. [RFC1977] Schryver, V., "PPP BSD Compression Protocol", RFC 1977, DOI 10.17487/RFC1977, August 1996, <http://www.rfc-editor.org/info/rfc1977>. [RFC2079] Smith, M., "Definition of an X.500 Attribute Type and an Object Class to Hold Uniform Resource Identifiers (URIs)", RFC 2079, DOI 10.17487/RFC2079, January 1997, <http://www.rfc-editor.org/info/rfc2079>. [RFC2566] deBry, R., Hastings, T., Herriot, R., Isaacson, S., and P. Powell, "Internet Printing Protocol/1.0: Model and Semantics", RFC 2566, DOI 10.17487/RFC2566, April 1999, <http://www.rfc-editor.org/info/rfc2566>.
[RFC2608] Guttman, E., Perkins, C., Veizades, J., and M. Day, "Service Location Protocol, Version 2", RFC 2608, DOI 10.17487/RFC2608, June 1999, <http://www.rfc-editor.org/info/rfc2608>. [RFC3712] Fleming, P. and I. McDonald, "Lightweight Directory Access Protocol (LDAP): Schema for Printer Services", RFC 3712, DOI 10.17487/RFC3712, February 2004, <http://www.rfc-editor.org/info/rfc3712>. [RFC4559] Jaganathan, K., Zhu, L., and J. Brezak, "SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft Windows", RFC 4559, DOI 10.17487/RFC4559, June 2006, <http://www.rfc-editor.org/info/rfc4559>. [SLPPRT20] IANA, "Service Location Protocol, Version 2 (SLPv2) Templates", <http://www.iana.org/assignments/svrloc-templates>.
Appendix A. Changes since RFC 3712 1) Added many editorial corrections and clarifications - corrected typos, missing words, and ambiguous sentences; - replaced lowercase 'printer' with titlecase 'Printer' for readability and consistency with IETF and IEEE-ISTO PWG IPP standards usage; - added implementation notes; - updated and added references. 2) Deleted length restrictions from formal definitions of DirectoryString syntax attributes - replaced with notes recommending length restrictions for compatibility with existing implementations of [RFC3712] and underlying string length limits in [RFC2707], [RFC2911], [RFC3805], [PWG5107.2], [PWG5100.13], and [PWG5100.14]. 3) Added new Printer attributes defined in [PWG5107.2], [PWG5100.13], and [PWG5100.14] (see Section 7.1) - updated the table of Printer attributes and source documents in Section 4 ("Definition of Attribute Types"); - added support for IEEE-ISTO PWG "IPP Everywhere" [PWG5100.14] project. 4) Added implementation note to Section 4 about string encodings - added discussion of 'List of xxx' and 'One of xxx' encodings; - stated that any of these attributes can be represented as multiple instances (i.e., to avoid length overflow). 5) Improved comma-delimited examples of string attributes - added both single-valued and multi-valued examples.
6) Clarified use of printer-xri-supported and printer-resolution-supported attributes, and their corresponding field delimiters - added note in Section 4 ("Definition of Attribute Types") to explain the origin of the different field delimiters; - added examples to show optional *trailing* whitespace after '<' delimiters in printer-xri-supported; - added examples to show optional *trailing* whitespace after '>' delimiters in printer-resolution-supported. 7) Clarified Section 8 ("Internationalization Considerations") - added note about Net-Unicode [RFC5198] and avoiding use of C0 and C1 control characters. 8) Clarified Section 9 ("Security Considerations") - added note about security vulnerabilities caused by use of DEL or any C0 or C1 control characters in names. 9) Clarified terms and abbreviations - renamed Section 2 ("Conventions Used in This Document"); - added Section 2.1 ("Requirements Language"); - added Section 2.2 ("LDAP Schema Descriptions"); - added Section 2.3 ("Abbreviations").
Acknowledgments The authors wish to acknowledge significant contributions from Ken Jones and Harry Lewis and excellent comments from Patrik Faltstrom, Ryan Moats, Robert Moore, Lee Rafalow, Kimberly Reger, and Kurt Zeilenga during the development of the original LDAP Printer schema [RFC3712]. The authors wish to acknowledge excellent comments from Nevil Brownlee, Barry Leiba, Alexey Melnikov, Tom Petch, and Mike Sweet during the development of this current version of the LDAP Printer schema. Thanks to the members of the IEEE-ISTO PWG IPP Working Group, for their review comments and help in preparing this document. Authors' Addresses Pat Fleming Independent 51796 171 Ave. Pine Island, MN 55963 United States Phone: +1 507-356-8277 Email: email@example.com Ira McDonald High North Inc. 221 Ridge Ave. Grand Marais, MI 49839 United States Phone: +1 906-494-2434 Email: firstname.lastname@example.org