[Docs] [txt|pdf] [Tracker] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 04 05 06 07 08 09 10 11 12 13 RFC 7612

Network Working Group                                        Pat Fleming
INTERNET-DRAFT                                                       IBM
Obsoletes: 3712 (if approved)                               Ira McDonald
Intended Status: Standards Track                              High North
Expires: 20 November 2012                                    20 May 2012


             Lightweight Directory Access Protocol (LDAP):
                      Schema for Printer Services
              <draft-mcdonald-ldap-printer-schema-02.txt>


Abstract

   This document defines a schema, object classes and attributes, for
   Printers and Print Services, for use with directories that support
   Lightweight Directory Access Protocol (RFC 4510).  This document is
   based on the Printer attributes listed in Appendix E of Internet
   Printing Protocol/1.1 (IPP) (RFC 2911).  Additional Printer
   attributes are based on definitions in the Printer MIB v2 (RFC 3805),
   IEEE-ISTO PWG Command Set for IEEE 1284 Device ID (PWG 5107.2),
   IEEE-ISTO PWG IPP Job and Printer Extensions - Set 3 (PWG 5100.JPS3),
   and IEEE-ISTO PWG IPP Everywhere (PWG 5100.EVE).


Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on 20 November 2012.


Copyright Notice



Fleming, McDonald           Expires 20 November 2012            [Page 1]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012

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

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) 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.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.








































Fleming, McDonald           Expires 20 November 2012            [Page 2]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012

                           Table of Contents

1.  Introduction ...............................................       5
  1.1.  Rationale for using DirectoryString Syntax .............       5
  1.2.  Rationale for using caseIgnoreMatch ....................       6
  1.3.  Rationale for using caseIgnoreSubstringsMatch ..........       7
2.  Terminology and Conventions ................................       7
3.  Definition of Object Classes ...............................       9
  3.1.  slpServicePrinter ......................................      10
  3.2.  printerAbstract ........................................      10
  3.3.  printerService .........................................      11
  3.4.  printerServiceAuxClass .................................      11
  3.5.  printerIPP .............................................      12
  3.6.  printerLPR .............................................      12
4.  Definition of Attribute Types ..............................      13
  4.1.  printer-uri ............................................      15
  4.2.  printer-xri-supported ..................................      15
  4.3.  printer-name ...........................................      17
  4.4.  printer-natural-language-configured ....................      17
  4.5.  printer-location .......................................      18
  4.6.  printer-info ...........................................      18
  4.7.  printer-more-info ......................................      19
  4.8.  printer-make-and-model .................................      19
  4.9.  printer-ipp-versions-supported .........................      20
  4.10.  printer-multiple-document-jobs-supported ..............      20
  4.11.  printer-charset-configured ............................      21
  4.12.  printer-charset-supported .............................      21
  4.13.  printer-generated-natural-language-supported ..........      22
  4.14.  printer-document-format-supported .....................      22
  4.15.  printer-color-supported ...............................      22
  4.16.  printer-compression-supported .........................      23
  4.17.  printer-pages-per-minute ..............................      23
  4.18.  printer-pages-per-minute-color ........................      24
  4.19.  printer-finishings-supported ..........................      24
  4.20.  printer-number-up-supported ...........................      25
  4.21.  printer-sides-supported ...............................      25
  4.22.  printer-media-supported ...............................      25
  4.23.  printer-media-local-supported .........................      26
  4.24.  printer-resolution-supported ..........................      26
  4.25.  printer-print-quality-supported .......................      27
  4.26.  printer-job-priority-supported ........................      28
  4.27.  printer-copies-supported ..............................      28
  4.28.  printer-job-k-octets-supported ........................      28
  4.29.  printer-current-operator ..............................      29
  4.30.  printer-service-person ................................      29
  4.31.  printer-delivery-orientation-supported ................      30
  4.32.  printer-stacking-order-supported ......................      30
  4.33.  printer-output-features-supported .....................      31
  4.34.  printer-aliases .......................................      32
  4.35.  printer-device-id .....................................      32
  4.36.  printer-device-service-count ..........................      33

Fleming, McDonald           Expires 20 November 2012            [Page 3]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012

  4.37.  printer-device-uuid ...................................      33
  4.38.  printer-uuid ..........................................      34
  4.39.  printer-charge-info ...................................      34
  4.40.  printer-charge-info-uri ...............................      35
  4.41.  printer-geo-location ..................................      35
  4.42.  printer-ipp-features-supported ........................      35
5.  Definition of Syntaxes .....................................      37
6.  Definition of Matching Rules ...............................      37
7.  IANA Considerations ........................................      38
  7.1.  Registration of Object Classes .........................      38
  7.2.  Registration of Attribute Types ........................      39
8.  Internationalization Considerations ........................      41
9.  Security Considerations ....................................      41
10.  References ................................................      42
  10.1.  Normative References ..................................      42
  10.2.  Informative References ................................      44
11.  Appendix A - Acknowledgments ..............................      45
12.  Appendix X - Change History ...............................      46
13.  Authors' Addresses ........................................      48

































Fleming, McDonald           Expires 20 November 2012            [Page 4]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012



1.  Introduction

   This document defines several object classes to provide Lightweight
   Directory Access Protocol [RFC4510] applications with flexible
   options in defining Printer information using LDAP schema.  Classes
   are provided for defining directory entries with common Printer
   information as well as for extending existing directory entries with
   SLPv2 [RFC2608], IPP/1.1 [RFC2911], and LPR [RFC1179]
   protocol-specific information.

   The schema defined in this document is based on the Printer
   attributes listed in Appendix E 'Generic Directory Schema' of
   Internet Printing Protocol/1.1 (IPP) [RFC2911].  Additional Printer
   attributes are based on definitions in the Printer MIB v2 [RFC3805],
   IEEE-ISTO PWG Command Set for IEEE 1284 Device ID [PWG5107.2], or
   IEEE-ISTO PWG IPP Job and Printer Extensions - Set 3 [PWG5100.JPS3].

   The schema defined in this document is technically aligned with the
   stable IANA-registered 'service:printer:' v2.0 template [SLPPRT20],
   for compatibility with already deployed Service Location Protocol
   (SLPv2) [RFC2608] 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' [RFC4517] rather than
   'labeledURI' [RFC2079] for the 'printer-uri' attribute).

   Please send comments directly to the authors at the addresses listed
   in the section "Authors' Addresses".



   1.1.  Rationale for using DirectoryString Syntax

   The attribute syntax 'DirectoryString' (UTF-8 [STD63]) defined in
   [RFC4517] 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-device-uuid, printer-charge-info-uri, printer-uuid

       The UTF-8 encoding is compatible with deployment of (UTF-8 based)
       IRI Internationalized Resource Identifiers (IRIs) [RFC3987].

   2)  Description
       - printer-name, printer-location, printer-info,
       printer-make-and-model

       The UTF-8 encoding supports descriptions in any language,

