<pre>Independent Submission                                        P. Fleming
Request for Comments: 7612                                   Independent
Obsoletes: <a href="./rfc3712">3712</a>                                              I. McDonald
Category: Informational                                       High North
ISSN: 2070-1721                                                June 2015


             <span class="h1">Lightweight Directory Access Protocol (LDAP):</span>
                      <span class="h1">Schema for Printer Services</span>

Abstract

   This document defines a schema, object classes, and attributes, for
   Printers and print services, for use with directories that support
   the Lightweight Directory Access Protocol (<a href="./rfc4510">RFC 4510</a>).  This document
   is based on the Printer attributes listed in <a href="#appendix-E">Appendix E</a> of "Internet
   Printing Protocol/1.1: Model and Semantics" (<a href="./rfc2911">RFC 2911</a>).  Additional
   Printer attributes are based on definitions in "Printer MIB v2" (<a href="./rfc3805">RFC</a>
   <a href="./rfc3805">3805</a>), "PWG Command Set Format for IEEE 1284 Device ID v1.0" (PWG
   5107.2), "IPP Job and Printer Extensions - Set 3 (JPS3)" (PWG
   5100.13), and "IPP Everywhere" (PWG 5100.14).

   This memo is an Independent Submission to the RFC Editor by the
   Internet Printing Protocol (IPP) Working Group of the IEEE-ISTO
   Printer Working Group (PWG), as part of their PWG "IPP Everywhere"
   (PWG 5100.14) project for secure mobile printing with vendor-neutral
   Client software.

   This document obsoletes <a href="./rfc3712">RFC 3712</a>.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This is a contribution to the RFC Series, independently of any other
   RFC stream.  The RFC Editor has chosen to publish this document at
   its discretion and makes no statement about its value for
   implementation or deployment.  Documents approved for publication by
   the RFC Editor are not a candidate for any level of Internet
   Standard; see <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   <a href="http://www.rfc-editor.org/info/rfc7612">http://www.rfc-editor.org/info/rfc7612</a>.






<span class="grey">Fleming &amp; McDonald            Informational                     [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.

Table of Contents

   <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-4">4</a>
      <a href="#section-1.1">1.1</a>. Relationship to SLP Printer Service ........................<a href="#page-4">4</a>
      <a href="#section-1.2">1.2</a>. Source of LDAP Printer Attributes ..........................<a href="#page-4">4</a>
      <a href="#section-1.3">1.3</a>. Source of LDAP Printer Schema OIDs .........................<a href="#page-5">5</a>
           <a href="#section-1.3.1">1.3.1</a>. IBM Assignments for <a href="./rfc3712">RFC 3712</a> ........................<a href="#page-5">5</a>
           <a href="#section-1.3.2">1.3.2</a>. IEEE-ISTO PWG Assignments ...........................<a href="#page-5">5</a>
      <a href="#section-1.4">1.4</a>. Rationale for Design Choices ...............................<a href="#page-5">5</a>
           <a href="#section-1.4.1">1.4.1</a>. Rationale for Using DirectoryString Syntax ..........<a href="#page-5">5</a>
           <a href="#section-1.4.2">1.4.2</a>. Rationale for Using caseIgnoreMatch .................<a href="#page-6">6</a>
           <a href="#section-1.4.3">1.4.3</a>. Rationale for Using caseIgnoreSubstringsMatch .......<a href="#page-7">7</a>
   <a href="#section-2">2</a>. Conventions Used in This Document ...............................<a href="#page-8">8</a>
      <a href="#section-2.1">2.1</a>. Requirements Language ......................................<a href="#page-8">8</a>
      <a href="#section-2.2">2.2</a>. LDAP Schema Descriptions ...................................<a href="#page-8">8</a>
      <a href="#section-2.3">2.3</a>. Abbreviations ..............................................<a href="#page-8">8</a>
   <a href="#section-3">3</a>. Definition of Object Classes ....................................<a href="#page-9">9</a>
      <a href="#section-3.1">3.1</a>. slpServicePrinter .........................................<a href="#page-10">10</a>
      <a href="#section-3.2">3.2</a>. printerAbstract ...........................................<a href="#page-10">10</a>
      <a href="#section-3.3">3.3</a>. printerService ............................................<a href="#page-11">11</a>
      <a href="#section-3.4">3.4</a>. printerServiceAuxClass ....................................<a href="#page-12">12</a>
      <a href="#section-3.5">3.5</a>. printerIPP ................................................<a href="#page-12">12</a>
      <a href="#section-3.6">3.6</a>. printerLPR ................................................<a href="#page-12">12</a>
   <a href="#section-4">4</a>. Definition of Attribute Types ..................................<a href="#page-13">13</a>
      <a href="#section-4.1">4.1</a>. printer-uri ...............................................<a href="#page-15">15</a>
      <a href="#section-4.2">4.2</a>. printer-xri-supported .....................................<a href="#page-16">16</a>
      <a href="#section-4.3">4.3</a>. printer-name ..............................................<a href="#page-18">18</a>
      <a href="#section-4.4">4.4</a>. printer-natural-language-configured .......................<a href="#page-19">19</a>
      <a href="#section-4.5">4.5</a>. printer-location ..........................................<a href="#page-19">19</a>
      <a href="#section-4.6">4.6</a>. printer-info ..............................................<a href="#page-20">20</a>
      <a href="#section-4.7">4.7</a>. printer-more-info .........................................<a href="#page-21">21</a>
      <a href="#section-4.8">4.8</a>. printer-make-and-model ....................................<a href="#page-21">21</a>
      <a href="#section-4.9">4.9</a>. printer-ipp-versions-supported ............................<a href="#page-22">22</a>
      <a href="#section-4.10">4.10</a>. printer-multiple-document-jobs-supported .................<a href="#page-23">23</a>
      <a href="#section-4.11">4.11</a>. printer-charset-configured ...............................<a href="#page-23">23</a>
      <a href="#section-4.12">4.12</a>. printer-charset-supported ................................<a href="#page-24">24</a>



<span class="grey">Fleming &amp; McDonald            Informational                     [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


      <a href="#section-4.13">4.13</a>. printer-generated-natural-language-supported .............<a href="#page-24">24</a>
      <a href="#section-4.14">4.14</a>. printer-document-format-supported ........................<a href="#page-25">25</a>
      <a href="#section-4.15">4.15</a>. printer-color-supported ..................................<a href="#page-25">25</a>
      <a href="#section-4.16">4.16</a>. printer-compression-supported ............................<a href="#page-26">26</a>
      <a href="#section-4.17">4.17</a>. printer-pages-per-minute .................................<a href="#page-26">26</a>
      <a href="#section-4.18">4.18</a>. printer-pages-per-minute-color ...........................<a href="#page-27">27</a>
      <a href="#section-4.19">4.19</a>. printer-finishings-supported .............................<a href="#page-27">27</a>
      <a href="#section-4.20">4.20</a>. printer-number-up-supported ..............................<a href="#page-28">28</a>
      <a href="#section-4.21">4.21</a>. printer-sides-supported ..................................<a href="#page-28">28</a>
      <a href="#section-4.22">4.22</a>. printer-media-supported ..................................<a href="#page-29">29</a>
      <a href="#section-4.23">4.23</a>. printer-media-local-supported ............................<a href="#page-30">30</a>
      <a href="#section-4.24">4.24</a>. printer-resolution-supported .............................<a href="#page-30">30</a>
      <a href="#section-4.25">4.25</a>. printer-print-quality-supported ..........................<a href="#page-31">31</a>
      <a href="#section-4.26">4.26</a>. printer-job-priority-supported ...........................<a href="#page-32">32</a>
      <a href="#section-4.27">4.27</a>. printer-copies-supported .................................<a href="#page-32">32</a>
      <a href="#section-4.28">4.28</a>. printer-job-k-octets-supported ...........................<a href="#page-33">33</a>
      <a href="#section-4.29">4.29</a>. printer-current-operator .................................<a href="#page-33">33</a>
      <a href="#section-4.30">4.30</a>. printer-service-person ...................................<a href="#page-34">34</a>
      <a href="#section-4.31">4.31</a>. printer-delivery-orientation-supported ...................<a href="#page-34">34</a>
      <a href="#section-4.32">4.32</a>. printer-stacking-order-supported .........................<a href="#page-35">35</a>
      <a href="#section-4.33">4.33</a>. printer-output-features-supported ........................<a href="#page-36">36</a>
      <a href="#section-4.34">4.34</a>. printer-aliases ..........................................<a href="#page-37">37</a>
      <a href="#section-4.35">4.35</a>. printer-device-id ........................................<a href="#page-37">37</a>
      <a href="#section-4.36">4.36</a>. printer-device-service-count .............................<a href="#page-38">38</a>
      <a href="#section-4.37">4.37</a>. printer-uuid .............................................<a href="#page-38">38</a>
      <a href="#section-4.38">4.38</a>. printer-charge-info ......................................<a href="#page-39">39</a>
      <a href="#section-4.39">4.39</a>. printer-charge-info-uri ..................................<a href="#page-39">39</a>
      <a href="#section-4.40">4.40</a>. printer-geo-location .....................................<a href="#page-40">40</a>
      <a href="#section-4.41">4.41</a>. printer-ipp-features-supported ...........................<a href="#page-41">41</a>
   <a href="#section-5">5</a>. Definition of Syntaxes .........................................<a href="#page-42">42</a>
   <a href="#section-6">6</a>. Definition of Matching Rules ...................................<a href="#page-42">42</a>
   <a href="#section-7">7</a>. IANA Considerations ............................................<a href="#page-42">42</a>
      <a href="#section-7.1">7.1</a>. Registration of Attribute Types ...........................<a href="#page-43">43</a>
      <a href="#section-7.2">7.2</a>. Object Classes and Attribute Types from <a href="./rfc3712">RFC 3712</a> ..........<a href="#page-44">44</a>
   <a href="#section-8">8</a>. Internationalization Considerations ............................<a href="#page-45">45</a>
   <a href="#section-9">9</a>. Security Considerations ........................................<a href="#page-45">45</a>
   <a href="#section-10">10</a>. References ....................................................<a href="#page-46">46</a>
      <a href="#section-10.1">10.1</a>. Normative References .....................................<a href="#page-46">46</a>
      <a href="#section-10.2">10.2</a>. Informative References ...................................<a href="#page-50">50</a>
   <a href="#appendix-A">Appendix A</a>. Changes since <a href="./rfc3712">RFC 3712</a> ................................<a href="#page-52">52</a>
   Acknowledgments ...................................................<a href="#page-54">54</a>
   Authors' Addresses ................................................<a href="#page-54">54</a>









<span class="grey">Fleming &amp; McDonald            Informational                     [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   This document defines several object classes to provide Lightweight
   Directory Access Protocol (LDAP) [<a href="./rfc4510" title="&quot;Lightweight Directory Access Protocol (LDAP): Technical Specification Road Map&quot;">RFC4510</a>] applications with flexible
   options in defining Printer information using an LDAP schema.
   Classes are provided for defining directory entries with common
   Printer information as well as for extending existing directory
   entries with Service Location Protocol Version 2 (SLPv2) [<a href="./rfc2608" title="&quot;Service Location Protocol, Version 2&quot;">RFC2608</a>],
   Internet Printing Protocol/1.1 (IPP/1.1) [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], and lineprinter
   (LPR) [<a href="./rfc1179" title="&quot;Line printer daemon protocol&quot;">RFC1179</a>] protocol-specific information.

   This memo is an Independent Submission to the RFC Editor by the
   Internet Printing Protocol Working Group of the IEEE-ISTO Printer
   Working Group, as part of their Printer Working Group (PWG) "IPP
   Everywhere" (PWG 5100.14) project for secure mobile printing with
   vendor-neutral Client software.

<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>.  Relationship to SLP Printer Service</span>

   The schema defined in this document is technically aligned with the
   stable IANA-registered 'service:printer:' v2.0 template [<a href="#ref-SLPPRT20" title="&quot;Service Location Protocol, Version 2 (SLPv2) Templates&quot;">SLPPRT20</a>],
   for compatibility with already-deployed SLPv2 [<a href="./rfc2608" title="&quot;Service Location Protocol, Version 2&quot;">RFC2608</a>] service
   advertising and discovery infrastructure.  The attribute syntaxes are
   technically aligned with the 'service:printer:' v2.0 template;
   therefore, simpler types are sometimes used (for example,
   'DirectoryString' [<a href="./rfc4517" title="&quot;Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching Rules&quot;">RFC4517</a>] rather than 'labeledURI' [<a href="./rfc2079" title="&quot;Definition of an X.500 Attribute Type and an Object Class to Hold Uniform Resource Identifiers (URIs)&quot;">RFC2079</a>] for
   the 'printer-uri' attribute).

<span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>.  Source of LDAP Printer Attributes</span>

   The schema defined in this document is based on:

   o  all of the Printer attributes listed in <a href="#appendix-E">Appendix E</a> ("Generic
      Directory Schema") of "Internet Printing Protocol/1.1: Model and
      Semantics" [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>] that are defined in <a href="#section-4.4">Section 4.4</a> ("Printer
      Description Attributes") of [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>]

   o  selected Printer attributes defined in "Printer MIB v2" [<a href="./rfc3805" title="&quot;Printer MIB v2&quot;">RFC3805</a>],
      "PWG Command Set for IEEE 1284 Device ID v1.0" [<a href="#ref-PWG5107.2" title="&quot;PWG Command Set Format for IEEE 1284 Device ID v1.0&quot;">PWG5107.2</a>], "IPP
      Job and Printer Extensions - Set 3 (JPS3)" [<a href="#ref-PWG5100.13" title="&quot;IPP Job and Printer Extensions - Set 3 (JPS3)&quot;">PWG5100.13</a>], and "IPP
      Everywhere" [<a href="#ref-PWG5100.14" title="&quot;IPP Everywhere&quot;">PWG5100.14</a>]

   See the table of Printer attributes and source documents in <a href="#section-4">Section 4</a>
   ("Definition of Attribute Types") of this document.







<span class="grey">Fleming &amp; McDonald            Informational                     [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h3"><a class="selflink" id="section-1.3" href="#section-1.3">1.3</a>.  Source of LDAP Printer Schema OIDs</span>

<span class="h4"><a class="selflink" id="section-1.3.1" href="#section-1.3.1">1.3.1</a>.  IBM Assignments for <a href="./rfc3712">RFC 3712</a></span>

   In March 2000, IBM permanently assigned ASN.1 OIDs to all of the
   object classes and attribute types that were defined in the original
   LDAP Printer Schema [<a href="./rfc3712" title="&quot;Lightweight Directory Access Protocol (LDAP): Schema for Printer Services&quot;">RFC3712</a>] (see <a href="#section-7.2">Section 7.2</a>).

<span class="h4"><a class="selflink" id="section-1.3.2" href="#section-1.3.2">1.3.2</a>.  IEEE-ISTO PWG Assignments</span>

   In October 2011, IBM permanently delegated the base ASN.1 OID
   "1.3.18.0.2.24.46" to the IEEE-ISTO PWG for use in any PWG project.
   In October 2011, the IEEE-ISTO PWG permanently assigned subordinate
   ASN.1 OIDs for all of the new attribute types defined in this updated
   LDAP Printer Schema (see <a href="#section-7.1">Section 7.1</a>).

<span class="h3"><a class="selflink" id="section-1.4" href="#section-1.4">1.4</a>.  Rationale for Design Choices</span>

<span class="h4"><a class="selflink" id="section-1.4.1" href="#section-1.4.1">1.4.1</a>.  Rationale for Using DirectoryString Syntax</span>

   The attribute syntax 'DirectoryString' (UTF-8 [<a href="#ref-STD63" title="&quot;UTF-8, a transformation format of ISO 10646&quot;">STD63</a>]) defined in
   [<a href="./rfc4517" title="&quot;Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching Rules&quot;">RFC4517</a>] is specified for several groups of string attributes that
   are defined in this document:

   1) URI

      - printer-uri, printer-xri-supported, printer-more-info,
        printer-charge-info-uri, printer-uuid

        The UTF-8 encoding is compatible with deployment of (UTF-8
        based) Internationalized Resource Identifiers (IRIs) [<a href="./rfc3987" title="&quot;Internationalized Resource Identifiers (IRIs)&quot;">RFC3987</a>].

   2) Description

      - printer-name, printer-location, printer-info,
        printer-make-and-model

        The UTF-8 encoding supports descriptions in any language,
        conformant with the IETF Policy on Character Sets and Languages
        [<a href="#ref-BCP18" title="&quot;IETF Policy on Character Sets and Languages&quot;">BCP18</a>].

        Note: The printer-natural-language-configured attribute contains
        a language tag [<a href="#ref-BCP47" title="&quot;Matching of Language Tags&quot;">BCP47</a>] for these description attributes (for
        example, to support text-to-speech conversions).







<span class="grey">Fleming &amp; McDonald            Informational                     [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


   3) Keyword

      - printer-compression-supported, printer-finishings-supported,
        printer-media-supported, printer-media-local-supported,
        printer-print-quality-supported

        The UTF-8 encoding is compatible with the current IPP/1.1
        [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>] definition of the equivalent attributes, most of which
        have the IPP/1.1 union syntax 'keyword' or 'name'.  The keyword
        attributes defined in this document are extensible by site-
        specific or vendor-specific 'names' that behave like new
        'keywords'.

        Note: In IPP/1.1, each value is strongly typed over-the-wire as
        either 'keyword' or 'name'.  This union selector is not
        preserved in the definitions of these equivalent LDAP
        attributes.

<span class="h4"><a class="selflink" id="section-1.4.2" href="#section-1.4.2">1.4.2</a>.  Rationale for Using caseIgnoreMatch</span>

   The EQUALITY matching rule 'caseIgnoreMatch' defined in [<a href="./rfc4517" title="&quot;Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching Rules&quot;">RFC4517</a>] is
   specified for several groups of string attributes that are defined in
   this document:

   1) URI

      These URI attributes specify EQUALITY matching with
      'caseIgnoreMatch' (rather than with 'caseExactMatch') in order to
      conform to the spirit of [<a href="#ref-STD66" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">STD66</a>], which requires case-insensitive
      matching on the host part of a URI versus case-sensitive matching
      on the remainder of a URI.

      These URI attributes follow existing practice of supporting
      case-insensitive equality matching for host names in the
      associatedDomain attribute defined in [<a href="./rfc4524" title="&quot;COSINE LDAP/X.500 Schema&quot;">RFC4524</a>].

      Either equality matching rule choice would be a compromise:

      a) case-sensitive whole URI matching can lead to false negative
         matches and has been shown to be fragile (given deployed client
         applications that 'pretty up' host names displayed and
         transferred in URI);

      b) case-insensitive whole URI matching can lead to false positive
         matches, although it is a dangerous practice to publish URI
         that differ only by case (for example, in the path elements).





<span class="grey">Fleming &amp; McDonald            Informational                     [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


   2) Description

      Case-insensitive equality matching is more user-friendly for
      description attributes.

   3) Keyword

      Case-insensitive equality matching is more user-friendly for
      keyword attributes.

   4) IEEE 1284 Device ID

      Case-insensitive equality matching is mandatory for IEEE 1284
      Device ID attributes.