Fleming, McDonald           Expires 20 November 2012            [Page 5]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012

       conformant with the IETF Policy on Character Sets and Languages
       [BCP18].

       Note:  The printer-natural-language-configured attribute contains
       a language tag [BCP47] for these description attributes (for
       example, to support text-to-speech conversions).

   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
       [RFC2911] 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' which 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.



   1.2.  Rationale for using caseIgnoreMatch

   The EQUALITY matching rule 'caseIgnoreMatch' defined in [RFC4517] 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 [STD66], 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 [RFC4524].

       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).

Fleming, McDonald           Expires 20 November 2012            [Page 6]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012


   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.



   1.3.  Rationale for using caseIgnoreSubstringsMatch

   The SUBSTR matching rule 'caseIgnoreSubstringsMatch' defined in
   [RFC4517] 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 [RFC4524].

   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.



2.  Terminology and Conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this

Fleming, McDonald           Expires 20 November 2012            [Page 7]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012

   document are to be interpreted as described in [RFC2119].

   Schema definitions are provided using LDAP [RFC4510] description
   formats.  Definitions provided here are formatted (line wrapped) for
   readability.















































Fleming, McDonald           Expires 20 November 2012            [Page 8]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012



3.  Definition of Object Classes

   We define the following LDAP object classes for use with both generic
   Printer related information and services specific to SLPv2 [RFC2608],
   IPP/1.1 [RFC2911], and LPR [RFC1179].

   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 Section 4 for 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 [RFC2911] have been prefixed with 'printer-' as recommended in
   [RFC2926] and [SLPPRT20].