<span class="h4"><a class="selflink" id="section-1.4.3" href="#section-1.4.3">1.4.3</a>.  Rationale for Using caseIgnoreSubstringsMatch</span>

   The SUBSTR matching rule 'caseIgnoreSubstringsMatch' defined in
   [<a href="./rfc4517" title="&quot;Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching Rules&quot;">RFC4517</a>] is specified for several groups of string attributes that
   are defined in this document:

   1) URI

      These URI attributes follow existing practice of supporting
      case-insensitive equality matching for host names in the
      associatedDomain attribute defined in [<a href="./rfc4524" title="&quot;COSINE LDAP/X.500 Schema&quot;">RFC4524</a>].

   2) Description

      Support for case-insensitive substring matching is more
      user-friendly for description attributes.

   3) Keyword

      Support for case-insensitive substring matching is more
      user-friendly for keyword attributes.

   4) IEEE 1284 Device ID

      Support for case-insensitive substring matching is mandatory for
      IEEE 1284 Device ID attributes.










<span class="grey">Fleming &amp; McDonald            Informational                     [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Conventions Used in This Document</span>

<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>.  Requirements Language</span>

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].

<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>.  LDAP Schema Descriptions</span>

   Schema definitions are provided using LDAP [<a href="./rfc4510" title="&quot;Lightweight Directory Access Protocol (LDAP): Technical Specification Road Map&quot;">RFC4510</a>] description
   formats.  Definitions provided here are formatted (line wrapped) for
   readability.

<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>.  Abbreviations</span>

   This document makes use of the following abbreviations (given with
   their expanded forms and references for further reading):

   IANA   - Internet Assigned Numbers Authority
            &lt;<a href="http://www.iana.org">http://www.iana.org</a>&gt;

   IEEE   - Institute of Electrical and Electronics Engineers
            &lt;<a href="http://www.ieee.org">http://www.ieee.org</a>&gt;

   IPP    - Internet Printing Protocol [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>] [<a href="#ref-PWG5100.12" title="&quot;IPP Version 2.0 Second Edition (IPP/2.0 SE)&quot;">PWG5100.12</a>]
            &lt;<a href="http://www.pwg.org/ipp/">http://www.pwg.org/ipp/</a>&gt;

   ISTO   - IEEE Industry Standards and Technology Organization
            &lt;<a href="http://www.ieee-isto.org/">http://www.ieee-isto.org/</a>&gt;

   PWG    - IEEE-ISTO Printer Working Group
            &lt;<a href="http://www.pwg.org">http://www.pwg.org</a>&gt;

   RFC    - Request for Comments
            &lt;<a href="http://www.rfc-editor.org">http://www.rfc-editor.org</a>&gt;

   TLS    - Transport Layer Security [<a href="./rfc5246" title="&quot;The Transport Layer Security (TLS) Protocol Version 1.2&quot;">RFC5246</a>]

   URI    - Uniform Resource Identifier [<a href="#ref-STD66" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">STD66</a>]

   URL    - Uniform Resource Locator [<a href="#ref-STD66" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">STD66</a>]

   UTF-8  - Unicode Transformation Format - 8-bit [<a href="#ref-STD63" title="&quot;UTF-8, a transformation format of ISO 10646&quot;">STD63</a>]







<span class="grey">Fleming &amp; McDonald            Informational                     [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  Definition of Object Classes</span>

   We define the following LDAP object classes for use with both generic
   Printer-related information and services specific to SLPv2 [<a href="./rfc2608" title="&quot;Service Location Protocol, Version 2&quot;">RFC2608</a>],
   IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], and LPR [<a href="./rfc1179" title="&quot;Line printer daemon protocol&quot;">RFC1179</a>].

      slpServicePrinter - auxiliary class for SLP-registered Printers
      printerAbstract - abstract class for all Printer classes
      printerService - structural class for Printers
      printerServiceAuxClass - auxiliary class for Printers
      printerIPP - auxiliary class for IPP Printers
      printerLPR - auxiliary class for LPR Printers

   The following are some examples of how applications could choose to
   use these classes when creating directory entries:

   1) Use printerService for directory entries containing common Printer
      information.

   2) Use both printerService and slpServicePrinter for directory
      entries containing common Printer information for SLP-registered
      Printers.

   3) Use printerService, printerLPR, and printerIPP for directory
      entries containing common Printer information for Printers that
      support both LPR and IPP.

   4) Use printerServiceAuxClass and object classes not defined by this
      document for directory entries containing common Printer
      information.  In this example, printerServiceAuxClass is used for
      extending other structural classes defining Printer information
      with common Printer information defined in this document.

   Refer to <a href="#section-4">Section 4</a> for the definition of attribute types referenced
   by these object classes.  We use attribute names instead of OIDs in
   object class definitions for clarity.  Some attribute names described
   in [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>] have been prefixed with 'printer-' as recommended in
   [<a href="./rfc2926" title="&quot;Conversion of LDAP Schemas to and from SLP Templates&quot;">RFC2926</a>] and [<a href="#ref-SLPPRT20" title="&quot;Service Location Protocol, Version 2 (SLPv2) Templates&quot;">SLPPRT20</a>].













<span class="grey">Fleming &amp; McDonald            Informational                     [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>.  slpServicePrinter</span>

   ( 1.3.18.0.2.6.254
   NAME  'slpServicePrinter'
   DESC  'Service Location Protocol (SLP) information.'
   AUXILIARY
   SUP   slpService
   )

   This auxiliary class defines information specific to the Service
   Location Protocol (SLPv2) [<a href="./rfc2608" title="&quot;Service Location Protocol, Version 2&quot;">RFC2608</a>].  It MAY be used to create new,
   or extend existing, directory entries with SLP 'service:printer'
   abstract service type information as defined in [<a href="#ref-SLPPRT20" title="&quot;Service Location Protocol, Version 2 (SLPv2) Templates&quot;">SLPPRT20</a>].  This
   object class is derived from 'slpService', the parent class for all
   SLP services, defined in [<a href="./rfc2926" title="&quot;Conversion of LDAP Schemas to and from SLP Templates&quot;">RFC2926</a>].

<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>.  printerAbstract</span>

   ( 1.3.18.0.2.6.258
   NAME  'printerAbstract'
   DESC  'Printer-related information.'
   ABSTRACT
   SUP   top
   MAY   ( printer-name $
           printer-natural-language-configured $
           printer-location $
           printer-info $
           printer-more-info $
           printer-make-and-model $
           printer-multiple-document-jobs-supported $
           printer-charset-configured $
           printer-charset-supported $
           printer-generated-natural-language-supported $
           printer-document-format-supported $
           printer-color-supported $
           printer-compression-supported $
           printer-pages-per-minute $
           printer-pages-per-minute-color $
           printer-finishings-supported $
           printer-number-up-supported $
           printer-sides-supported $
           printer-media-supported $
           printer-media-local-supported $
           printer-resolution-supported $
           printer-print-quality-supported $
           printer-job-priority-supported $
           printer-copies-supported $
           printer-job-k-octets-supported $



<span class="grey">Fleming &amp; McDonald            Informational                    [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


           printer-current-operator $
           printer-service-person $
           printer-delivery-orientation-supported $
           printer-stacking-order-supported $
           printer-output-features-supported $
           printer-device-id $
           printer-device-service-count $
           printer-uuid $
           printer-charge-info $
           printer-charge-info-uri $
           printer-geo-location )
   )

   This abstract class defines Printer information.  It is a base class
   for deriving other Printer-related classes, such as, but not limited
   to, classes defined in this document.  It defines a common set of
   Printer attributes that are not specific to any one type of service,
   protocol, or operating system.

<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>.  printerService</span>

   ( 1.3.18.0.2.6.255
   NAME  'printerService'
   DESC  'Printer information.'
   STRUCTURAL
   SUP   printerAbstract
   MAY   ( printer-uri $
           printer-xri-supported )
   )

   This structural class defines Printer information.  It is derived
   from class printerAbstract and thus inherits common Printer
   attributes.  This class can be used with or without auxiliary classes
   to define Printer information.  Auxiliary classes can be used to
   extend the common Printer information with information specific to
   the protocol, service, or operating system.

   Note: When extending other structural classes with auxiliary classes,
   printerService SHOULD NOT be used.












<span class="grey">Fleming &amp; McDonald            Informational                    [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>.  printerServiceAuxClass</span>

   ( 1.3.18.0.2.6.257
   NAME  'printerServiceAuxClass'
   DESC  'Printer information.'
   AUXILIARY
   SUP   printerAbstract
   MAY   ( printer-uri $
           printer-xri-supported )
   )

   This auxiliary class defines Printer information.  It is derived from
   class printerAbstract and thus inherits common Printer attributes.

<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>.  printerIPP</span>

   ( 1.3.18.0.2.6.256
   NAME  'printerIPP'
   DESC  'Internet Printing Protocol (IPP) information.'
   AUXILIARY
   SUP   top
   MAY   ( printer-ipp-versions-supported $
           printer-ipp-features-supported $
           printer-multiple-document-jobs-supported )
   )

   This auxiliary class defines Internet Printing Protocol (IPP/1.1)
   [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>] information.  It is used to extend structural classes with
   IPP-specific Printer information.

   Note: See "Internet Printing Protocol/1.1: IPP URL Scheme" [<a href="./rfc3510" title="&quot;Internet Printing Protocol/1.1: IPP URL Scheme&quot;">RFC3510</a>]
   and "Internet Printing Protocol (IPP) over HTTPS Transport Binding
   and the 'ipps' URI Scheme" [<a href="./rfc7472" title="&quot;Internet Printing Protocol (IPP) over HTTPS Transport Binding and the 'ipps' URI Scheme&quot;">RFC7472</a>] for conforming URI for IPP
   Printers.

<span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a>.  printerLPR</span>

   ( 1.3.18.0.2.6.253
   NAME  'printerLPR'
   DESC  'LPR information.'
   AUXILIARY
   SUP   top
   MUST  ( printer-name )
   MAY   ( printer-aliases )
   )

   This auxiliary class defines LPR [<a href="./rfc1179" title="&quot;Line printer daemon protocol&quot;">RFC1179</a>] information.  It is used
   to identify directory entries that support LPR.



<span class="grey">Fleming &amp; McDonald            Informational                    [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  Definition of Attribute Types</span>

   The following attribute types are referenced by the object classes
   defined in <a href="#section-3">Section 3</a>.

   The following attribute types reference syntax OIDs defined in
   <a href="./rfc4517#section-3">Section&nbsp;3 of [RFC4517]</a> (see <a href="#section-5">Section 5</a> ("Definition of Syntaxes")
   below).

   The following attribute types reference matching rule names (instead
   of OIDs) for clarity (see <a href="#section-6">Section 6</a> below).  For optional attributes,
   if the Printer information is not known, the attribute value
   SHOULD NOT be set.  In the following definitions, referenced matching
   rules are defined in <a href="./rfc4517#section-4">Section&nbsp;4 of [RFC4517]</a> and discussed in
   <a href="#section-6">Section 6</a> ("Definition of Matching Rules") later in this document.

   Note: For compatibility with existing implementations of [<a href="./rfc3712" title="&quot;Lightweight Directory Access Protocol (LDAP): Schema for Printer Services&quot;">RFC3712</a>]
   and underlying string length limits in [<a href="./rfc2707" title="&quot;Job Monitoring MIB - V1.0&quot;">RFC2707</a>], [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>],
   [<a href="./rfc3805" title="&quot;Printer MIB v2&quot;">RFC3805</a>], [<a href="#ref-PWG5107.2" title="&quot;PWG Command Set Format for IEEE 1284 Device ID v1.0&quot;">PWG5107.2</a>], [<a href="#ref-PWG5100.13" title="&quot;IPP Job and Printer Extensions - Set 3 (JPS3)&quot;">PWG5100.13</a>], and [<a href="#ref-PWG5100.14" title="&quot;IPP Everywhere&quot;">PWG5100.14</a>],
   implementations of the attributes defined in this document SHOULD NOT
   exceed those underlying string length limits (to avoid truncation and
   false matches).

   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" [<a href="./rfc5198" title="&quot;Unicode Format for Network Interchange&quot;">RFC5198</a>];
   (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.

   Note: Some of the following attributes are described as 'List of xxx'
   (using a comma as the member delimiter).  Some other attributes are
   described as 'One of xxx' (single-valued).  In all cases, any
   attribute can have multiple values represented as multiple instances,
   except where explicitly restricted in syntax to be single-valued.

   Note: Values of the string attributes printer-xri-supported and
   printer-resolution-supported use different field delimiters ('&lt;' and
   '&gt;', respectively).  These two field delimiters are different for
   compatibility with the corresponding attributes in the IANA-
   registered SLP 'service:printer:' v2.0 template [<a href="#ref-SLPPRT20" title="&quot;Service Location Protocol, Version 2 (SLPv2) Templates&quot;">SLPPRT20</a>], which was
   defined before the original LDAP Printer Schema [<a href="./rfc3712" title="&quot;Lightweight Directory Access Protocol (LDAP): Schema for Printer Services&quot;">RFC3712</a>] was
   written.







<span class="grey">Fleming &amp; McDonald            Informational                    [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


   The following table is a summary of the attribute names defined by
   this document and their corresponding source document names as
   defined in [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], [<a href="./rfc3805" title="&quot;Printer MIB v2&quot;">RFC3805</a>], [<a href="#ref-PWG5107.2" title="&quot;PWG Command Set Format for IEEE 1284 Device ID v1.0&quot;">PWG5107.2</a>], or [<a href="#ref-PWG5100.13" title="&quot;IPP Job and Printer Extensions - Set 3 (JPS3)&quot;">PWG5100.13</a>].  Some
   source attribute names have been prefixed with 'printer-' as
   recommended in [<a href="./rfc2926" title="&quot;Conversion of LDAP Schemas to and from SLP Templates&quot;">RFC2926</a>], to address the flat namespace for LDAP
   identifiers.

   LDAP and SLP Printer Schema     Source Document and Attribute Name
   ------------------------------  -------------------------------------
   ***                             IPP/1.1 and Semantics Model [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>]
   printer-uri
   printer-xri-supported
                                   [printer-uri-supported]
                                   [uri-authentication-supported]
                                   [uri-security-supported]
   printer-name                    printer-name
   printer-natural-language-configured
                                   natural-language-configured
   printer-location                printer-location
   printer-info                    printer-info
   printer-more-info               printer-more-info
   printer-make-and-model          printer-make-and-model
   printer-ipp-versions-supported  ipp-versions-supported
   printer-multiple-document-jobs-supported
                                   multiple-document-jobs-supported
   printer-charset-configured      charset-configured
   printer-charset-supported       charset-supported
   printer-generated-natural-language-supported
                                   generated-natural-language-supported
   printer-document-format-supported
                                   document-format-supported
   printer-color-supported         color-supported
   printer-compression-supported   compression-supported
   printer-pages-per-minute        pages-per-minute
   printer-pages-per-minute-color  pages-per-minute-color
   printer-finishings-supported    finishings-supported
   printer-number-up-supported     number-up-supported
   printer-sides-supported         sides-supported
   printer-media-supported         media-supported
   printer-media-local-supported   [site names from IPP media-supported]
   printer-resolution-supported    printer-resolution-supported
   printer-print-quality-supported print-quality-supported
   printer-job-priority-supported  job-priority-supported
   printer-copies-supported        copies-supported
   printer-job-k-octets-supported  job-k-octets-supported






<span class="grey">Fleming &amp; McDonald            Informational                    [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


   ***                             Printer MIB v2 [<a href="./rfc3805" title="&quot;Printer MIB v2&quot;">RFC3805</a>]
   printer-current-operator        prtGeneralCurrentOperator
   printer-service-person          prtGeneralServicePerson
   printer-delivery-orientation-supported
                                   prtOutputPageDeliveryOrientation
   printer-stacking-order-supported
                                   prtOutputStackingOrder
   printer-output-features-supported
                                   [prtOutputBursting]
                                   [prtOutputDecollating]
                                   [prtOutputPageCollated]
                                   [prtOutputOffsetStacking]
   printer-aliases                 prtGeneralPrinterName

   ***                             Cmd Set 1284 Device ID [<a href="#ref-PWG5107.2" title="&quot;PWG Command Set Format for IEEE 1284 Device ID v1.0&quot;">PWG5107.2</a>]
   printer-device-id               printer-device-id

   ***                             IPP Job/Printer Ext Set3 [<a href="#ref-PWG5100.13" title="&quot;IPP Job and Printer Extensions - Set 3 (JPS3)&quot;">PWG5100.13</a>]
   printer-device-service-count    device-service-count
   printer-uuid                    printer-uuid
   printer-charge-info             printer-charge-info
   printer-charge-info-uri         printer-charge-info-uri
   printer-geo-location            printer-geo-location
   printer-ipp-features-supported  ipp-features-supported

<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>.  printer-uri</span>

   ( 1.3.18.0.2.4.1140
   NAME 'printer-uri'
   DESC 'A URI supported by this Printer.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   SINGLE-VALUE
   )

   If the printer-xri-supported LDAP attribute is implemented, then this
   printer-uri value MUST be listed in printer-xri-supported.

   See [<a href="#ref-STD66" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">STD66</a>] for details of URI syntax.

   Note: For compatibility with IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], values of this
   attribute SHOULD NOT exceed 1023 octets in length.

   Note: LDAP application clients SHOULD NOT attempt to use malformed
   URI values read from this attribute.  LDAP administrative clients
   SHOULD NOT write malformed URI values into this attribute.




<span class="grey">Fleming &amp; McDonald            Informational                    [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


   Note: See "Internet Printing Protocol/1.1: IPP URL Scheme" [<a href="./rfc3510" title="&quot;Internet Printing Protocol/1.1: IPP URL Scheme&quot;">RFC3510</a>]
   and "Internet Printing Protocol (IPP) over HTTPS Transport Binding
   and the 'ipps' URI Scheme" [<a href="./rfc7472" title="&quot;Internet Printing Protocol (IPP) over HTTPS Transport Binding and the 'ipps' URI Scheme&quot;">RFC7472</a>] for conforming URI for IPP
   Printers.

   Note: For SLP-registered Printers, the LDAP printer-uri attribute
   SHOULD be set to the value of the SLP-registered URL of the Printer,
   for interworking with SLPv2 [<a href="./rfc2608" title="&quot;Service Location Protocol, Version 2&quot;">RFC2608</a>] service discovery.

   Note: See Sections <a href="#section-1.4.1">1.4.1</a>, <a href="#section-1.4.2">1.4.2</a>, and <a href="#section-1.4.3">1.4.3</a> for rationale for design
   choices.

<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>.  printer-xri-supported</span>

   ( 1.3.18.0.2.4.1107
   NAME 'printer-xri-supported'
   DESC 'An XRI (extended resource identifier) supported by
         this Printer.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   )

   Each value of this attribute MUST consist of a URI (uniform resource
   identifier) followed by (optional) authentication and security
   fields.

   Each XRI field MUST be delimited by '&lt;', with optional trailing
   whitespace.  For example:

      'uri=ipp://example.com/ipp&lt; auth=digest&lt; sec=tls&lt;'
      'uri=ipps://example.com/ipp&lt; auth=digest&lt; sec=tls&lt;'
      'uri=lpr://example.com/lpr&lt; auth=none&lt; sec=none&lt;'
      'uri=mailto:printer@example.com&lt; auth=none&lt; sec=none&lt;'

   Note: See the note in <a href="#section-4">Section 4</a> about the different field delimiters
   used in the printer-xri-supported and printer-resolution-supported
   attributes ('&lt;' and '&gt;', respectively), chosen for compatibility with
   the IANA-registered SLP 'service:printer:' v2.0 template [<a href="#ref-SLPPRT20" title="&quot;Service Location Protocol, Version 2 (SLPv2) Templates&quot;">SLPPRT20</a>].

   Note: Multiple values for this attribute are represented as multiple
   instances of this attribute.

   See [<a href="#ref-STD66" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">STD66</a>] for details of URI syntax.

   Note: For compatibility with IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], values of this
   attribute SHOULD NOT exceed 1023 octets in length.




<span class="grey">Fleming &amp; McDonald            Informational                    [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


   Note: LDAP application clients SHOULD NOT attempt to use malformed
   URI values read from this attribute.  LDAP administrative clients
   SHOULD NOT write malformed URI values into this attribute.

   Note: This attribute is based on the IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>] attributes
   'printer-uri-supported', 'uri-authentication-supported', and
   'uri-security-supported' (called the 'Three Musketeers' because they
   are parallel, ordered attributes).  This attribute unfolds those
   IPP/1.1 attributes and thus avoids the ordering (and same number of
   values) constraints of the IPP/1.1 separate attributes.

   Defined keywords for fields include:

      'uri' (IPP 'printer-uri-supported')
      'auth' (IPP 'uri-authentication-supported')
      'sec' (IPP 'uri-security-supported')

   A missing 'auth' field SHOULD be interpreted to mean 'none'.  Per
   IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], "IPP Job and Printer Extensions - Set 3 (JPS3)"
   [<a href="#ref-PWG5100.13" title="&quot;IPP Job and Printer Extensions - Set 3 (JPS3)&quot;">PWG5100.13</a>], and the IANA IPP registry [<a href="#ref-IANAIPP" title="&quot;Internet Printing Protocol (IPP) Registrations&quot;">IANAIPP</a>], defined values of
   the 'auth' field include:

      'none' (no authentication for this URI)
      'requesting-user-name' (from operation request)
      'basic' (HTTP/1.1 Basic [<a href="./rfc2617" title="&quot;HTTP Authentication: Basic and Digest Access Authentication&quot;">RFC2617</a>] and [<a href="./rfc7235" title="&quot;Hypertext Transfer Protocol (HTTP/1.1): Authentication&quot;">RFC7235</a>])
      'digest' (HTTP/1.1 Digest [<a href="./rfc2617" title="&quot;HTTP Authentication: Basic and Digest Access Authentication&quot;">RFC2617</a>] and [<a href="./rfc7235" title="&quot;Hypertext Transfer Protocol (HTTP/1.1): Authentication&quot;">RFC7235</a>])
      'certificate' (X.509 Certificate [<a href="./rfc5280" title="&quot;Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile&quot;">RFC5280</a>] and [<a href="./rfc6818" title="&quot;Updates to the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile&quot;">RFC6818</a>])
      'negotiate' (HTTP/1.1 Negotiate [<a href="./rfc4559" title="&quot;SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft Windows&quot;">RFC4559</a>])

   The 'certificate' value refers to the IPP Client certificate
   extracted from the TLS session.

   A missing 'sec' field SHOULD be interpreted to mean 'none'.  Per
   IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>] and the IANA IPP registry [<a href="#ref-IANAIPP" title="&quot;Internet Printing Protocol (IPP) Registrations&quot;">IANAIPP</a>], defined values
   of the 'sec' field include:

      'none' (no security for this URI)
      'ssl3' (Netscape's Secure Socket Layer protocol (SSL3))
      'tls' (IETF TLS, [<a href="./rfc5246" title="&quot;The Transport Layer Security (TLS) Protocol Version 1.2&quot;">RFC5246</a>])

   Note: The syntax and delimiter for this attribute are aligned with
   the equivalent attribute in the 'service:printer:' v2.0 template
   [<a href="#ref-SLPPRT20" title="&quot;Service Location Protocol, Version 2 (SLPv2) Templates&quot;">SLPPRT20</a>].  Whitespace is permitted after (but not before) the
   delimiter '&lt;'.







<span class="grey">Fleming &amp; McDonald            Informational                    [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


   Note: See "Internet Printing Protocol/1.1: IPP URL Scheme" [<a href="./rfc3510" title="&quot;Internet Printing Protocol/1.1: IPP URL Scheme&quot;">RFC3510</a>]
   and "Internet Printing Protocol (IPP) over HTTPS Transport Binding
   and the 'ipps' URI Scheme" [<a href="./rfc7472" title="&quot;Internet Printing Protocol (IPP) over HTTPS Transport Binding and the 'ipps' URI Scheme&quot;">RFC7472</a>] for conforming URI for IPP
   Printers.

   Note: See Sections <a href="#section-1.4.1">1.4.1</a>, <a href="#section-1.4.2">1.4.2</a>, and <a href="#section-1.4.3">1.4.3</a> for rationale for design
   choices.

<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>.  printer-name</span>

   ( 1.3.18.0.2.4.1135
   NAME 'printer-name'
   DESC 'The site-specific administrative name of this Printer.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   SINGLE-VALUE
   )

   Values of this attribute SHOULD be specified in the language
   specified in printer-natural-language-configured (for example, to
   support text-to-speech conversions), although the Printer's name MAY
   be specified in any language.

   Note: For compatibility with IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], values of this
   attribute SHOULD NOT exceed 255 octets in length.

   Note: This name can be the last part of the Printer's URI, or it can
   be completely unrelated.  This name can contain characters that are
   not allowed in a conventional URI (see [<a href="#ref-STD66" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">STD66</a>]).

   Note: For interoperability, values of this attribute (a) SHOULD be
   normalized as recommended in "Unicode Format for Network Interchange"
   [<a href="./rfc5198" title="&quot;Unicode Format for Network Interchange&quot;">RFC5198</a>]; and (b) SHOULD NOT contain DEL or any C0 or C1 control
   characters.
















<span class="grey">Fleming &amp; McDonald            Informational                    [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>.  printer-natural-language-configured</span>

   ( 1.3.18.0.2.4.1119
   NAME 'printer-natural-language-configured'
   DESC 'The configured natural language for LDAP attributes of
         syntax DirectoryString (UTF-8) in this directory entry.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   SINGLE-VALUE
   )

   Also, a possible natural language for IPP protocol string attributes
   set by operator, system administrator, or manufacturer.  Also, the
   (declared) natural language of the printer-name, printer-location,
   printer-info, and printer-make-and-model attributes of this Printer.

   Values of language tags MUST conform to "Tags for Identifying
   Languages" [<a href="#ref-BCP47" title="&quot;Matching of Language Tags&quot;">BCP47</a>].  For example:

      'en-us' (English as spoken in the US)
      'fr-fr' (French as spoken in France)

   Note: For compatibility with IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], values of this
   attribute SHOULD NOT exceed 63 octets in length.

   Note: For compatibility with IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], language tags in this
   attribute SHOULD be lowercase normalized.

<span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>.  printer-location</span>

   ( 1.3.18.0.2.4.1136
   NAME 'printer-location'
   DESC 'The physical location of this Printer.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   SINGLE-VALUE
   )

   For example:

      'Room 123A'
      'Second floor of building XYZ'

   Note: For compatibility with IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], values of this
   attribute SHOULD NOT exceed 127 octets in length.




<span class="grey">Fleming &amp; McDonald            Informational                    [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


   Note: For interoperability and consistent text display, values of
   this attribute (a) SHOULD be normalized as recommended in "Unicode
   Format for Network Interchange" [<a href="./rfc5198" title="&quot;Unicode Format for Network Interchange&quot;">RFC5198</a>]; (b) SHOULD NOT contain DEL
   or any C0 or C1 control characters except for HT, CR, and LF; and
   (c) SHOULD only contain CR and LF characters together (not as
   singletons).

<span class="h3"><a class="selflink" id="section-4.6" href="#section-4.6">4.6</a>.  printer-info</span>

   ( 1.3.18.0.2.4.1139
   NAME 'printer-info'
   DESC 'Descriptive information about this Printer.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   SINGLE-VALUE
   )

   For example:

      'This Printer can be used for printing color transparencies for
       HR presentations'

      'Out of courtesy for others, please print only small (1-5 page)
       jobs at this Printer'

      'This Printer is going away on July 1, 1997; please find a new
       Printer'

   Note: For compatibility with IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], values of this
   attribute SHOULD NOT exceed 127 octets in length.

   Note: For interoperability and consistent text display, values of
   this attribute (a) SHOULD be normalized as recommended in "Unicode
   Format for Network Interchange" [<a href="./rfc5198" title="&quot;Unicode Format for Network Interchange&quot;">RFC5198</a>]; (b) SHOULD NOT contain DEL
   or any C0 or C1 control characters except for HT, CR, and LF; and
   (c) SHOULD only contain CR and LF characters together (not as
   singletons).













<span class="grey">Fleming &amp; McDonald            Informational                    [Page 20]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h3"><a class="selflink" id="section-4.7" href="#section-4.7">4.7</a>.  printer-more-info</span>

   ( 1.3.18.0.2.4.1134
   NAME 'printer-more-info'
   DESC 'A URI for more information about this specific Printer.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   SINGLE-VALUE
   )

   For example, this could be an HTTP URI referencing an HTML page
   accessible to a Web Browser.  The information obtained from this URI
   is intended for end user consumption.

   See [<a href="#ref-STD66" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">STD66</a>] for details of URI syntax.

   Note: For compatibility with IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], values of this
   attribute SHOULD NOT exceed 1023 octets in length.

   Note: LDAP application clients SHOULD NOT attempt to use malformed
   URI values read from this attribute.  LDAP administrative clients
   SHOULD NOT write malformed URI values into this attribute.

   Note: See Sections <a href="#section-1.4.1">1.4.1</a>, <a href="#section-1.4.2">1.4.2</a>, and <a href="#section-1.4.3">1.4.3</a> for rationale for design
   choices.

<span class="h3"><a class="selflink" id="section-4.8" href="#section-4.8">4.8</a>.  printer-make-and-model</span>

   ( 1.3.18.0.2.4.1138
   NAME 'printer-make-and-model'
   DESC 'Make and model of this Printer.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   SINGLE-VALUE
   )

   Note: For compatibility with IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], values of this
   attribute SHOULD NOT exceed 127 octets in length.

   Note: The Printer manufacturer MAY initially populate this attribute.









<span class="grey">Fleming &amp; McDonald            Informational                    [Page 21]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


   Note: For interoperability and consistent text display, values of
   this attribute (a) SHOULD be normalized as recommended in "Unicode
   Format for Network Interchange" [<a href="./rfc5198" title="&quot;Unicode Format for Network Interchange&quot;">RFC5198</a>]; (b) SHOULD NOT contain DEL
   or any C0 or C1 control characters except for HT, CR, and LF; and
   (c) SHOULD only contain CR and LF characters together (not as
   singletons).

<span class="h3"><a class="selflink" id="section-4.9" href="#section-4.9">4.9</a>.  printer-ipp-versions-supported</span>

   ( 1.3.18.0.2.4.1133
   NAME 'printer-ipp-versions-supported'
   DESC 'Comma-delimited list of IPP versions supported by
         this Printer.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   )

   For example:

      '1.1,2.0'

   Note: Length overflow in values of this attribute MUST be handled by
   multiple instances of this attribute, i.e., individual
   comma-delimited list members MUST NOT be truncated.

   The IPP protocol version(s) MUST include major and minor versions,
   i.e., the exact version numbers for which this Printer implementation
   meets the IPP version-specific conformance requirements as registered
   in the IANA IPP registry [<a href="#ref-IANAIPP" title="&quot;Internet Printing Protocol (IPP) Registrations&quot;">IANAIPP</a>].

   IANA-registered versions of IPP currently are:

      '1.0' (IPP/1.0 [<a href="./rfc2566" title="&quot;Internet Printing Protocol/1.0: Model and Semantics&quot;">RFC2566</a>], OBSOLETE)
      '1.1' (IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>])
      '2.0' (IPP/2.0 [<a href="#ref-PWG5100.12" title="&quot;IPP Version 2.0 Second Edition (IPP/2.0 SE)&quot;">PWG5100.12</a>])
      '2.1' (IPP/2.1 [<a href="#ref-PWG5100.12" title="&quot;IPP Version 2.0 Second Edition (IPP/2.0 SE)&quot;">PWG5100.12</a>])
      '2.2' (IPP/2.2 [<a href="#ref-PWG5100.12" title="&quot;IPP Version 2.0 Second Edition (IPP/2.0 SE)&quot;">PWG5100.12</a>])













<span class="grey">Fleming &amp; McDonald            Informational                    [Page 22]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h3"><a class="selflink" id="section-4.10" href="#section-4.10">4.10</a>.  printer-multiple-document-jobs-supported</span>

   ( 1.3.18.0.2.4.1132
   NAME 'printer-multiple-document-jobs-supported'
   DESC 'Indicates whether or not this Printer supports more than one
         document per job.'
   EQUALITY booleanMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.7
   SINGLE-VALUE
   )

<span class="h3"><a class="selflink" id="section-4.11" href="#section-4.11">4.11</a>.  printer-charset-configured</span>

   ( 1.3.18.0.2.4.1109
   NAME 'printer-charset-configured'
   DESC 'The configured charset for IPP protocol values of error
         and status messages generated by this Printer.'
   EQUALITY caseIgnoreMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   SINGLE-VALUE
   )

   Also, a possible charset for IPP protocol string attributes set by
   operator, system administrator, or manufacturer.  For example:

      'utf-8' (ISO 10646/Unicode in UTF-8 transform [<a href="#ref-STD63" title="&quot;UTF-8, a transformation format of ISO 10646&quot;">STD63</a>])
      'iso-8859-1' (ISO Latin1)

   Values of charset tags SHOULD be defined in the IANA registry of
   Character Sets [<a href="#ref-IANACHAR" title="&quot;Character Sets&quot;">IANACHAR</a>] (see also [<a href="#ref-BCP19" title="&quot;IANA Charset Registration Procedures&quot;">BCP19</a>]), and the '(preferred
   MIME name)' SHOULD be used as the charset tag in this attribute.

   Note: For compatibility with IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], values of this
   attribute SHOULD NOT exceed 63 octets in length.

   Note: For compatibility with IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], charset tags in this
   attribute SHOULD be lowercase normalized.














<span class="grey">Fleming &amp; McDonald            Informational                    [Page 23]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h3"><a class="selflink" id="section-4.12" href="#section-4.12">4.12</a>.  printer-charset-supported</span>

   ( 1.3.18.0.2.4.1131
   NAME 'printer-charset-supported'
   DESC 'One of the charsets supported for IPP protocol values of
         IPP string attributes that correspond to attributes of
         syntax DirectoryString (UTF-8) for this directory entry.'
   EQUALITY caseIgnoreMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   )

   For example:

      'utf-8' (ISO 10646/Unicode in UTF-8 transform [<a href="#ref-STD63" title="&quot;UTF-8, a transformation format of ISO 10646&quot;">STD63</a>])
      'iso-8859-1' (ISO Latin1)

   Note: Multiple values for this attribute are represented as multiple
   instances of this attribute.

   Values of charset tags SHOULD be defined in the IANA registry of
   Character Sets [<a href="#ref-IANACHAR" title="&quot;Character Sets&quot;">IANACHAR</a>] (see also [<a href="#ref-BCP19" title="&quot;IANA Charset Registration Procedures&quot;">BCP19</a>]), and the '(preferred
   MIME name)' SHOULD be used as the charset tag in this attribute.

   Note: For compatibility with IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], values of this
   attribute SHOULD NOT exceed 63 octets in length.

   Note: For compatibility with IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], charset tags in this
   attribute SHOULD be lowercase normalized.