Fleming, McDonald           Expires 20 November 2012            [Page 9]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012



   3.1.  slpServicePrinter

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

   This auxiliary class defines Service Location Protocol (SLPv2)
   [RFC2608] specific information.  It SHOULD be used with a structural
   class such as printerService.  It MAY be used to create new or extend
   existing directory entries with SLP 'service:printer' abstract
   service type information as defined in [SLPPRT20].  This object class
   is derived from 'slpService', the parent class for all SLP services,
   defined in [RFC2926].



   3.2.  printerAbstract

   ( 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 $ 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 $

Fleming, McDonald           Expires 20 November 2012           [Page 10]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012

           printer-device-uuid $
           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.



   3.3.  printerService

   ( 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 protocol, service or
   operating system specific information.

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



   3.4.  printerServiceAuxClass

   ( 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.
   This class SHOULD be used with a structural class.


Fleming, McDonald           Expires 20 November 2012           [Page 11]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012




   3.5.  printerIPP

   ( 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)
   [RFC2911] information.  It SHOULD be used with a structural class
   such as printerService.  It is used to extend structural classes with
   IPP specific Printer information.

   Note:  See IPP URL Scheme [RFC3510] and IPP over HTTPS Transport
   Binding and 'ipps' URI Scheme [IPPSURI] for conforming URI for IPP
   Printers.



   3.6.  printerLPR

   ( 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 [RFC1179] information.  It SHOULD be
   used with a structural class such as printerService.  It is used to
   identify directory entries that support LPR.












Fleming, McDonald           Expires 20 November 2012           [Page 12]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012



4.  Definition of Attribute Types

   The following attribute types are referenced by the object classes
   defined in Section 3.

   The following attribute types reference syntax OIDs defined in
   Section 3 of [RFC4517] (see Section 5 'Definition of Syntaxes'
   below).

   The following attribute types reference matching rule names (instead
   of OIDs) for clarity (see Section 6 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 Section 4 of [RFC4517] (see Section 6 'Definition of
   Matching Rules' below).

   The following table is a summary of the attribute names defined by
   this document and their corresponding source document names as
   defined in [RFC2911], [RFC3805], [PWG5107.2], or [PWG5100.JPS3].
   Some source attribute names have been prefixed with 'printer-' as
   recommended in [RFC2926], to address the flat namespace for LDAP
   identifiers.

   LDAP & SLP Printer Schema       Source Document and Attribute Name
   ------------------------------  -------------------------------------
   ***                             IPP/1.1 and Semantics Model [RFC2911]
   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

Fleming, McDonald           Expires 20 November 2012           [Page 13]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012

   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

   ***                             Printer MIB v2 [RFC3805]
   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 [PWG5107.2]
   printer-device-id               printer-device-id

   ***                             IPP Job/PrinterExt Set 3 [PWG5100.JPS
   printer-device-service-count    device-service-count
   printer-device-uuid             device-uuid
   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














Fleming, McDonald           Expires 20 November 2012           [Page 14]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012



   4.1.  printer-uri

   ( 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{255}
   SINGLE-VALUE
   )

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

   Values of URI SHOULD conform to [STD66], although URI schemes can be
   defined which do not conform to [STD66] (see [BCP35]).

   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 IPP URL Scheme [RFC3510] and IPP over HTTPS Transport
   Binding and 'ipps' URI Scheme [IPPSURI] 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 [RFC2608] service discovery.

   Note:  See Sections 1.1, 1.2, and 1.3 for rationale for design
   choices.



   4.2.  printer-xri-supported

   ( 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{255}
   )

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


Fleming, McDonald           Expires 20 November 2012           [Page 15]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012


   Values of URI SHOULD conform to [STD66], although URI schemes can be
   defined which do not conform to [STD66] (see [BCP35]).

   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 'printer-uri-supported',
   'uri-authentication-supported', and 'uri-security-supported' (called
   the 'Three Musketeers' because they are parallel ordered attributes)
   defined in IPP/1.1 [RFC2911].  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 [RFC2911], IPP Job and Printer Extensions - Set 3
   [PWG5100.JPS3], and IANA IPP Registry [IANAIPP], defined values of
   the 'auth' field include:

       'none' (no authentication for this URI)
       'requesting-user-name' (from operation request)
       'basic' (HTTP/1.1 Basic [RFC2617])
       'digest' (HTTP/1.1 Digest [RFC2617])
       'certificate' (X.509 Certificate [RFC5280])
       'negotiate' (HTTP/1.1 Negotiate [RFC4559])

   A missing 'sec' field SHOULD be interpreted to mean 'none'.  Per
   IPP/1.1 [RFC2911] and IANA IPP Registry [IANAIPP], defined values of
   the 'sec' field include:

       'none' (no security for this URI)
       'ssl3' (Netscape SSL3)
       'tls' (IETF TLS, [RFC5246])

   Each XRI field MUST be delimited by '<'.  For example:

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

   Note:  The syntax and delimiter for this attribute are aligned with
   the equivalent attribute in the 'service:printer:' v2.0 template
   [SLPPRT20].  Whitespace is permitted after (but not before) the

Fleming, McDonald           Expires 20 November 2012           [Page 16]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012

   delimiter '<'.

   Note:  See IPP URL Scheme [RFC3510] and IPP over HTTPS Transport
   Binding and 'ipps' URI Scheme [IPPSURI] for conforming URI for IPP
   Printers.

   Note:  See Sections 1.1, 1.2, and 1.3 for rationale for design
   choices.



   4.3.  printer-name

   ( 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{127}
   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.  This name MAY be the last part of the
   Printer's URI or it MAY be completely unrelated.  This name MAY
   contain characters that are not allowed in a conventional URI (see
   [STD66]).



   4.4.  printer-natural-language-configured

   ( 1.3.18.0.2.4.1119
   NAME 'printer-natural-language-configured'
   DESC 'The configured natural language in which error and status
         messages will be generated (by default) by this Printer.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15{63}
   SINGLE-VALUE
   )

   Also, a possible natural language for Printer 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 SHOULD conform to Tags for Identifying
   Languages [BCP47].  For example:

Fleming, McDonald           Expires 20 November 2012           [Page 17]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012


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

   Note:  For consistency with IPP/1.1 [RFC2911], language tags in this
   attribute SHOULD be lowercase normalized.



   4.5.  printer-location

   ( 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{127}
   SINGLE-VALUE
   )

   For example:

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

   Note:  For interoperability and consistent text display, values of
   this attribute:  (a) SHOULD be normalized as recommended in Unicode
   Format for Network Interchange [RFC5198]; (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).



   4.6.  printer-info

   ( 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{127}
   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

Fleming, McDonald           Expires 20 November 2012           [Page 18]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012

        Printer'

   Note:  For interoperability and consistent text display, values of
   this attribute:  (a) SHOULD be normalized as recommended in Unicode
   Format for Network Interchange [RFC5198]; (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).



   4.7.  printer-more-info

   ( 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{255}
   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.

   Values of URI SHOULD conform to [STD66], although URI schemes can be
   defined which do not conform to [STD66] (see [BCP35]).

   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 1.1, 1.2, and 1.3 for rationale for design
   choices.



   4.8.  printer-make-and-model

   ( 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{127}
   SINGLE-VALUE
   )

   Note:  The Printer manufacturer MAY initially populate this
   attribute.


Fleming, McDonald           Expires 20 November 2012           [Page 19]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012


   Note:  For interoperability and consistent text display, values of
   this attribute:  (a) SHOULD be normalized as recommended in Unicode
   Format for Network Interchange [RFC5198]; (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).



   4.9.  printer-ipp-versions-supported

   ( 1.3.18.0.2.4.1133
   NAME 'printer-ipp-versions-supported'
   DESC 'List of all the IPP versions that this Printer supports.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15{127}
   )

   A comma-delimited list of all the IPP versions that this Printer
   supports.  For example:

       '1.1,2.0'

   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 and
   registered in the IANA IPP Registry [IANAIPP].

   IANA-registered versions of IPP currently are:

       '1.0' (IPP/1.0 [RFC2566], OBSOLETE)
       '1.1' (IPP/1.1 [RFC2911])
       '2.0' (IPP/2.0 [PWG5100.12])
       '2.1' (IPP/2.1 [PWG5100.12])
       '2.2' (IPP/2.2 [PWG5100.12])



   4.10.  printer-multiple-document-jobs-supported

   ( 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
   )



Fleming, McDonald           Expires 20 November 2012           [Page 20]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012



   4.11.  printer-charset-configured

   ( 1.3.18.0.2.4.1109
   NAME 'printer-charset-configured'
   DESC 'The configured charset in which error and status messages will
         be generated (by default) by this Printer.'
   EQUALITY caseIgnoreMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15{63}
   SINGLE-VALUE
   )

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

       'utf-8' (ISO 10646/Unicode in UTF-8 transform [STD63])
       'iso-8859-1' (Latin1)

   Values of charset tags SHOULD be defined in the IANA Registry of
   Character Sets [IANACHAR] (see also [BCP19]) and the '(preferred MIME
   name)' SHOULD be used as the charset tag in this attribute.

   Note:  For consistency with IPP/1.1 [RFC2911], charset tags in this
   attribute SHOULD be lowercase normalized.



   4.12.  printer-charset-supported

   ( 1.3.18.0.2.4.1131
   NAME 'printer-charset-supported'
   DESC 'One of the charsets supported for the attribute values of synta
         DirectoryString for this directory entry.'
   EQUALITY caseIgnoreMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15{255}
   )

   One of the charsets supported for the attribute values of syntax
   DirectoryString for this directory entry.  For example:

       'iso-8859-1' (ISO Latin1)
       'utf-8' (UTF-8 [STD63])

   Values of charset tags SHOULD be defined in the IANA Registry of
   Character Sets [IANACHAR] (see also [BCP19]) and the '(preferred MIME
   name)' SHOULD be used as the charset tag in this attribute.

   Note:  For consistency with IPP/1.1 [RFC2911], charset tags in this
   attribute SHOULD be lowercase normalized.


Fleming, McDonald           Expires 20 November 2012           [Page 21]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012




   4.13.  printer-generated-natural-language-supported

   ( 1.3.18.0.2.4.1137
   NAME 'printer-generated-natural-language-supported'
   DESC 'One of the natural languages supported for this directory entry
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15{63}
   )

   Values of language tags SHOULD conform to Tags for Identifying
   Languages [BCP47].  For example:

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

   Note:  For consistency with IPP/1.1 [RFC2911], language tags in this
   attribute SHOULD be lowercase normalized.



   4.14.  printer-document-format-supported

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

   Values of document formats SHOULD be MIME media types defined in the
   IANA Registry of MIME Media Types [IANAMIME] (see also [BCP13]).

   For example:

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



   4.15.  printer-color-supported

   ( 1.3.18.0.2.4.1129
   NAME 'printer-color-supported'
   DESC 'Indicates whether this Printer is capable of any type of color
         printing at all, including highlight color.'

Fleming, McDonald           Expires 20 November 2012           [Page 22]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012

   EQUALITY booleanMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.7
   SINGLE-VALUE
   )



   4.16.  printer-compression-supported

   ( 1.3.18.0.2.4.1128
   NAME 'printer-compression-supported'
   DESC 'List of compression algorithms supported by this Printer.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15{255}
   )

   Comma-delimited list of the compression algorithms supported by this
   Printer.  For example:

       'none'
       'deflate,gzip'

   Values defined in IPP/1.1 [RFC2911] and recorded in the IANA IPP
   Registry [IANAIPP] include:

       'none' (no compression is used)
       'deflate' (public domain ZIP described in [RFC1951])
       'gzip' (GNU ZIP described in [RFC1952])
       'compress' (UNIX compression described in [RFC1977])



   4.17.  printer-pages-per-minute

   ( 1.3.18.0.2.4.1127
   NAME 'printer-pages-per-minute'
   DESC 'The nominal number of pages per minute which 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.



Fleming, McDonald           Expires 20 November 2012           [Page 23]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012



   4.18.  printer-pages-per-minute-color

   ( 1.3.18.0.2.4.1126
   NAME 'printer-pages-per-minute-color'
   DESC 'The nominal number of color pages per minute which 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.



   4.19.  printer-finishings-supported

   ( 1.3.18.0.2.4.1125
   NAME 'printer-finishings-supported'
   DESC 'List of the finishing operations supported by this Printer.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15{255}
   )

   Comma-delimited list of the finishing operations supported by this
   Printer.  For example:

       'staple,punch,bind'

   Values defined in IPP/1.1 [RFC2911] and recorded in the IANA IPP
   Registry [IANAIPP] 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'.

   Note:  Implementations MAY support other values.






Fleming, McDonald           Expires 20 November 2012           [Page 24]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012



   4.20.  printer-number-up-supported

   ( 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
   )

   Maximum number of print-stream pages that can be imposed upon a
   single side of an instance of a selected medium by this Printer.  For
   example:

       '1'
       '4'



   4.21.  printer-sides-supported

   ( 1.3.18.0.2.4.1123
   NAME 'printer-sides-supported'
   DESC 'List of the 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{127}
   )

   Comma-delimited list of the impression sides (one or two) and the
   two-sided impression rotations supported by this Printer.  For
   example:

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

   Values defined in IPP/1.1 [RFC2911] and recorded in the IANA IPP
   Registry [IANAIPP] are:

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



   4.22.  printer-media-supported

   ( 1.3.18.0.2.4.1122
   NAME 'printer-media-supported'

Fleming, McDonald           Expires 20 November 2012           [Page 25]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012

   DESC 'One of the names/types/sizes (and optional color suffixes) of t
         media supported by this Printer.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15{255}
   )

   Values SHOULD conform to PWG Media Standardized Names [PWG5101.1].
   Values of standardized media size names, media types, and media
   colors defined in [PWG5101.1] and recorded in the IANA IPP Registry
   [IANAIPP] include:

       'na_letter_8.5x11in'
       'iso_a4_210x297mm'
       'envelope'
       'stationery'
       'white'
       'blue'



   4.23.  printer-media-local-supported

   ( 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{255}
   )

   Values SHOULD conform to PWG Media Standardized Names [PWG5101.1].

   For example:

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



   4.24.  printer-resolution-supported

   ( 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{63}
   )

   Each resolution value MUST be a string containing 3 fields:

Fleming, McDonald           Expires 20 November 2012           [Page 26]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012

   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 '>'.  For example:

       '300>300>dpi>'
       '600>600>dpi>'

   Note:  This attribute is based on 'printer-resolution-supported'
   defined in IPP/1.1 [RFC2911] (which has a binary complex encoding)
   derived from 'prtMarkerAddressabilityFeedDir',
   'prtMarkerAddressabilityXFeedDir', and 'prtMarkerAddressabilityUnit'
   defined in the Printer MIB v2 [RFC3805] (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
   [SLPPRT20].  Whitespace is permitted after (but not before) the
   delimiter '>'.



   4.25.  printer-print-quality-supported

   ( 1.3.18.0.2.4.1120
   NAME 'printer-print-quality-supported'
   DESC '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{127}
   )

   Comma-delimited list of the print qualities supported for printing
   documents on this Printer.  For example:

       'unknown'
       'draft,normal,high'

   Values defined in IPP/1.1 [RFC2911] and recorded in the IANA IPP
   Registry [IANAIPP] 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.



Fleming, McDonald           Expires 20 November 2012           [Page 27]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012



   4.26.  printer-job-priority-supported

   ( 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 [RFC2911] 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'.



   4.27.  printer-copies-supported

   ( 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
   [SLPPRT20].



   4.28.  printer-job-k-octets-supported

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

Fleming, McDonald           Expires 20 November 2012           [Page 28]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012

   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
   [SLPPRT20].



   4.29.  printer-current-operator

   ( 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{127}
   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 [RFC5198]; (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).



   4.30.  printer-service-person

   ( 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{127}
   SINGLE-VALUE
   )

   The value of this attribute SHOULD include information that would

Fleming, McDonald           Expires 20 November 2012           [Page 29]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012

   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 [RFC5198]; (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).



   4.31.  printer-delivery-orientation-supported

   ( 1.3.18.0.2.4.1114
   NAME 'printer-delivery-orientation-supported'
   DESC 'List of the 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{127}
   )

   Comma-delimited list of the delivery orientations of pages as they
   are printed and ejected supported by this Printer.  For example:

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

   Values defined in Printer MIB v2 [RFC3805] 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.

   Note:  The syntax and values for this attribute are aligned with the
   equivalent attribute in the 'service:printer:' v2.0 template
   [SLPPRT20].



   4.32.  printer-stacking-order-supported

   ( 1.3.18.0.2.4.1115
   NAME 'printer-stacking-order-supported'
   DESC 'List of the stacking order 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{127}

Fleming, McDonald           Expires 20 November 2012           [Page 30]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012

   )

   Comma-delimited list of the stacking order of pages as they are
   printed and ejected supported by this Printer.  For example:

       'unknown'
       'first-to-last'

   Values defined in Printer MIB v2 [RFC3805]
   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
   [SLPPRT20].



   4.33.  printer-output-features-supported

   ( 1.3.18.0.2.4.1116
   NAME 'printer-output-features-supported'
   DESC 'List of the output features supported by this Printer.'
   EQUALITY caseIgnoreMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15{127}
   )

   Comma-delimited list of the output features supported by this
   Printer.  For example:

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

   Values defined in Printer MIB v2 [RFC3805] 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

Fleming, McDonald           Expires 20 November 2012           [Page 31]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012

   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
   [SLPPRT20].

   Note:  Implementations MAY support other values.



   4.34.  printer-aliases

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

   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.



   4.35.  printer-device-id

   ( 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{255}
   )

   Values of this attribute SHOULD conform to IEEE-ISTO PWG Command Set
   Format for IEEE 1284 Device ID [PWG5107.2].

   Note:  The corresponding IPP printer-device-id attribute defined in
   [PWG5107.2] has a maximum string length of 1023 octets.
   Implementations SHOULD place required key/value pairs first and
   SHOULD truncate only at key/value pair boundaries for
   interoperability.






Fleming, McDonald           Expires 20 November 2012           [Page 32]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012



   4.36.  printer-device-service-count

   ( 1.3.18.0.2.24.46.1.102
   NAME 'printer-device-service-count'
   DESC 'The number of Printer (Print Service) instances configured on t
   Imaging Device (host system).'
         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 number of Printer (Print Service)
   instances configured on this Imaging Device (host system).  A value
   of '0' is not meaningful (because this attribute must be reported by
   some Printer instance).  A value of '-1' indicates 'unknown'.

   Note:  The syntax and values for this attribute are aligned with the
   equivalent 'device-service-count' attribute defined in
   [PWG5100.JPS3].



   4.37.  printer-device-uuid

   ( 1.3.18.0.2.24.46.1.103
   NAME 'printer-device-uuid'
   DESC 'A URN specifying UUID of the Imaging Device (host system) that
   contains this Printer (Print Service) instance.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch
   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15{45}
   SINGLE-VALUE
   )

   The UUID of the Imaging Device (host system) that contains this
   Printer (Print Service) instance.

   Values of this attribute MUST conform to the UUID URN namespace
   [RFC4122].

   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 'device-uuid' attribute defined in [PWG5100.JPS3].


Fleming, McDonald           Expires 20 November 2012           [Page 33]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012




   4.38.  printer-uuid

   ( 1.3.18.0.2.24.46.1.104
   NAME 'printer-uuid'
   DESC 'A URN specifying 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{45}
   SINGLE-VALUE
   )

   The UUID of this Printer (Print Service) instance on this Imaging
   Device (host system).

   Values of this attribute MUST conform to the UUID URN namespace
   [RFC4122].

   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 [PWG5100.JPS3].



   4.39.  printer-charge-info

   ( 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{255}
   SINGLE-VALUE
   )

   For example:

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

   Note:  For interoperability and consistent text display, values of
   this attribute:  (a) SHOULD be normalized as recommended in Unicode
   Format for Network Interchange [RFC5198]; (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).

Fleming, McDonald           Expires 20 November 2012           [Page 34]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012




   4.40.  printer-charge-info-uri

   ( 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{255}
   SINGLE-VALUE
   )

   Values of URI SHOULD conform to [STD66], although URI schemes can be
   defined which do not conform to [STD66] (see [BCP35]).

   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.



   4.41.  printer-geo-location

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

   Values of this attribute MUST conform to the 'geo' URI scheme
   [RFC5870].

   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.



   4.42.  printer-ipp-features-supported

   ( 1.3.18.0.2.24.46.1.108
   NAME 'printer-ipp-features-supported'
   DESC 'List of the IPP protocol features that this Printer supports.'
   EQUALITY caseIgnoreMatch
   SUBSTR caseIgnoreSubstringsMatch

Fleming, McDonald           Expires 20 November 2012           [Page 35]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012

   SYNTAX  1.3.6.1.4.1.1466.115.121.1.15{255}
   )

   Comma-delimited list of the IPP protocol features that this Printer
   supports.  For example:

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

   Values of this attribute SHOULD specify only IANA-registered keywords
   for the 'ipp-features-supported' attribute defined in [PWG5100.JPS3],
   [PWG5100.EVE], 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 [PWG5100.5])
       'ipp-everywhere' (IPP Everywhere defined in [PWG5100.EVE])
       'job-save' (Job save defined in [PWG5100.11])
       'page-overrides' (Page overrides defined in [PWG5100.6])
       'proof-print' (Proof print defined in [PWG5100.11])
       'subscription-object' (Subscription object defined in [RFC3995])




























Fleming, McDonald           Expires 20 November 2012           [Page 36]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012



5.  Definition of Syntaxes

   No new attribute syntaxes are defined by this document.

   The attribute types defined in Section 4 of this document reference
   syntax OIDs defined in Section 3 of [RFC4517], which are summarized
   below:

   Syntax OID                      Syntax Description
   ------------------------------  ------------------
   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 [STD63])
   1.3.6.1.4.1.1466.115.121.1.27   Integer



6.  Definition of Matching Rules

   No new matching rules are defined by this document.

   The attribute types defined in Section 4 of this document reference
   matching rules defined in Section 4 of [RFC4517], which are
   summarized below:

   Matching Rule OID               Matching Rule Name          Usage
   ------------------------------  ------------------          -----
   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



















Fleming, McDonald           Expires 20 November 2012           [Page 37]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012



7.  IANA Considerations

   This document does not define any new syntaxes or matching rules.

   This document does define the following Object Identifier
   Descriptors, for registration by IANA when this RFC is published:



   7.1.  Registration of Object Classes

   Subject:  Request for LDAP Descriptor Registration

   Descriptor (short name):  see table below

   Object Identifier:  see table below

   Person & email address to contact for further information:  see below

   Usage:  object class

   Specification:  RFCnnnn [ [RFC Editor: to be assigned] ]

   Author/Change Controller:

       Pat Fleming
       IBM
       Highway 52 N
       Rochester, MN 55901
       USA
       Phone: +1 507-253-7583
       EMail: flemingp@us.ibm.com

   Comments:

   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







Fleming, McDonald           Expires 20 November 2012           [Page 38]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012



   7.2.  Registration of Attribute Types

   [[[ ISSUE:  Need to assign new IBM subtree OIDs to new attributes -
   but SHOULD wait until final set of new attributes has settled down
   after review by IEEE-ISTO PWG IPP working group members.  ]]]

   Subject:  Request for LDAP Descriptor Registration

   Descriptor (short name):  see table below

   Object Identifier:  see table below

   Person & email address to contact for further information:  see below

   Usage:  attribute type

   Specification:  RFCnnnn [ [RFC Editor: to be assigned] ]

   Author/Change Controller:

       Pat Fleming
       IBM
       Highway 52 N
       Rochester, MN 55901
       USA
       Phone: +1 507-253-7583
       EMail: flemingp@us.ibm.com

   Comments:

   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

Fleming, McDonald           Expires 20 November 2012           [Page 39]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012

   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
   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
   ------------------------------------            ---------------------
   printer-device-id                               1.3.18.0.2.24.46.1.10
   printer-device-service-count                    1.3.18.0.2.24.46.1.10
   printer-device-uuid                             1.3.18.0.2.24.46.1.10
   printer-uuid                                    1.3.18.0.2.24.46.1.10
   printer-charge-info                             1.3.18.0.2.24.46.1.10
   printer-charge-info-uri                         1.3.18.0.2.24.46.1.10
   printer-geo-location                            1.3.18.0.2.24.46.1.10
   printer-ipp-features-supported                  1.3.18.0.2.24.46.1.10


























Fleming, McDonald           Expires 20 November 2012           [Page 40]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012



8.  Internationalization Considerations

   All text string attributes defined in this document of syntax
   'DirectoryString' [RFC4517] have values that are encoded in UTF-8
   [STD63], as required by [RFC4517].

   A language tag [BCP47] for all of the text string attributes defined
   in this document is contained in the
   printer-natural-language-configured attribute.

   Therefore, all object classes defined in this document conform to the
   IETF Policy on Character Sets and Languages [BCP18].



9.  Security Considerations

   See [RFC4513] for detailed guidance on authentication methods for
   LDAP and the use of TLS/1.2 [RFC5246] to supply connection
   confidentiality and data integrity for LDAP sessions.

   As with any LDAP schema, it is important to protect specific entries
   and attributes with the appropriate access control.  It is
   particularly important that only administrators can modify entries
   defined in this LDAP Printer schema.  Otherwise, an LDAP client might
   be fooled into diverting print service requests from the original
   Printer (or spooler) to a malicious intruder's host system, thus
   exposing the information in printed documents.

   For additional security considerations of deploying Printers in an
   IPP environment, see Section 8 of [RFC2911].



















Fleming, McDonald           Expires 20 November 2012           [Page 41]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012



10.  References



10.1.  Normative References


   [BCP47] A. Phillips, Ed., M. Davis, Ed.  Tags for Identifying
   Languages, BCP 47, RFC 5646, September 2009.

   [IANACHAR] Internet Assigned Numbers Authority (IANA) Registry
   "Character Sets"
   <http://www.iana.org/assignments/character-sets>

   [IANAIPP] Internet Assigned Numbers Authority (IANA) Registry
   "Internet Printing Protocol"
   <http://www.iana.org/assignments/ipp-registrations>

   [IANAMIME] Internet Assigned Numbers Authority (IANA) Registry "MIME
   Media Types"
   <http://www.iana.org/assignments/media-types/index.html>

   [IPPSURI] McDonald, I., and M. Sweet.  IPP over HTTPS Transport
   Binding and 'ipps' URI Scheme, draft-mcdonald-ipps-uri-scheme-xx.txt,
   work-in-progress.

   [PWG5100.5] Carney, D., Hastings, T., and P. Zehler.  Internet
   Printing Protocol (IPP): Document Object, PWG 5100.5, October 2003.
   <ftp://ftp.pwg.org/pub/pwg/candidates/
   cs-ippdocobject10-20031031-5100.5.pdf>

   [PWG5100.6] Zehler, P., Herriot, R., and K. Ocke.  Internet Printing
   Protocol (IPP): Page Overrides, October 2003.
   <ftp://ftp.pwg.org/pub/pwg/candidates/
   cs-ipppageoverride10-20031031-5100.6.pdf>

   [PWG5100.12] Bergman, R., McDonald, I., and M. Sweet.  Internet
   Printing Protocol Version 2.0 Second Edition (IPP/2.0 SE), PWG
   5100.12, February 2011.
   <ftp://ftp.pwg.org/pub/pwg/candidates/
   cs-ipp20-20110214-5100.12.pdf>

   [PWG5100.EVE] Sweet, M., and I. McDonald.  IEEE-ISTO PWG IPP
   Everywhere, <work-in-progress>.
   <http://www.pwg.org/ipp>

   [PWG5100.JPS3] Sweet, M., and I. McDonald.  IEEE-ISTO PWG IPP Job and
   Printer Extensions - Set 3, <work-in-progress>.


Fleming, McDonald           Expires 20 November 2012           [Page 42]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012

   <http://www.pwg.org/ipp>

   [PWG5101.1] Bergman, R., and T. Hastings.  IEEE-ISTO PWG Media
   Standardized Names, PWG 5101.1, February 2002.
   <ftp://ftp.pwg.org/pub/pwg/candidates/
   cs-pwgmsn10-20020226-5101.1.pdf>

   [PWG5107.2] I. McDonald.  IEEE-ISTO PWG Command Set for IEEE 1284
   Device ID, PWG 5107.2, May 2010.
   <ftp://ftp.pwg.org/pub/pwg/candidates/
   cs-pmp1284cmdset10-20100531-5107.2.pdf>

   [RFC2119] S. Bradner.  Key words for use in RFCs to Indicate
   Requirement Levels, RFC 2119 / BCP 14, March 1997.

   [RFC2617] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S.,
   Leach, P., Luotonen, A., and L. Stewart.  HTTP Authentication: Basic
   and Digest Access Authentication, RFC 2617, June 1999.

   [RFC2911] T. Hastings, Ed., Herriot, R., Isaacson, S., and P. Powell.
   Internet Printing Protocol/1.1: Model and Semantics, RFC 2911,
   September 2000.

   [RFC2926] Kempf, J., Moats, R., and P. St. Pierre.  Conversion of
   LDAP Schemas to and from SLP Templates, RFC 2926, September 2000.

   [RFC3510] Herriot, R., and I. McDonald.  Internet Printing Protocol
   1.1:  IPP URL Scheme, RFC 3510, April 2003.

   [RFC3987] Duerst, M., and M. Suignard.  Internationalized Resource
   Identifiers (IRI), RFC 3987, January 2005.

   [RFC3995] Herriot, R., and T. Hastings.  Internet Printing Protocol
   (IPP): Event Notifications and Subscriptions, RFC 3995, March 2005.

   [RFC4122] Leach, P., Mealling, M., and R. Salz.  A Universally Unique
   IDentifier (UUID) URN Namespace, RFC 4122, July 2005.

   [RFC4510] K. Zeilenga, Ed.  Lightweight Directory Access Protocol
   (LDAP): Technical Specification Road Map, RFC 4510, June 2006.

   [RFC4513] R. Harrison, Ed.  Lightweight Directory Access Protocol
   (LDAP): Authentication Methods and Security Mechanisms, RFC 4513,
   June 2006.

   [RFC4517] S. Legg, Ed.  Lightweight Directory Access Protocol (LDAP):
   Syntaxes and Matching Rules, RFC 4517, June 2006.

   [RFC4519] A. Sciberras, Ed.  Lightweight Directory Access Protocol
   (LDAP): Schema for User Applications, RFC 4519, June 2006.


Fleming, McDonald           Expires 20 November 2012           [Page 43]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012


   [RFC4524] K. Zeilenga, Ed.  COSINE LDAP/X.500 Schema, RFC 4524, June
   2006.

   [RFC5198] Klensin, J., and M. Padlipsky.  Unicode Format for Network
   Interchange, RFC 5198, March 2008.

   [RFC5246] Dierks, T., and E. Rescorla.  The Transport Layer Security
   (TLS) Protocol Version 1.2, RFC 5246, August 2008.

   [RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S.,
   Housley, R., and W. Polk.  Internet X.509 Public Key Infrastructure
   Certificate and Certificate Revocation List (CRL) Profile, RFC 5280,
   May 2008.

   [RFC5870] Mayrhofer, A., and C. Spanring.  A Uniform Resource
   Identifier for Geographic Locations ('geo' URI), RFC 5870, June 2010.

   [STD63] F. Yergeau.  UTF-8, a Transformation Format of ISO 10646, STD
   63, RFC 3629, November 2003.

   [STD66] Berners-Lee, T., Fielding, R., and L. Masinter.  Uniform
   Resource Identifier (URI): Generic Syntax, STD 66, RFC 3986, January
   2005.



10.2.  Informative References


   [BCP13] Freed, N., and J. Klensin.  Media Type Specifications and
   Registration Procedures, BCP 13, RFC 4288, December 2005.

   [BCP18] H. Alvestrand.  IETF Policy on Character Sets and Languages,
   BCP 18, RFC 2277, January 1998.

   [BCP19] Freed, N., and J. Postel.  IANA Charset Registration
   Procedures, BCP 19, RFC 2978, October 2000.

   [BCP35] Hansen, T., Hardie, T., and L. Masinter.  Guidelines and
   Registration Procedures for New URI Schemes, BCP 35, RFC 4395,
   February 2006.

   [IANASLP] Internet Assigned Numbers Authority (IANA) Registry
   "Service Location Protocol, Version 2 (SLPv2) Templates"
   <http://www.iana.org/assignments/svrloc-templates.html>

   [RFC1179] L. McLaughlin.  Line Printer Daemon Protocol, RFC 1179,
   August 1990.

   [RFC1951] P. Deutsch.  DEFLATE Compressed Data Format Specification

Fleming, McDonald           Expires 20 November 2012           [Page 44]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012

   Version 1.3, RFC 1951, May 1996.

   [RFC1952] P. Deutsch.  GZIP File Format Specification Version 4.3,
   RFC 1952, May 1996.

   [RFC1977] V. Schryver.  PPP BSD Compression Protocol, RFC 1977,
   August 1996.

   [RFC2079] M. Smith.  Definition of an X.500 Attribute Type and an
   Object Class to Hold Uniform Resource Identifiers (URIs), RFC 2079,
   January 1997.

   [RFC2566] deBry, R., Hastings, T., Herriot, R., Isaacson, S., and
   P. Powell.  Internet Printing Protocol/1.0:  Model and Semantics, RFC
   2566, April 1999.

   [RFC2608] Guttman, E., Perkins, C., Veizades, J., and M. Day.
   Service Location Protocol v2, RFC 2608, June 1999.

   [RFC2609] Guttman, E., Perkins, C., and J. Kempf.  Service Templates
   and Service: Schemes, RFC 2609, June 1999.

   [RFC4559] Jaganathan, K., Zhu, L., and J. Brezak.  SPNEGO-based
   Kerberos and NTLM HTTP Authentication in Microsoft Windows, RFC 4559,
   June 2006.

   [SLPPRT20] St. Pierre, P., Isaacson, S., and I. McDonald.  Definition
   of of the PrinterAbstract Service Type v2.0, May 2000.
   Reviewed and approved by IETF SLP Designated Expert, according to
   Section 5 'IANA Considerations' in [RFC2609].
   Archived in [IANASLP] as "printer.2.0.en".



11.  Appendix A - Acknowledgments

   The editors wish to acknowledge the very significant contributions of
   Ken Jones (Bytemobile) and Harry Lewis (IBM) during the development
   of the original LDAP Printer schema [RFC3712].

   Thanks to Patrik Faltstrom (Cisco), Ryan Moats (Lemur Networks),
   Robert Moore (IBM), Lee Rafalow (IBM), Kimberly Reger (IBM), and Kurt
   Zeilenga (OpenLDAP) for comments on the original LDAP Printer schema
   [RFC3712].

   Thanks to the members of the IEEE-ISTO PWG IPP Working Group, for
   their review comments and help in preparing this document.





Fleming, McDonald           Expires 20 November 2012           [Page 45]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012



12.  Appendix X - Change History

   [ [RFC Editor:  This section to be deleted before RFC publication] ]

   20 May 2012 - draft-mcdonald-ldap-printer-schema-02.txt
   - Third draft - for IEEE-ISTO PWG IPP Everywhere project
   - Cover - changed intended category to Standards Track for
   consistency w/ recent LDAP schema specs and IPP Everywhere
   recommendations.
   - Global - replace 'must' w/ 'MUST', 'should' w/ 'SHOULD', and 'may'
   w/ 'can' or 'MAY' (as appropriate) for Standards Track document.
   - Global - updated publication and expiration dates in copyright,
   header, footer, and boilerplate.
   - Global - replaced [RFC1759] references (obsolete) w/ [RFC 3805],
   per IEEE-ISTO PWG IPP WG review.
   - Global - replaced lowercase 'printer' with titlecase 'Printer' for
   readability and consistency with IPP standards usage.
   - Revised section 1, to correct format of reference to IPP JPS3, per
   IEEE-ISTO PWG IPP WG review.
   - Revised section 3.5, section 4.1, and section 4.2 to add references
   to IPP and IPPS URI scheme specs, per IEEE-ISTO PWG IPP WG review.
   - Revised section 4.2 to correct reference for 'digest' and add
   reference for 'certificate' to [RFC5280], per IEEE-ISTO PWG IPP WG
   review.
   - Revised sections 4.5, 4.6, 4.8, 4.29, 4.30, and 4.36 to add note
   about use of Network Unicode [RFC5198] and prohibition against all C0
   and C1 control characters except HT, CR, and LF, per IEEE-ISTO PWG
   IPP WG review.
   - Revised section 4.9 to enumerate all known IPP versions (noting
   that IPP/1.0 is OBSOLETE) and refer to IANA IPP Registry, per
   IEEE-ISTO PWG IPP WG review.
   - Revised section 4.22 to replace legacy examples w/ examples of
   media size names, media types, and media colors defined in
   [PWG5101.1], per IEEE-ISTO PWG IPP WG review.
   - Revised section 4.24 to delete obscure note about delimiter, per
   IEEE-ISTO PWG IPP WG review.
   - Revised sections 4.25, 4.31, 4.32, and 4.33 to add note about use
   of 'unknown' (out-of-band value) ONLY when the correspond IPP or
   Printer MIB attributes are not present (i.e., artifact of LDAP
   mapping), per IEEE-ISTO PWG IPP WG review.
   - Revised section 4.39 to add exhaustive list of feature keywords
   from [PWG5100.JPS3] and [PWG5100.EVE], per IEEE-ISTO PWG IPP WG
   review.
   - Added section 4.x 'printer-device-service-count' aligned w/
   "device-service-count" in [PWG5100.JPS3], per IEEE-ISTO PWG IPP WG
   review.
   - Added section 4.x 'printer-device-uuid' aligned w/ "device-uuid" in
   [PWG5100.JPS3], per IEEE-ISTO PWG IPP WG review.


Fleming, McDonald           Expires 20 November 2012           [Page 46]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012

   - Revised sections 4.x to add length restrictions to unbounded
   strings (text, URI, and UUID) w/ maximum 255 octets (consistent w/
   RFC 3712), verify attribute lengths (per source IPP attribute), and
   clarify "list of" (comma-delimited) versus "one of" (simple
   multi-valued) for all 'printer-xxx-supported' attributes, per
   IEEE-ISTO PWG IPP WG review.
   - Revised section 7.2 to assign new OIDs for the LDAP Printer Schema
   new attributes, per IEEE-ISTO PWG IPP WG review.
   - Revised section 10.1 to add BCP 14 to [RFC2119] definition, per
   IEEE-ISTO PWG IPP WG review.
   - Revised section 10.1 and section 10.2 to move [RFC2617], [RFC3987],
   [RFC4122], [RFC5198], [RFC5246], [RFC5280], [RFC5870], [STD63] from
   informative to normative references, per IEEE-ISTO PWG IPP WG review.

   3 April 2012 - draft-mcdonald-ldap-printer-schema-01.txt
   - Second draft - for IEEE-ISTO PWG IPP Everywhere project
   - Global - changed [IPPEVE1] to [PWG5100.EVE] and [IPPJPS3] to
   [PWG5100.JPS3], per IEEE-ISTO PWG IPP WG review.
   - Revised section 1.1, to add printer-charge-info-uri and
   printer-uuid to discussion of URI syntax, per IEEE-ISTO PWG IPP WG
   review.
   - Revised section 1.2 and section 1.3, to add printer-device-id to
   discussions of equality and substring matching, per IEEE-ISTO PWG IPP
   WG review.
   - Revised section 3.2, section 4, and section 7.2, to delete
   redundant printer-organization and printer-organizational-unit
   (already covered by 'O' and 'OU'), per IEEE-ISTO PWG IPP WG review.
   - Revised section 3.2, section 4, and section 7.2, to add missing
   printer-charge-info, per IEEE-ISTO PWG IPP WG review.
   - Revised section 3.5, section 4, and section 7.2, to rename
   printer-ipp-extensions-supported to printer-ipp-features-supported,
   per IEEE-ISTO PWG IPP WG review.
   - Revised numerous section 4 subsections, to add references to
   [IANAIPP] or [RFC3805] as appropriate for enumerations and keywords,
   per IEEE-ISTO PWG IPP WG review.
   - Revised section 4.2, to add 'negotiate' as value for 'auth' and
   references to [PWG5100.JPS3], [RFC4559], and [IANAIPP], per IEEE-ISTO
   PWG IPP WG review.
   - Revised section 4.2, to use 'example.com' for all DNS names, per
   IEEE-ISTO PWG IPP WG review.
   - Revised section 4.22 and section 4.23, to add normative reference
   to PWG Media Standardized Names [PWG5101.1], per IEEE-ISTO PWG IPP WG
   review.
   - Revised section 4.24, to divide notes into two separate paragraphs,
   per IEEE-ISTO PWG IPP WG review.
   - Revised section 4.31, section 4.32, and section 4.33, to change
   'Values ...  include' to 'Values ...  are' (i.e., closed set), per
   IEEE-ISTO PWG IPP WG review.
   - Revised section 4.35 printer-device-id, to add warning about
   ordering of required key/value pairs (first) and truncation only at
   key/value pair boundaries for interoperability, per IEEE-ISTO PWG IPP

Fleming, McDonald           Expires 20 November 2012           [Page 47]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012

   WG review.
   - Revised section 4, to add printer-charge-info from [PWG5100.JPS3],
   per IEEE-ISTO PWG IPP WG review.
   - Revised section 4.38 printer-geo-location, to change 'should' to
   'must' for conformance to [RFC5870], per IEEE-ISTO PWG IPP WG review.
   - Revised section 4.39, to change printer-ipp-extensions-supported to
   printer-ipp-features-supported per [PWG5100.JPS3] and add examples,
   per IEEE-ISTO PWG IPP WG review.
   - Revised section 4 subsection printer-uuid, to change 'should' to
   'must' for conformance to [RFC4122], per IEEE-ISTO PWG IPP WG review.
   - Revised section 10 References, to update out-of-date references.

   2 October 2011 - draft-mcdonald-ldap-printer-schema-00.txt
   - Initial version - for IEEE-ISTO PWG IPP Everywhere project
   - Revised document to add current I-D individual submission
   boilerplate.
   - Revised Abstract and section 1 Introduction, to cite [PWG5107.2]
   and [PWG5100.JPS3] new attribute sources.
   - Revised section 3.2 printerAbstract, to add new attributes from
   [PWG5107.2] and [IPPJPS3].
   - Revised section 3.5, to add new attributes from [IPPJPS3].
   - Revised section 4 Definition of Attribute Types, to add new
   attributes from [PWG5107.2] and [IPPJPS3] to table and later specific
   definitions.
   - Revised section 7.2 Registration of Attribute Types, to add new
   attributes from [PWG5107.2] and [IPPJPS3] - new OIDs needed.
   - Revised section 10 References, to update out-of-date references.




13.  Authors' Addresses

   Please send comments to the authors at the addresses listed below.


   Pat Fleming
   IBM
   3065 Highway 52 N
   Rochester, MN 55901
   USA
   Phone: +1 507-253-7583
   EMail: patfleming@us.ibm.com


   Ira McDonald
   High North Inc
   221 Ridge Ave
   Grand Marais, MI 49839
   USA
   Phone: +1 906-494-2434

Fleming, McDonald           Expires 20 November 2012           [Page 48]


Internet-Draft       LDAP Schema for Printer Services        20 May 2012

   Email: blueroofmusic@gmail.com



















































Fleming, McDonald           Expires 20 November 2012           [Page 49]


Html markup produced by rfcmarkup 1.129d, available from https://tools.ietf.org/tools/rfcmarkup/