<span class="h3"><a class="selflink" id="section-4.13" href="#section-4.13">4.13</a>.  printer-generated-natural-language-supported</span>

   ( 1.3.18.0.2.4.1137
   NAME 'printer-generated-natural-language-supported'
   DESC 'One of the natural languages supported for LDAP attributes of
         syntax DirectoryString (UTF-8) in this directory entry.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   )

   Values of language tags SHOULD conform to "Tags for Identifying
   Languages" [<a href="#ref-BCP47" title="&quot;Matching of Language Tags&quot;">BCP47</a>].  For example:

      'en-us' (English as spoken in the US)
      'fr-ca' (French as spoken in Canada)

   Note: Multiple values for this attribute are represented as multiple
   instances of this attribute.



<span class="grey">Fleming &amp; McDonald            Informational                    [Page 24]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


   Note: For compatibility with IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], values of this
   attribute SHOULD NOT exceed 63 octets in length.

   Note: For compatibility with IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], language tags in this
   attribute SHOULD be lowercase normalized.

<span class="h3"><a class="selflink" id="section-4.14" href="#section-4.14">4.14</a>.  printer-document-format-supported</span>

   ( 1.3.18.0.2.4.1130
   NAME 'printer-document-format-supported'
   DESC 'One of the source document formats that can be interpreted
         and printed by this Printer.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   )

   Values of document formats SHOULD be MIME media types defined in the
   IANA registry of MIME Media Types [<a href="#ref-IANAMIME" title="&quot;Media Types&quot;">IANAMIME</a>] (see also [<a href="#ref-BCP13" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures&quot;">BCP13</a>]).

   For example:

      'application/postscript' (Adobe PostScript)
      'text/plain' (plain text)

   Note: Multiple values for this attribute are represented as multiple
   instances of this attribute.

   Note: For compatibility with IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], values of this
   attribute SHOULD NOT exceed 255 octets in length.

<span class="h3"><a class="selflink" id="section-4.15" href="#section-4.15">4.15</a>.  printer-color-supported</span>

   ( 1.3.18.0.2.4.1129
   NAME 'printer-color-supported'
   DESC 'Indicates whether or not this Printer is capable of any type of
         color printing at all, including highlight color.'
   EQUALITY booleanMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.7
   SINGLE-VALUE
   )










<span class="grey">Fleming &amp; McDonald            Informational                    [Page 25]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h3"><a class="selflink" id="section-4.16" href="#section-4.16">4.16</a>.  printer-compression-supported</span>

   ( 1.3.18.0.2.4.1128
   NAME 'printer-compression-supported'
   DESC 'Comma-delimited list of compression algorithms supported by
         this Printer.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   )

   For example:

      'none'
      'deflate,gzip'

   Note: Length overflow in values of this attribute MUST be handled by
   multiple instances of this attribute, i.e., individual
   comma-delimited list members MUST NOT be truncated.

   Note: For compatibility with IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], values of this
   attribute SHOULD NOT exceed 255 octets in length.

   Values defined in IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>] and recorded in the IANA IPP
   registry [<a href="#ref-IANAIPP" title="&quot;Internet Printing Protocol (IPP) Registrations&quot;">IANAIPP</a>] include:

      'none' (no compression is used)
      'deflate' (public domain ZIP described in [<a href="./rfc1951" title="&quot;DEFLATE Compressed Data Format Specification version 1.3&quot;">RFC1951</a>])
      'gzip' (GNU ZIP described in [<a href="./rfc1952" title="&quot;GZIP file format specification version 4.3&quot;">RFC1952</a>])
      'compress' (UNIX compression described in [<a href="./rfc1977" title="&quot;PPP BSD Compression Protocol&quot;">RFC1977</a>])

<span class="h3"><a class="selflink" id="section-4.17" href="#section-4.17">4.17</a>.  printer-pages-per-minute</span>

   ( 1.3.18.0.2.4.1127
   NAME 'printer-pages-per-minute'
   DESC 'The nominal number of pages per minute that can be output by
         this Printer.'
   EQUALITY integerMatch
   ORDERING integerOrderingMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.27
   SINGLE-VALUE
   )

   This attribute is informative, not a service guarantee.  Typically,
   it is the value used in marketing literature to describe this Printer
   -- for example, the value for a simplex or black-and-white print
   mode.




<span class="grey">Fleming &amp; McDonald            Informational                    [Page 26]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h3"><a class="selflink" id="section-4.18" href="#section-4.18">4.18</a>.  printer-pages-per-minute-color</span>

   ( 1.3.18.0.2.4.1126
   NAME 'printer-pages-per-minute-color'
   DESC 'The nominal number of color pages per minute that can be
         output by this Printer.'
   EQUALITY integerMatch
   ORDERING integerOrderingMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.27
   SINGLE-VALUE
   )

   This attribute is informative, not a service guarantee.  Typically,
   it is the value used in marketing literature to describe this
   Printer.

<span class="h3"><a class="selflink" id="section-4.19" href="#section-4.19">4.19</a>.  printer-finishings-supported</span>

   ( 1.3.18.0.2.4.1125
   NAME 'printer-finishings-supported'
   DESC 'Comma-delimited list of finishing operations supported by
         this Printer.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   )

   For example:

      'staple'
      'staple,punch,bind'

   Note: Length overflow in values of this attribute MUST be handled by
   multiple instances of this attribute, i.e., individual
   comma-delimited list members MUST NOT be truncated.

   Note: For compatibility with IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], values of this
   attribute SHOULD NOT exceed 255 octets in length.

   Values defined in IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>] and recorded in the IANA IPP
   registry [<a href="#ref-IANAIPP" title="&quot;Internet Printing Protocol (IPP) Registrations&quot;">IANAIPP</a>] include:

      'none', 'staple', 'punch', 'cover', 'bind', 'saddle-stitch',
      'edge-stitch', 'staple-top-left', 'staple-bottom-left',
      'staple-top-right', 'staple-bottom-right', 'edge-stitch-left',
      'edge-stitch-top', 'edge-stitch-right', 'edge-stitch-bottom',
      'staple-dual-left', 'staple-dual-top', 'staple-dual-right',
      'staple-dual-bottom'.



<span class="grey">Fleming &amp; McDonald            Informational                    [Page 27]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


   Note: Implementations MAY support other values.

<span class="h3"><a class="selflink" id="section-4.20" href="#section-4.20">4.20</a>.  printer-number-up-supported</span>

   ( 1.3.18.0.2.4.1124
   NAME 'printer-number-up-supported'
   DESC 'Maximum number of print-stream pages that can be imposed upon
         a single side of an instance of a selected medium by this
         Printer.'
   EQUALITY integerMatch
   ORDERING integerOrderingMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.27
   SINGLE-VALUE
   )

   For example:

      '1'
      '4'

   Note: Values of this attribute differ from the corresponding IPP
   attribute, in that only the maximum number-up is mapped from the
   corresponding IPP attribute 'number-up-supported' defined in
   [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>].

<span class="h3"><a class="selflink" id="section-4.21" href="#section-4.21">4.21</a>.  printer-sides-supported</span>

   ( 1.3.18.0.2.4.1123
   NAME 'printer-sides-supported'
   DESC 'Comma-delimited list of impression sides (one or two) and the
         two-sided impression rotations supported by this Printer.'
   EQUALITY caseIgnoreMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   )

   For example:

      'one-sided'
      'one-sided,two-sided-short-edge'

   Note: Length overflow in values of this attribute MUST be handled by
   multiple instances of this attribute, i.e., individual
   comma-delimited list members MUST NOT be truncated.

   Note: For compatibility with IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], values of this
   attribute SHOULD NOT exceed 255 octets in length.





<span class="grey">Fleming &amp; McDonald            Informational                    [Page 28]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


   Values defined in IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>] and recorded in the IANA IPP
   registry [<a href="#ref-IANAIPP" title="&quot;Internet Printing Protocol (IPP) Registrations&quot;">IANAIPP</a>] are:

      'one-sided'
      'two-sided-long-edge'
      'two-sided-short-edge'

<span class="h3"><a class="selflink" id="section-4.22" href="#section-4.22">4.22</a>.  printer-media-supported</span>

   ( 1.3.18.0.2.4.1122
   NAME 'printer-media-supported'
   DESC 'One of the names/sizes/types/colors of the media supported by
         this Printer.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   )

   Values SHOULD conform to "PWG Media Standardized Names 2.0 (MSN2)"
   [<a href="#ref-PWG5101.1" title="&quot;PWG Media Standardized Names 2.0 (MSN2)&quot;">PWG5101.1</a>].

   Note: For compatibility with IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], values of this
   attribute SHOULD NOT exceed 255 octets in length.

   Values of standardized media size names defined in [<a href="#ref-PWG5101.1" title="&quot;PWG Media Standardized Names 2.0 (MSN2)&quot;">PWG5101.1</a>] and
   recorded in the IANA IPP registry [<a href="#ref-IANAIPP" title="&quot;Internet Printing Protocol (IPP) Registrations&quot;">IANAIPP</a>] include:

      'na_letter_8.5x11in'
      'iso_a4_210x297mm'

   Values of standardized media types defined in [<a href="#ref-PWG5101.1" title="&quot;PWG Media Standardized Names 2.0 (MSN2)&quot;">PWG5101.1</a>] and
   recorded in the IANA IPP registry [<a href="#ref-IANAIPP" title="&quot;Internet Printing Protocol (IPP) Registrations&quot;">IANAIPP</a>] include:

      'envelope'
      'stationery'

   Values of standardized media colors defined in [<a href="#ref-PWG5101.1" title="&quot;PWG Media Standardized Names 2.0 (MSN2)&quot;">PWG5101.1</a>] and
   recorded in the IANA IPP registry [<a href="#ref-IANAIPP" title="&quot;Internet Printing Protocol (IPP) Registrations&quot;">IANAIPP</a>] include:

      'white'
      'blue'

   Note: Multiple values for this attribute are represented as multiple
   instances of this attribute.







<span class="grey">Fleming &amp; McDonald            Informational                    [Page 29]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h3"><a class="selflink" id="section-4.23" href="#section-4.23">4.23</a>.  printer-media-local-supported</span>

   ( 1.3.18.0.2.4.1117
   NAME 'printer-media-local-supported'
   DESC 'One of the site-specific media supported by this Printer.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   )

   Values SHOULD conform to "PWG Media Standardized Names 2.0 (MSN2)"
   [<a href="#ref-PWG5101.1" title="&quot;PWG Media Standardized Names 2.0 (MSN2)&quot;">PWG5101.1</a>].

   For example:

      'custom_purchasing-form_8.5x11in' (site-specific name)

   Note: Multiple values for this attribute are represented as multiple
   instances of this attribute.

   Note: For compatibility with IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], values of this
   attribute SHOULD NOT exceed 255 octets in length.

<span class="h3"><a class="selflink" id="section-4.24" href="#section-4.24">4.24</a>.  printer-resolution-supported</span>

   ( 1.3.18.0.2.4.1121
   NAME 'printer-resolution-supported'
   DESC 'One of the resolutions supported for printing documents by
         this Printer.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   )

   Each resolution value MUST be a string containing three fields:

   1) Cross-feed direction resolution (positive integer);

   2) Feed direction resolution (positive integer);

   3) Unit -- 'dpi' (dots per inch) or 'dpcm' (dots per centimeter).

   Each resolution field MUST be delimited by '&gt;', with optional
   trailing whitespace.  For example:

      '300&gt; 300&gt; dpi&gt;'
      '600&gt; 600&gt; dpi&gt;'




<span class="grey">Fleming &amp; McDonald            Informational                    [Page 30]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


   Note: See the note in <a href="#section-4">Section 4</a> about the different field delimiters
   used in the printer-xri-supported and printer-resolution-supported
   attributes ('&lt;' and '&gt;', respectively), chosen for compatibility with
   the IANA-registered SLP 'service:printer:' v2.0 template [<a href="#ref-SLPPRT20" title="&quot;Service Location Protocol, Version 2 (SLPv2) Templates&quot;">SLPPRT20</a>].

   Note: Multiple values for this attribute are represented as multiple
   instances of this attribute.

   Note: This attribute is based on 'printer-resolution-supported'
   defined in IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>] with a complex encoding derived from
   'prtMarkerAddressabilityFeedDir', 'prtMarkerAddressabilityXFeedDir',
   and 'prtMarkerAddressabilityUnit' defined in "Printer MIB v2"
   [<a href="./rfc3805" title="&quot;Printer MIB v2&quot;">RFC3805</a>] (which have integer encodings).

   Note: The syntax and delimiter for this attribute are aligned with
   the equivalent attribute in the 'service:printer:' v2.0 template
   [<a href="#ref-SLPPRT20" title="&quot;Service Location Protocol, Version 2 (SLPv2) Templates&quot;">SLPPRT20</a>].  Whitespace is permitted after (but not before) the
   delimiter '&gt;'.

<span class="h3"><a class="selflink" id="section-4.25" href="#section-4.25">4.25</a>.  printer-print-quality-supported</span>

   ( 1.3.18.0.2.4.1120
   NAME 'printer-print-quality-supported'
   DESC 'Comma-delimited list of print qualities supported
         for printing documents on this Printer.'
   EQUALITY caseIgnoreMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   )

   For example:

      'unknown'
      'draft,normal,high'

   Note: Length overflow in values of this attribute MUST be handled by
   multiple instances of this attribute, i.e., individual
   comma-delimited list members MUST NOT be truncated.

   Values defined in IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>] and recorded in the IANA IPP
   registry [<a href="#ref-IANAIPP" title="&quot;Internet Printing Protocol (IPP) Registrations&quot;">IANAIPP</a>] include:

      'draft'
      'normal'
      'high'

   Note: The value 'unknown' MUST only be reported if the corresponding
   IPP attribute is not present, i.e., the value 'unknown' is an
   artifact of this LDAP mapping.



<span class="grey">Fleming &amp; McDonald            Informational                    [Page 31]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h3"><a class="selflink" id="section-4.26" href="#section-4.26">4.26</a>.  printer-job-priority-supported</span>

   ( 1.3.18.0.2.4.1110
   NAME 'printer-job-priority-supported'
   DESC 'Indicates the number of job priority levels supported by
         this Printer.'
   EQUALITY integerMatch
   ORDERING integerOrderingMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.27
   SINGLE-VALUE
   )

   An IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>] conformant Printer, which supports job priority,
   always supports a full range of priorities from '1' to '100' (to
   ensure consistent behavior); therefore, this attribute describes the
   'granularity' of priority supported.  Values of this attribute are
   from '1' to '100'.

<span class="h3"><a class="selflink" id="section-4.27" href="#section-4.27">4.27</a>.  printer-copies-supported</span>

   ( 1.3.18.0.2.4.1118
   NAME 'printer-copies-supported'
   DESC 'The maximum number of copies of a document that can be printed
         as a single job on this Printer.'
   EQUALITY integerMatch
   ORDERING integerOrderingMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.27
   SINGLE-VALUE
   )

   A positive value indicates the maximum supported copies.  A value of
   '0' indicates no maximum limit.  A value of '-1' indicates 'unknown'.

   Note: The syntax and values for this attribute are aligned with the
   equivalent attribute in the 'service:printer:' v2.0 template
   [<a href="#ref-SLPPRT20" title="&quot;Service Location Protocol, Version 2 (SLPv2) Templates&quot;">SLPPRT20</a>].















<span class="grey">Fleming &amp; McDonald            Informational                    [Page 32]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h3"><a class="selflink" id="section-4.28" href="#section-4.28">4.28</a>.  printer-job-k-octets-supported</span>

   ( 1.3.18.0.2.4.1111
   NAME 'printer-job-k-octets-supported'
   DESC 'The maximum size of an incoming print job that this Printer
         will accept, in kilobytes (1,024 octets).'
   EQUALITY integerMatch
   ORDERING integerOrderingMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.27
   SINGLE-VALUE
   )

   A positive value indicates the maximum supported job size.  A value
   of '0' indicates no maximum limit.  A value of '-1' indicates
   'unknown'.

   Note: The syntax and values for this attribute are aligned with the
   equivalent attribute in the 'service:printer:' v2.0 template
   [<a href="#ref-SLPPRT20" title="&quot;Service Location Protocol, Version 2 (SLPv2) Templates&quot;">SLPPRT20</a>].

<span class="h3"><a class="selflink" id="section-4.29" href="#section-4.29">4.29</a>.  printer-current-operator</span>

   ( 1.3.18.0.2.4.1112
   NAME 'printer-current-operator'
   DESC 'The identity of the current human operator responsible for
         operating this Printer.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   SINGLE-VALUE
   )

   The value of this attribute SHOULD include information that would
   enable other humans to reach the operator, such as a telephone
   number.

   Note: For interoperability and consistent text display, values of
   this attribute (a) SHOULD be normalized as recommended in "Unicode
   Format for Network Interchange" [<a href="./rfc5198" title="&quot;Unicode Format for Network Interchange&quot;">RFC5198</a>]; (b) SHOULD NOT contain DEL
   or any C0 or C1 control characters except for HT, CR, and LF; and
   (c) SHOULD only contain CR and LF characters together (not as
   singletons).









<span class="grey">Fleming &amp; McDonald            Informational                    [Page 33]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h3"><a class="selflink" id="section-4.30" href="#section-4.30">4.30</a>.  printer-service-person</span>

   ( 1.3.18.0.2.4.1113
   NAME 'printer-service-person'
   DESC 'The identity of the current human service person responsible
         for servicing this Printer.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   SINGLE-VALUE
   )

   The value of this attribute SHOULD include information that would
   enable other humans to reach the service person, such as a telephone
   number.

   Note: For interoperability and consistent text display, values of
   this attribute (a) SHOULD be normalized as recommended in "Unicode
   Format for Network Interchange" [<a href="./rfc5198" title="&quot;Unicode Format for Network Interchange&quot;">RFC5198</a>]; (b) SHOULD NOT contain DEL
   or any C0 or C1 control characters except for HT, CR, and LF; and
   (c) SHOULD only contain CR and LF characters together (not as
   singletons).

<span class="h3"><a class="selflink" id="section-4.31" href="#section-4.31">4.31</a>.  printer-delivery-orientation-supported</span>

   ( 1.3.18.0.2.4.1114
   NAME 'printer-delivery-orientation-supported'
   DESC 'Comma-delimited list of delivery orientations of pages as they
         are printed and ejected supported by this Printer.'
   EQUALITY caseIgnoreMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   )

   For example:

      'unknown'
      'face-up,face-down'

   Values defined in "Printer MIB v2" [<a href="./rfc3805" title="&quot;Printer MIB v2&quot;">RFC3805</a>] for
   prtOutputPageDeliveryOrientation are:

      'face-up'
      'face-down'

   Note: The value 'unknown' MUST only be reported if the corresponding
   Printer MIB attribute is not present, i.e., the value 'unknown' is an
   artifact of this LDAP mapping.




<span class="grey">Fleming &amp; McDonald            Informational                    [Page 34]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


   Note: The syntax and values for this attribute are aligned with the
   equivalent attribute in the 'service:printer:' v2.0 template
   [<a href="#ref-SLPPRT20" title="&quot;Service Location Protocol, Version 2 (SLPv2) Templates&quot;">SLPPRT20</a>].

<span class="h3"><a class="selflink" id="section-4.32" href="#section-4.32">4.32</a>.  printer-stacking-order-supported</span>

   ( 1.3.18.0.2.4.1115
   NAME 'printer-stacking-order-supported'
   DESC 'Comma-delimited list of stacking orders of pages as they are
         printed and ejected supported by this Printer.'
   EQUALITY caseIgnoreMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   )

   For example:

      'unknown'
      'first-to-last'
      'first-to-last,last-to-first'

   Values defined in "Printer MIB v2" [<a href="./rfc3805" title="&quot;Printer MIB v2&quot;">RFC3805</a>] for
   prtOutputStackingOrder are:

      'first-to-last'
      'last-to-first'

   Note: The value 'unknown' MUST only be reported if the corresponding
   Printer MIB attribute is not present, i.e., the value 'unknown' is an
   artifact of this LDAP mapping.

   Note: The syntax and values for this attribute are aligned with the
   equivalent attribute in the 'service:printer:' v2.0 template
   [<a href="#ref-SLPPRT20" title="&quot;Service Location Protocol, Version 2 (SLPv2) Templates&quot;">SLPPRT20</a>].


















<span class="grey">Fleming &amp; McDonald            Informational                    [Page 35]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h3"><a class="selflink" id="section-4.33" href="#section-4.33">4.33</a>.  printer-output-features-supported</span>

   ( 1.3.18.0.2.4.1116
   NAME 'printer-output-features-supported'
   DESC 'Comma-delimited list of output features supported by
         this Printer.'
   EQUALITY caseIgnoreMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   )

   For example:

      'unknown'
      'bursting,decollating'
      'offset-stacking'

   Note: Length overflow in values of this attribute MUST be handled by
   multiple instances of this attribute, i.e., individual
   comma-delimited list members MUST NOT be truncated.

   Values defined in "Printer MIB v2" [<a href="./rfc3805" title="&quot;Printer MIB v2&quot;">RFC3805</a>] for prtOutputBursting,
   prtOutputDecollating, prtOutputPageCollated, and
   prtOutputOffsetStacking are:

      'bursting'
      'decollating'
      'page-collating'
      'offset-stacking'

   Note: The value 'unknown' MUST only be reported if the corresponding
   Printer MIB attributes are not present, i.e., the value 'unknown' is
   an artifact of this LDAP mapping.

   Note: The syntax and values for this attribute are aligned with the
   equivalent attribute in the 'service:printer:' v2.0 template
   [<a href="#ref-SLPPRT20" title="&quot;Service Location Protocol, Version 2 (SLPv2) Templates&quot;">SLPPRT20</a>].

   Note: Implementations MAY support other values.













<span class="grey">Fleming &amp; McDonald            Informational                    [Page 36]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h3"><a class="selflink" id="section-4.34" href="#section-4.34">4.34</a>.  printer-aliases</span>

   ( 1.3.18.0.2.4.1108
   NAME 'printer-aliases'
   DESC 'One of the site-specific administrative names of this Printer
         in addition to the value specified for printer-name.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   )

   Values of this attribute SHOULD be specified in the language
   specified in printer-natural-language-configured (for example, to
   support text-to-speech conversions), although the Printer's alias MAY
   be specified in any language.

   Note: Multiple values for this attribute are represented as multiple
   instances of this attribute.

   Note: For compatibility with IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>], values of this
   attribute SHOULD NOT exceed 255 octets in length.

   Note: For interoperability, values of this attribute (a) SHOULD be
   normalized as recommended in "Unicode Format for Network Interchange"
   [<a href="./rfc5198" title="&quot;Unicode Format for Network Interchange&quot;">RFC5198</a>]; and (b) SHOULD NOT contain DEL or any C0 or C1 control
   characters.

<span class="h3"><a class="selflink" id="section-4.35" href="#section-4.35">4.35</a>.  printer-device-id</span>

   ( 1.3.18.0.2.24.46.1.101
   NAME 'printer-device-id'
   DESC 'The IEEE 1284 Device ID for this Printer.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   SINGLE-VALUE
   )

   Values of this attribute SHOULD conform to "PWG Command Set Format
   for IEEE 1284 Device ID v1.0" [<a href="#ref-PWG5107.2" title="&quot;PWG Command Set Format for IEEE 1284 Device ID v1.0&quot;">PWG5107.2</a>].

   Note: For compatibility with [<a href="#ref-PWG5100.14" title="&quot;IPP Everywhere&quot;">PWG5100.14</a>] and [<a href="#ref-PWG5107.2" title="&quot;PWG Command Set Format for IEEE 1284 Device ID v1.0&quot;">PWG5107.2</a>], values of
   this attribute SHOULD NOT exceed 1023 octets in length.








<span class="grey">Fleming &amp; McDonald            Informational                    [Page 37]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h3"><a class="selflink" id="section-4.36" href="#section-4.36">4.36</a>.  printer-device-service-count</span>

   ( 1.3.18.0.2.24.46.1.102
   NAME 'printer-device-service-count'
   DESC 'The number of Printer (print service) instances configured on
         this Imaging Device (host system).'
   EQUALITY integerMatch
   ORDERING integerOrderingMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.27
   SINGLE-VALUE
   )

   A positive value indicates the number of Printer (print service)
   instances.  A value of '-1' indicates 'unknown'.  A value of '0' is
   not meaningful (because this attribute must be reported by some
   Printer instance).

   Note: The syntax and values for this attribute are aligned with the
   equivalent 'device-service-count' attribute defined in [<a href="#ref-PWG5100.13" title="&quot;IPP Job and Printer Extensions - Set 3 (JPS3)&quot;">PWG5100.13</a>].

<span class="h3"><a class="selflink" id="section-4.37" href="#section-4.37">4.37</a>.  printer-uuid</span>

   ( 1.3.18.0.2.24.46.1.104
   NAME 'printer-uuid'
   DESC 'A URN specifying the UUID of this Printer (print service)
         instance on this Imaging Device (host system).'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   SINGLE-VALUE
   )

   For example:

      'urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6'

   Values of this attribute MUST conform to the Universally Unique
   Identifier (UUID) URN namespace [<a href="./rfc4122" title="&quot;A Universally Unique IDentifier (UUID) URN Namespace&quot;">RFC4122</a>].

   Note: For compatibility with [<a href="#ref-PWG5100.13" title="&quot;IPP Job and Printer Extensions - Set 3 (JPS3)&quot;">PWG5100.13</a>] and [<a href="./rfc4122" title="&quot;A Universally Unique IDentifier (UUID) URN Namespace&quot;">RFC4122</a>], values of
   this attribute SHOULD NOT exceed 45 octets in length.

   Note: LDAP application clients SHOULD NOT attempt to use malformed
   URN values read from this attribute.  LDAP administrative clients
   SHOULD NOT write malformed URN values into this attribute.

   Note: The syntax and values for this attribute are aligned with the
   equivalent 'printer-uuid' attribute defined in [<a href="#ref-PWG5100.13" title="&quot;IPP Job and Printer Extensions - Set 3 (JPS3)&quot;">PWG5100.13</a>].



<span class="grey">Fleming &amp; McDonald            Informational                    [Page 38]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h3"><a class="selflink" id="section-4.38" href="#section-4.38">4.38</a>.  printer-charge-info</span>

   ( 1.3.18.0.2.24.46.1.105
   NAME 'printer-charge-info'
   DESC 'Descriptive information about paid printing services for this
         Printer.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   SINGLE-VALUE
   )

   For example:

      'This Printer can be used for paid printing at 2 cents/page.'

   Note: For compatibility with [<a href="#ref-PWG5100.13" title="&quot;IPP Job and Printer Extensions - Set 3 (JPS3)&quot;">PWG5100.13</a>], values of this attribute
   SHOULD NOT exceed 1023 octets in length.

   Note: For interoperability and consistent text display, values of
   this attribute (a) SHOULD be normalized as recommended in "Unicode
   Format for Network Interchange" [<a href="./rfc5198" title="&quot;Unicode Format for Network Interchange&quot;">RFC5198</a>]; (b) SHOULD NOT contain any
   C0 or C1 control characters except for HT, CR, and LF; and (c) SHOULD
   only contain CR and LF characters together (not as singletons).

   Note: The syntax and values for this attribute are aligned with the
   equivalent 'printer-charge-info' attribute defined in [<a href="#ref-PWG5100.13" title="&quot;IPP Job and Printer Extensions - Set 3 (JPS3)&quot;">PWG5100.13</a>].

<span class="h3"><a class="selflink" id="section-4.39" href="#section-4.39">4.39</a>.  printer-charge-info-uri</span>

   ( 1.3.18.0.2.24.46.1.106
   NAME 'printer-charge-info-uri'
   DESC 'A URI for a human-readable Web page for paid printing services
         for this Printer.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   SINGLE-VALUE
   )

   For example:

      'http://example.com/charges'

   See [<a href="#ref-STD66" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">STD66</a>] for details of URI syntax.

   Note: For compatibility with IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>] and [<a href="#ref-PWG5100.13" title="&quot;IPP Job and Printer Extensions - Set 3 (JPS3)&quot;">PWG5100.13</a>],
   values of this attribute SHOULD NOT exceed 1023 octets in length.



<span class="grey">Fleming &amp; McDonald            Informational                    [Page 39]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


   Note: LDAP application clients SHOULD NOT attempt to use malformed
   URI values read from this attribute.  LDAP administrative clients
   SHOULD NOT write malformed URI values into this attribute.

   Note: The syntax and values for this attribute are aligned with the
   equivalent 'printer-charge-info-uri' attribute defined in
   [<a href="#ref-PWG5100.13" title="&quot;IPP Job and Printer Extensions - Set 3 (JPS3)&quot;">PWG5100.13</a>].

<span class="h3"><a class="selflink" id="section-4.40" href="#section-4.40">4.40</a>.  printer-geo-location</span>

   ( 1.3.18.0.2.24.46.1.107
   NAME 'printer-geo-location'
   DESC 'A geo: URI specifying the geographic location of this Printer.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   SINGLE-VALUE
   )

   For example:

      'geo:13.4125,103.8667'

   Values of this attribute MUST conform to the 'geo' URI scheme
   [<a href="./rfc5870" title="&quot;A Uniform Resource Identifier for Geographic Locations ('geo' URI)&quot;">RFC5870</a>].

   Note: For compatibility with IPP/1.1 [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>] and [<a href="#ref-PWG5100.13" title="&quot;IPP Job and Printer Extensions - Set 3 (JPS3)&quot;">PWG5100.13</a>],
   values of this attribute SHOULD NOT exceed 1023 octets in length.

   Note: LDAP application clients SHOULD NOT attempt to use malformed
   URI values read from this attribute.  LDAP administrative clients
   SHOULD NOT write malformed URI values into this attribute.

   Note: The syntax and values for this attribute are aligned with the
   equivalent 'printer-geo-location' attribute defined in [<a href="#ref-PWG5100.13" title="&quot;IPP Job and Printer Extensions - Set 3 (JPS3)&quot;">PWG5100.13</a>].
















<span class="grey">Fleming &amp; McDonald            Informational                    [Page 40]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h3"><a class="selflink" id="section-4.41" href="#section-4.41">4.41</a>.  printer-ipp-features-supported</span>

   ( 1.3.18.0.2.24.46.1.108
   NAME 'printer-ipp-features-supported'
   DESC 'Comma-delimited list of IPP protocol features that
         this Printer supports.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15
   )

   For example:

      'none'
      'unknown'
      'proof-print'
      'ipp-everywhere,proof-print,job-save'

   Note: Length overflow in values of this attribute MUST be handled by
   multiple instances of this attribute, i.e., individual
   comma-delimited list members MUST NOT be truncated.

   Values of this attribute SHOULD specify only IANA-registered keywords
   for the 'ipp-features-supported' attribute defined in [<a href="#ref-PWG5100.13" title="&quot;IPP Job and Printer Extensions - Set 3 (JPS3)&quot;">PWG5100.13</a>] or
   other Standards Track IETF or IEEE-ISTO PWG specifications if this
   Printer implementation meets all of the IPP feature-specific
   conformance requirements.

   IANA-registered values include:

      'none' (No extension features are supported)
      'document-object' (Document object defined in [<a href="#ref-PWG5100.5" title="&quot;IPP Document Object&quot;">PWG5100.5</a>])
      'job-save' (Job save defined in [<a href="#ref-PWG5100.11" title="&quot;IPP Job and Printer Extensions - Set 2 (JPS2)&quot;">PWG5100.11</a>])
      'ipp-everywhere' ("IPP Everywhere" defined in [<a href="#ref-PWG5100.14" title="&quot;IPP Everywhere&quot;">PWG5100.14</a>])
      'page-overrides' (Page overrides defined in [<a href="#ref-PWG5100.6" title="">PWG5100.6</a>])
      'proof-print' (Proof print defined in [<a href="#ref-PWG5100.11" title="&quot;IPP Job and Printer Extensions - Set 2 (JPS2)&quot;">PWG5100.11</a>])
      'subscription-object' (Subscription object defined in [<a href="./rfc3995" title="&quot;Internet Printing Protocol (IPP): Event Notifications and Subscriptions&quot;">RFC3995</a>])

   Note: The value 'unknown' MUST only be reported if the corresponding
   IPP Printer attribute is not present, i.e., the value 'unknown' is an
   artifact of this LDAP mapping.

   Note: The syntax and values for this attribute are aligned with the
   equivalent 'ipp-features-supported' attribute defined in
   [<a href="#ref-PWG5100.13" title="&quot;IPP Job and Printer Extensions - Set 3 (JPS3)&quot;">PWG5100.13</a>].






<span class="grey">Fleming &amp; McDonald            Informational                    [Page 41]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Definition of Syntaxes</span>

   No new attribute syntaxes are defined by this document.

   The attribute types defined in <a href="#section-4">Section 4</a> of this document reference
   syntax OIDs defined in <a href="./rfc4517#section-3">Section&nbsp;3 of [RFC4517]</a>, which are summarized
   below:

   Syntax OID                      Syntax Description
   ------------------------------  -------------------------------
   1.3.6.1.4.1.1466.115.121.1.7    Boolean
   1.3.6.1.4.1.1466.115.121.1.15   DirectoryString (UTF-8 [<a href="#ref-STD63" title="&quot;UTF-8, a transformation format of ISO 10646&quot;">STD63</a>])
   1.3.6.1.4.1.1466.115.121.1.27   Integer

<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>.  Definition of Matching Rules</span>

   No new matching rules are defined by this document.

   The attribute types defined in <a href="#section-4">Section 4</a> of this document reference
   matching rules defined in <a href="./rfc4517#section-4">Section&nbsp;4 of [RFC4517]</a>, which are
   summarized below:

   Matching Rule OID               Matching Rule Name          Usage
   -----------------------------   ------------------          --------
   2.5.13.13                       booleanMatch                EQUALITY
   2.5.13.2                        caseIgnoreMatch             EQUALITY
   2.5.13.14                       integerMatch                EQUALITY
   2.5.13.15                       integerOrderingMatch        ORDERING
   2.5.13.4                        caseIgnoreSubstringsMatch   SUBSTR

<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>.  IANA Considerations</span>

   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 <a href="#section-7.1">Section 7.1</a> below).

   All of the object classes and most of the attribute types described
   in this document were registered by IANA when <a href="./rfc3712">RFC 3712</a> was published
   (see <a href="#section-7.2">Section 7.2</a> below).











<span class="grey">Fleming &amp; McDonald            Informational                    [Page 42]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>.  Registration of Attribute Types</span>

   The following Attribute Type OIDs have been assigned by the IEEE-ISTO
   PWG (see <a href="#section-1.3.2">Section 1.3.2</a>) 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 &amp; email address to contact for further information:  see below

   Usage:  attribute type

   Specification:  <a href="./rfc7612">RFC 7612</a> (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: blueroofmusic@gmail.com

   Comments:

   Attribute Type                                OID
   ------------------------------------          ----------------------
   printer-device-id                             1.3.18.0.2.24.46.1.101
   printer-device-service-count                  1.3.18.0.2.24.46.1.102
   printer-uuid                                  1.3.18.0.2.24.46.1.104
   printer-charge-info                           1.3.18.0.2.24.46.1.105
   printer-charge-info-uri                       1.3.18.0.2.24.46.1.106
   printer-geo-location                          1.3.18.0.2.24.46.1.107
   printer-ipp-features-supported                1.3.18.0.2.24.46.1.108













<span class="grey">Fleming &amp; McDonald            Informational                    [Page 43]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>.  Object Classes and Attribute Types from <a href="./rfc3712">RFC 3712</a></span>

   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
   <a href="#section-1.3.1">Section 1.3.1</a>) and were already registered by IANA when <a href="./rfc3712">RFC 3712</a> was
   published.

   Object Class                                  OID
   ------------------------------------          ----------------
   slpServicePrinter                             1.3.18.0.2.6.254
   printerAbstract                               1.3.18.0.2.6.258
   printerService                                1.3.18.0.2.6.255
   printerServiceAuxClass                        1.3.18.0.2.6.257
   printerIPP                                    1.3.18.0.2.6.256
   printerLPR                                    1.3.18.0.2.6.253

   The following Attribute Type OIDs were assigned by IBM (see
   <a href="#section-1.3.1">Section 1.3.1</a>) and were already registered by IANA when <a href="./rfc3712">RFC 3712</a> was
   published.

   Attribute Type                                OID
   ------------------------------------          -----------------
   printer-uri                                   1.3.18.0.2.4.1140
   printer-xri-supported                         1.3.18.0.2.4.1107
   printer-name                                  1.3.18.0.2.4.1135
   printer-natural-language-configured           1.3.18.0.2.4.1119
   printer-location                              1.3.18.0.2.4.1136
   printer-info                                  1.3.18.0.2.4.1139
   printer-more-info                             1.3.18.0.2.4.1134
   printer-make-and-model                        1.3.18.0.2.4.1138
   printer-ipp-versions-supported                1.3.18.0.2.4.1133
   printer-multiple-document-jobs-supported      1.3.18.0.2.4.1132
   printer-charset-configured                    1.3.18.0.2.4.1109
   printer-charset-supported                     1.3.18.0.2.4.1131
   printer-generated-natural-language-supported  1.3.18.0.2.4.1137
   printer-document-format-supported             1.3.18.0.2.4.1130
   printer-color-supported                       1.3.18.0.2.4.1129
   printer-compression-supported                 1.3.18.0.2.4.1128
   printer-pages-per-minute                      1.3.18.0.2.4.1127
   printer-pages-per-minute-color                1.3.18.0.2.4.1126
   printer-finishings-supported                  1.3.18.0.2.4.1125
   printer-number-up-supported                   1.3.18.0.2.4.1124
   printer-sides-supported                       1.3.18.0.2.4.1123
   printer-media-supported                       1.3.18.0.2.4.1122
   printer-media-local-supported                 1.3.18.0.2.4.1117
   printer-resolution-supported                  1.3.18.0.2.4.1121



<span class="grey">Fleming &amp; McDonald            Informational                    [Page 44]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


   printer-print-quality-supported               1.3.18.0.2.4.1120
   printer-job-priority-supported                1.3.18.0.2.4.1110
   printer-copies-supported                      1.3.18.0.2.4.1118
   printer-job-k-octets-supported                1.3.18.0.2.4.1111
   printer-current-operator                      1.3.18.0.2.4.1112
   printer-service-person                        1.3.18.0.2.4.1113
   printer-delivery-orientation-supported        1.3.18.0.2.4.1114
   printer-stacking-order-supported              1.3.18.0.2.4.1115
   printer-output-features-supported             1.3.18.0.2.4.1116
   printer-aliases                               1.3.18.0.2.4.1108

<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>.  Internationalization Considerations</span>

   All text string attributes defined in this document of syntax
   'DirectoryString' [<a href="./rfc4517" title="&quot;Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching Rules&quot;">RFC4517</a>] have values that are encoded in UTF-8
   [<a href="#ref-STD63" title="&quot;UTF-8, a transformation format of ISO 10646&quot;">STD63</a>], as required by [<a href="./rfc4517" title="&quot;Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching Rules&quot;">RFC4517</a>].

   A language tag [<a href="#ref-BCP47" title="&quot;Matching of Language Tags&quot;">BCP47</a>] 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 [<a href="#ref-BCP18" title="&quot;IETF Policy on Character Sets and Languages&quot;">BCP18</a>].

   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" [<a href="./rfc5198" title="&quot;Unicode Format for Network Interchange&quot;">RFC5198</a>];
   (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.

<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>.  Security Considerations</span>

   See [<a href="./rfc4513" title="&quot;Lightweight Directory Access Protocol (LDAP): Authentication Methods and Security Mechanisms&quot;">RFC4513</a>] for detailed guidance on authentication methods for
   LDAP and the use of TLS/1.2 [<a href="./rfc5246" title="&quot;The Transport Layer Security (TLS) Protocol Version 1.2&quot;">RFC5246</a>] 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.






<span class="grey">Fleming &amp; McDonald            Informational                    [Page 45]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


   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 <a href="./rfc2911#section-8">Section&nbsp;8 of [RFC2911]</a>.

<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>.  References</span>

<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>.  Normative References</span>

   [<a id="ref-BCP47">BCP47</a>]      Phillips, A. and M. Davis, "Matching of Language Tags",
                <a href="https://www.rfc-editor.org/bcp/bcp47">BCP 47</a>, <a href="./rfc4647">RFC 4647</a>, September 2006.

                Phillips, A., Ed., and M. Davis, Ed., "Tags for
                Identifying Languages", <a href="https://www.rfc-editor.org/bcp/bcp47">BCP 47</a>, <a href="./rfc5646">RFC 5646</a>,
                September 2009.

                &lt;<a href="http://www.rfc-editor.org/info/bcp47">http://www.rfc-editor.org/info/bcp47</a>&gt;

   [<a id="ref-IANACHAR">IANACHAR</a>]   Internet Assigned Numbers Authority (IANA) registry
                "Character Sets",
                &lt;<a href="http://www.iana.org/assignments/character-sets">http://www.iana.org/assignments/character-sets</a>&gt;.

   [<a id="ref-IANAIPP">IANAIPP</a>]    Internet Assigned Numbers Authority (IANA) registry
                "Internet Printing Protocol (IPP) Registrations",
                &lt;<a href="http://www.iana.org/assignments/ipp-registrations">http://www.iana.org/assignments/ipp-registrations</a>&gt;.

   [<a id="ref-IANAMIME">IANAMIME</a>]   Internet Assigned Numbers Authority (IANA) registry
                "Media Types", &lt;<a href="http://www.iana.org/assignments/media-types/index.html">http://www.iana.org/assignments/</a>
                <a href="http://www.iana.org/assignments/media-types/index.html">media-types/index.html</a>&gt;.

   [<a id="ref-PWG5100.5">PWG5100.5</a>]  Carney, D., Hastings, T., and P. Zehler, "IPP Document
                Object", PWG 5100.5-2003, October 2003,
                &lt;<a href="http://www.pwg.org/standards.html">http://www.pwg.org/standards.html</a>&gt;.

   [<a id="ref-PWG5100.6">PWG5100.6</a>]  Zehler, P., Herriot, R., and K. Ocke, "IPP Page
                Overrides", PWG 5100.6-2003, October 2003,
                &lt;<a href="http://www.pwg.org/standards.html">http://www.pwg.org/standards.html</a>&gt;.

   [<a id="ref-PWG5100.11">PWG5100.11</a>] Hastings, T. and D. Fullman, "IPP Job and Printer
                Extensions - Set 2 (JPS2)", PWG 5100.11-2010,
                October 2010, &lt;<a href="http://www.pwg.org/standards.html">http://www.pwg.org/standards.html</a>&gt;.

   [<a id="ref-PWG5100.12">PWG5100.12</a>] 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,
                &lt;<a href="http://www.pwg.org/standards.html">http://www.pwg.org/standards.html</a>&gt;.



<span class="grey">Fleming &amp; McDonald            Informational                    [Page 46]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-47" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


   [<a id="ref-PWG5100.13">PWG5100.13</a>] Sweet, M., McDonald, I., and P. Zehler, "IPP Job and
                Printer Extensions - Set 3 (JPS3)", PWG 5100.13-2012,
                July 2012, &lt;<a href="http://www.pwg.org/standards.html">http://www.pwg.org/standards.html</a>&gt;.

   [<a id="ref-PWG5100.14">PWG5100.14</a>] Sweet, M., McDonald, I., Mitchell, A., and J. Hutchings,
                "IPP Everywhere", PWG 5100.14-2013, January 2013,
                &lt;<a href="http://www.pwg.org/standards.html">http://www.pwg.org/standards.html</a>&gt;.

   [<a id="ref-PWG5101.1">PWG5101.1</a>]  Sweet, M., Bergman, R., and T. Hastings, "PWG Media
                Standardized Names 2.0 (MSN2)", PWG 5101.1-2013,
                March 2013, &lt;<a href="http://www.pwg.org/standards.html">http://www.pwg.org/standards.html</a>&gt;.

   [<a id="ref-PWG5107.2">PWG5107.2</a>]  McDonald, I., "PWG Command Set Format for IEEE 1284
                Device ID v1.0", PWG 5107.2-2010, May 2010,
                &lt;<a href="http://www.pwg.org/standards.html">http://www.pwg.org/standards.html</a>&gt;.

   [<a id="ref-RFC2119">RFC2119</a>]    Bradner, S., "Key words for use in RFCs to Indicate
                Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>,
                DOI 10.17487/RFC2119, March 1997,
                &lt;<a href="http://www.rfc-editor.org/info/rfc2119">http://www.rfc-editor.org/info/rfc2119</a>&gt;.

   [<a id="ref-RFC2617">RFC2617</a>]    Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence,
                S., Leach, P., Luotonen, A., and L. Stewart, "HTTP
                Authentication: Basic and Digest Access Authentication",
                <a href="./rfc2617">RFC 2617</a>, DOI 10.17487/RFC2617, June 1999,
                &lt;<a href="http://www.rfc-editor.org/info/rfc2617">http://www.rfc-editor.org/info/rfc2617</a>&gt;.

   [<a id="ref-RFC2707">RFC2707</a>]    Bergman, R., Hastings, T., Isaacson, S., and H. Lewis,
                "Job Monitoring MIB - V1.0", <a href="./rfc2707">RFC 2707</a>,
                DOI 10.17487/RFC2707, November 1999,
                &lt;<a href="http://www.rfc-editor.org/info/rfc2707">http://www.rfc-editor.org/info/rfc2707</a>&gt;.

   [<a id="ref-RFC2911">RFC2911</a>]    Hastings, T., Ed., Herriot, R., deBry, R., Isaacson, S.,
                and P. Powell, "Internet Printing Protocol/1.1: Model
                and Semantics", <a href="./rfc2911">RFC 2911</a>, DOI 10.17487/RFC2911,
                September 2000,
                &lt;<a href="http://www.rfc-editor.org/info/rfc2911">http://www.rfc-editor.org/info/rfc2911</a>&gt;.

   [<a id="ref-RFC2926">RFC2926</a>]    Kempf, J., Moats, R., and P. St. Pierre, "Conversion of
                LDAP Schemas to and from SLP Templates", <a href="./rfc2926">RFC 2926</a>,
                DOI 10.17487/RFC2926, September 2000,
                &lt;<a href="http://www.rfc-editor.org/info/rfc2926">http://www.rfc-editor.org/info/rfc2926</a>&gt;.

   [<a id="ref-RFC3510">RFC3510</a>]    Herriot, R. and I. McDonald, "Internet Printing
                Protocol/1.1: IPP URL Scheme", <a href="./rfc3510">RFC 3510</a>,
                DOI 10.17487/RFC3510, April 2003,
                &lt;<a href="http://www.rfc-editor.org/info/rfc3510">http://www.rfc-editor.org/info/rfc3510</a>&gt;.




<span class="grey">Fleming &amp; McDonald            Informational                    [Page 47]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-48" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


   [<a id="ref-RFC3805">RFC3805</a>]    Bergman, R., Lewis, H., and I. McDonald, "Printer
                MIB v2", <a href="./rfc3805">RFC 3805</a>, DOI 10.17487/RFC3805, June 2004,
                &lt;<a href="http://www.rfc-editor.org/info/rfc3805">http://www.rfc-editor.org/info/rfc3805</a>&gt;.

   [<a id="ref-RFC3987">RFC3987</a>]    Duerst, M. and M. Suignard, "Internationalized Resource
                Identifiers (IRIs)", <a href="./rfc3987">RFC 3987</a>, DOI 10.17487/RFC3987,
                January 2005, &lt;<a href="http://www.rfc-editor.org/info/rfc3987">http://www.rfc-editor.org/info/rfc3987</a>&gt;.

   [<a id="ref-RFC3995">RFC3995</a>]    Herriot, R. and T. Hastings, "Internet Printing Protocol
                (IPP): Event Notifications and Subscriptions", <a href="./rfc3995">RFC 3995</a>,
                DOI 10.17487/RFC3995, March 2005,
                &lt;<a href="http://www.rfc-editor.org/info/rfc3995">http://www.rfc-editor.org/info/rfc3995</a>&gt;.

   [<a id="ref-RFC4122">RFC4122</a>]    Leach, P., Mealling, M., and R. Salz, "A Universally
                Unique IDentifier (UUID) URN Namespace", <a href="./rfc4122">RFC 4122</a>,
                DOI 10.17487/RFC4122, July 2005,
                &lt;<a href="http://www.rfc-editor.org/info/rfc4122">http://www.rfc-editor.org/info/rfc4122</a>&gt;.

   [<a id="ref-RFC4510">RFC4510</a>]    Zeilenga, K., Ed., "Lightweight Directory Access
                Protocol (LDAP): Technical Specification Road Map",
                <a href="./rfc4510">RFC 4510</a>, DOI 10.17487/RFC4510, June 2006,
                &lt;<a href="http://www.rfc-editor.org/info/rfc4510">http://www.rfc-editor.org/info/rfc4510</a>&gt;.

   [<a id="ref-RFC4513">RFC4513</a>]    Harrison, R., Ed., "Lightweight Directory Access
                Protocol (LDAP): Authentication Methods and Security
                Mechanisms", <a href="./rfc4513">RFC 4513</a>, DOI 10.17487/RFC4513, June 2006,
                &lt;<a href="http://www.rfc-editor.org/info/rfc4513">http://www.rfc-editor.org/info/rfc4513</a>&gt;.

   [<a id="ref-RFC4517">RFC4517</a>]    Legg, S., Ed., "Lightweight Directory Access Protocol
                (LDAP): Syntaxes and Matching Rules", <a href="./rfc4517">RFC 4517</a>,
                DOI 10.17487/RFC4517, June 2006,
                &lt;<a href="http://www.rfc-editor.org/info/rfc4517">http://www.rfc-editor.org/info/rfc4517</a>&gt;.

   [<a id="ref-RFC4524">RFC4524</a>]    Zeilenga, K., Ed., "COSINE LDAP/X.500 Schema", <a href="./rfc4524">RFC 4524</a>,
                DOI 10.17487/RFC4524, June 2006,
                &lt;<a href="http://www.rfc-editor.org/info/rfc4524">http://www.rfc-editor.org/info/rfc4524</a>&gt;.

   [<a id="ref-RFC5198">RFC5198</a>]    Klensin, J. and M. Padlipsky, "Unicode Format for
                Network Interchange", <a href="./rfc5198">RFC 5198</a>, DOI 10.17487/RFC5198,
                March 2008, &lt;<a href="http://www.rfc-editor.org/info/rfc5198">http://www.rfc-editor.org/info/rfc5198</a>&gt;.

   [<a id="ref-RFC5246">RFC5246</a>]    Dierks, T. and E. Rescorla, "The Transport Layer
                Security (TLS) Protocol Version 1.2", <a href="./rfc5246">RFC 5246</a>,
                DOI 10.17487/RFC5246, August 2008,
                &lt;<a href="http://www.rfc-editor.org/info/rfc5246">http://www.rfc-editor.org/info/rfc5246</a>&gt;.






<span class="grey">Fleming &amp; McDonald            Informational                    [Page 48]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-49" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


   [<a id="ref-RFC5280">RFC5280</a>]    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", <a href="./rfc5280">RFC 5280</a>, DOI 10.17487/RFC5280,
                May 2008, &lt;<a href="http://www.rfc-editor.org/info/rfc5280">http://www.rfc-editor.org/info/rfc5280</a>&gt;.

   [<a id="ref-RFC5870">RFC5870</a>]    Mayrhofer, A. and C. Spanring, "A Uniform Resource
                Identifier for Geographic Locations ('geo' URI)",
                <a href="./rfc5870">RFC 5870</a>, DOI 10.17487/RFC5870, June 2010,
                &lt;<a href="http://www.rfc-editor.org/info/rfc5870">http://www.rfc-editor.org/info/rfc5870</a>&gt;.

   [<a id="ref-RFC6818">RFC6818</a>]    Yee, P., "Updates to the Internet X.509 Public Key
                Infrastructure Certificate and Certificate Revocation
                List (CRL) Profile", <a href="./rfc6818">RFC 6818</a>, DOI 10.17487/RFC6818,
                January 2013, &lt;<a href="http://www.rfc-editor.org/info/rfc6818">http://www.rfc-editor.org/info/rfc6818</a>&gt;.

   [<a id="ref-RFC7235">RFC7235</a>]    Fielding, R., Ed., and J. Reschke, Ed., "Hypertext
                Transfer Protocol (HTTP/1.1): Authentication", <a href="./rfc7235">RFC 7235</a>,
                DOI 10.17487/RFC7235, June 2014,
                &lt;<a href="http://www.rfc-editor.org/info/rfc7235">http://www.rfc-editor.org/info/rfc7235</a>&gt;.

   [<a id="ref-RFC7472">RFC7472</a>]    McDonald, I. and M. Sweet, "Internet Printing Protocol
                (IPP) over HTTPS Transport Binding and the 'ipps' URI
                Scheme", <a href="./rfc7472">RFC 7472</a>, DOI 10.17487/RFC7472, March 2015,
                &lt;<a href="http://www.rfc-editor.org/info/rfc7472">http://www.rfc-editor.org/info/rfc7472</a>&gt;.

   [<a id="ref-STD63">STD63</a>]      Yergeau, F., "UTF-8, a transformation format of ISO
                10646", STD 63, <a href="./rfc3629">RFC 3629</a>, November 2003,
                &lt;<a href="http://www.rfc-editor.org/info/std63">http://www.rfc-editor.org/info/std63</a>&gt;.

   [<a id="ref-STD66">STD66</a>]      Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
                Resource Identifier (URI): Generic Syntax", STD 66, <a href="./rfc3986">RFC</a>
                <a href="./rfc3986">3986</a>, January 2005,
                &lt;<a href="http://www.rfc-editor.org/info/std66">http://www.rfc-editor.org/info/std66</a>&gt;.

















<span class="grey">Fleming &amp; McDonald            Informational                    [Page 49]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-50" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>.  Informative References</span>

   [<a id="ref-BCP13">BCP13</a>]      Freed, N. and J. Klensin, "Multipurpose Internet Mail
                Extensions (MIME) Part Four: Registration Procedures",
                <a href="https://www.rfc-editor.org/bcp/bcp13">BCP 13</a>, <a href="./rfc4289">RFC 4289</a>, December 2005.

                Freed, N., Klensin, J., and T. Hansen, "Media Type
                Specifications and Registration Procedures", <a href="https://www.rfc-editor.org/bcp/bcp13">BCP 13</a>,
                <a href="./rfc6838">RFC 6838</a>, January 2013.

                &lt;<a href="http://www.rfc-editor.org/info/bcp13">http://www.rfc-editor.org/info/bcp13</a>&gt;

   [<a id="ref-BCP18">BCP18</a>]      Alvestrand, H., "IETF Policy on Character Sets and
                Languages", <a href="https://www.rfc-editor.org/bcp/bcp18">BCP 18</a>, <a href="./rfc2277">RFC 2277</a>, January 1998,
                &lt;<a href="http://www.rfc-editor.org/info/bcp18">http://www.rfc-editor.org/info/bcp18</a>&gt;.

   [<a id="ref-BCP19">BCP19</a>]      Freed, N. and J. Postel, "IANA Charset Registration
                Procedures", <a href="https://www.rfc-editor.org/bcp/bcp19">BCP 19</a>, <a href="./rfc2978">RFC 2978</a>, October 2000,
                &lt;<a href="http://www.rfc-editor.org/info/bcp19">http://www.rfc-editor.org/info/bcp19</a>&gt;.

   [<a id="ref-RFC1179">RFC1179</a>]    McLaughlin, L., "Line printer daemon protocol",
                <a href="./rfc1179">RFC 1179</a>, DOI 10.17487/RFC1179, August 1990,
                &lt;<a href="http://www.rfc-editor.org/info/rfc1179">http://www.rfc-editor.org/info/rfc1179</a>&gt;.

   [<a id="ref-RFC1951">RFC1951</a>]    Deutsch, P., "DEFLATE Compressed Data Format
                Specification version 1.3", <a href="./rfc1951">RFC 1951</a>,
                DOI 10.17487/RFC1951, May 1996,
                &lt;<a href="http://www.rfc-editor.org/info/rfc1951">http://www.rfc-editor.org/info/rfc1951</a>&gt;.

   [<a id="ref-RFC1952">RFC1952</a>]    Deutsch, P., "GZIP file format specification
                version 4.3", <a href="./rfc1952">RFC 1952</a>, DOI 10.17487/RFC1952, May 1996,
                &lt;<a href="http://www.rfc-editor.org/info/rfc1952">http://www.rfc-editor.org/info/rfc1952</a>&gt;.

   [<a id="ref-RFC1977">RFC1977</a>]    Schryver, V., "PPP BSD Compression Protocol", <a href="./rfc1977">RFC 1977</a>,
                DOI 10.17487/RFC1977, August 1996,
                &lt;<a href="http://www.rfc-editor.org/info/rfc1977">http://www.rfc-editor.org/info/rfc1977</a>&gt;.

   [<a id="ref-RFC2079">RFC2079</a>]    Smith, M., "Definition of an X.500 Attribute Type and an
                Object Class to Hold Uniform Resource Identifiers
                (URIs)", <a href="./rfc2079">RFC 2079</a>, DOI 10.17487/RFC2079, January 1997,
                &lt;<a href="http://www.rfc-editor.org/info/rfc2079">http://www.rfc-editor.org/info/rfc2079</a>&gt;.

   [<a id="ref-RFC2566">RFC2566</a>]    deBry, R., Hastings, T., Herriot, R., Isaacson, S., and
                P. Powell, "Internet Printing Protocol/1.0: Model and
                Semantics", <a href="./rfc2566">RFC 2566</a>, DOI 10.17487/RFC2566, April 1999,
                &lt;<a href="http://www.rfc-editor.org/info/rfc2566">http://www.rfc-editor.org/info/rfc2566</a>&gt;.





<span class="grey">Fleming &amp; McDonald            Informational                    [Page 50]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-51" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


   [<a id="ref-RFC2608">RFC2608</a>]    Guttman, E., Perkins, C., Veizades, J., and M. Day,
                "Service Location Protocol, Version 2", <a href="./rfc2608">RFC 2608</a>,
                DOI 10.17487/RFC2608, June 1999,
                &lt;<a href="http://www.rfc-editor.org/info/rfc2608">http://www.rfc-editor.org/info/rfc2608</a>&gt;.

   [<a id="ref-RFC3712">RFC3712</a>]    Fleming, P. and I. McDonald, "Lightweight Directory
                Access Protocol (LDAP): Schema for Printer Services",
                <a href="./rfc3712">RFC 3712</a>, DOI 10.17487/RFC3712, February 2004,
                &lt;<a href="http://www.rfc-editor.org/info/rfc3712">http://www.rfc-editor.org/info/rfc3712</a>&gt;.

   [<a id="ref-RFC4559">RFC4559</a>]    Jaganathan, K., Zhu, L., and J. Brezak, "SPNEGO-based
                Kerberos and NTLM HTTP Authentication in Microsoft
                Windows", <a href="./rfc4559">RFC 4559</a>, DOI 10.17487/RFC4559, June 2006,
                &lt;<a href="http://www.rfc-editor.org/info/rfc4559">http://www.rfc-editor.org/info/rfc4559</a>&gt;.

   [<a id="ref-SLPPRT20">SLPPRT20</a>]   IANA, "Service Location Protocol, Version 2 (SLPv2)
                Templates",
                &lt;<a href="http://www.iana.org/assignments/svrloc-templates">http://www.iana.org/assignments/svrloc-templates</a>&gt;.

































<span class="grey">Fleming &amp; McDonald            Informational                    [Page 51]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-52" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>.  Changes since <a href="./rfc3712">RFC 3712</a></span>

   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 [<a href="./rfc3712" title="&quot;Lightweight Directory Access Protocol (LDAP): Schema for Printer Services&quot;">RFC3712</a>] and
        underlying string length limits in [<a href="./rfc2707" title="&quot;Job Monitoring MIB - V1.0&quot;">RFC2707</a>], [<a href="./rfc2911" title="&quot;Internet Printing Protocol/1.1: Model and Semantics&quot;">RFC2911</a>],
        [<a href="./rfc3805" title="&quot;Printer MIB v2&quot;">RFC3805</a>], [<a href="#ref-PWG5107.2" title="&quot;PWG Command Set Format for IEEE 1284 Device ID v1.0&quot;">PWG5107.2</a>], [<a href="#ref-PWG5100.13" title="&quot;IPP Job and Printer Extensions - Set 3 (JPS3)&quot;">PWG5100.13</a>], and [<a href="#ref-PWG5100.14" title="&quot;IPP Everywhere&quot;">PWG5100.14</a>].

   3) Added new Printer attributes defined in [<a href="#ref-PWG5107.2" title="&quot;PWG Command Set Format for IEEE 1284 Device ID v1.0&quot;">PWG5107.2</a>], [<a href="#ref-PWG5100.13" title="&quot;IPP Job and Printer Extensions - Set 3 (JPS3)&quot;">PWG5100.13</a>],
      and [<a href="#ref-PWG5100.14" title="&quot;IPP Everywhere&quot;">PWG5100.14</a>] (see <a href="#section-7.1">Section 7.1</a>)

      - updated the table of Printer attributes and source documents in
        <a href="#section-4">Section 4</a> ("Definition of Attribute Types");

      - added support for IEEE-ISTO PWG "IPP Everywhere" [<a href="#ref-PWG5100.14" title="&quot;IPP Everywhere&quot;">PWG5100.14</a>]
        project.

   4) Added implementation note to <a href="#section-4">Section 4</a> 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.










<span class="grey">Fleming &amp; McDonald            Informational                    [Page 52]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-53" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


   6) Clarified use of printer-xri-supported and
      printer-resolution-supported attributes, and their corresponding
      field delimiters

      - added note in <a href="#section-4">Section 4</a> ("Definition of Attribute Types") to
        explain the origin of the different field delimiters;

      - added examples to show optional *trailing* whitespace after '&lt;'
        delimiters in printer-xri-supported;

      - added examples to show optional *trailing* whitespace after '&gt;'
        delimiters in printer-resolution-supported.

   7) Clarified <a href="#section-8">Section 8</a> ("Internationalization Considerations")

      - added note about Net-Unicode [<a href="./rfc5198" title="&quot;Unicode Format for Network Interchange&quot;">RFC5198</a>] and avoiding use of C0
        and C1 control characters.

   8) Clarified <a href="#section-9">Section 9</a> ("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 <a href="#section-2">Section 2</a> ("Conventions Used in This Document");

      - added <a href="#section-2.1">Section 2.1</a> ("Requirements Language");

      - added <a href="#section-2.2">Section 2.2</a> ("LDAP Schema Descriptions");

      - added <a href="#section-2.3">Section 2.3</a> ("Abbreviations").



















<span class="grey">Fleming &amp; McDonald            Informational                    [Page 53]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-54" ></span>
<span class="grey"><a href="./rfc7612">RFC 7612</a>            LDAP Schema for Printer Services           June 2015</span>


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
   [<a href="./rfc3712" title="&quot;Lightweight Directory Access Protocol (LDAP): Schema for Printer Services&quot;">RFC3712</a>].

   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: patfleminghtc@gmail.com


   Ira McDonald
   High North Inc.
   221 Ridge Ave.
   Grand Marais, MI  49839
   United States

   Phone: +1 906-494-2434
   Email: blueroofmusic@gmail.com















Fleming &amp; McDonald            Informational                    [Page 54]
</pre>