draft-ietf-ipp-ldap-printer-schema-03.txt   draft-ietf-ipp-ldap-printer-schema-04.txt 
Internet Printing Protocol Working Group Pat Fleming Internet Printing Protocol Working Group Pat Fleming
INTERNET DRAFT IBM INTERNET DRAFT IBM
Expires 04 February 2001 Ken Jones Expires 20 June 2001 Ken Jones
Sun Microsystems eStarCom
Harry Lewis [Target Category: Standards Track] Harry Lewis
IBM IBM
Ira McDonald Ira McDonald
High North Inc High North Inc
04 August 2000 20 December 2000
Internet Printing Protocol (IPP): Internet Printing Protocol (IPP):
LDAP Schema for Printer Services LDAP Schema for Printer Services
<draft-ietf-ipp-ldap-printer-schema-03.txt> <draft-ietf-ipp-ldap-printer-schema-04.txt>
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
Status of This Memo Status of This Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. Internet-Drafts are all provisions of Section 10 of RFC 2026. Internet-Drafts are
working documents of the Internet Engineering Task Force (IETF), its working documents of the Internet Engineering Task Force (IETF), its
areas, and its working groups. Note that other groups may also areas, and its working groups. Note that other groups may also
distribute working documents as Internet-Drafts. distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at To view the list of Internet-Draft Shadow Directories, see
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract Abstract
This document is a product of the Internet Printing Protocol Working This document is a product of the Internet Printing Protocol Working
Group, chartered by the IETF. Comments should be sent to the Group, chartered by the IETF. Comments should be sent to the
ipp@pwg.org mailing list and the principal editor ipp@pwg.org mailing list and the principal editor
flemingp@us.ibm.com. flemingp@us.ibm.com.
This document defines a common printer schema for use with LDAP This document defines a common printer schema for use with directory
directories (a directory service supporting the Lightweight Directory services that support the Lightweight Directory Access Protocol
Access Protocol (LDAP)). Using this common printer schema enables (LDAP) [RFC 2251]. Using this common printer schema enables client
client applications to use LDAP to search for printers using applications to use LDAP to search for printers using application or
application or user specified search criteria. Searches are defined user specified search criteria. Searches are defined based on the
based on the entry's type and attributes independent of the LDAP entry's type and attributes independent of the LDAP directory being
directory being used. used.
This document describes the LDAP schema, object classes and This document describes the LDAP schema, object classes and
attributes, for printers and printer services. This document uses attributes, for printers and printer services. This document uses
the printer attributes defined in Appendix E of [IPPMOD], the the printer attributes defined in Appendix E of [RFC 2911], the
'printer:' service template defined in [SLPPRT], and the mapping 'printer:' service template defined in [SLPPRT], and the mapping
between SLP service advertisements and LDAP descriptions of services between SLP service advertisements and LDAP descriptions of services
defined in [SLPLDAP] to define an LDAP printer schema. defined in [RFC 2926] to define an LDAP printer schema.
The goal of this document is to define a consistent schema to be used The goal of this document is to define a consistent schema to be used
by printers and print servers. The LDAP printer schema described in by printers and print servers. The LDAP printer schema described in
this document MAY be used in part or whole. this document MAY be used in part or whole.
Table of Contents Table of Contents
1. Introduction ............................................... 5 1. Introduction ............................................... 5
2. Terminology ................................................ 5 2. Terminology ................................................ 5
3. Definition of Object Classes ............................... 6 3. Definition of Object Classes ............................... 6
3.1. slpServicePrinter ...................................... 7 3.1. slpServicePrinter ...................................... 7
3.2. printerAbstract ........................................ 7 3.2. printerAbstract ........................................ 7
3.3. printerService ......................................... 8 3.3. printerService ......................................... 8
3.4. printerServiceAuxClass ................................. 8 3.4. printerServiceAuxClass ................................. 8
3.5. printerIPP ............................................. 9 3.5. printerIPP ............................................. 9
3.6. printerLPR ............................................. 9 3.6. printerLPR ............................................. 9
4. Definition of Attribute Types .............................. 10 4. Definition of Attribute Types .............................. 10
skipping to change at page 3, line 55 skipping to change at page 4, line 4
4.30. printer-service-person ................................ 20 4.30. printer-service-person ................................ 20
4.31. printer-delivery-orientation-supported ................ 21 4.31. printer-delivery-orientation-supported ................ 21
4.32. printer-stacking-order-supported ...................... 21 4.32. printer-stacking-order-supported ...................... 21
4.33. printer-output-features-supported ..................... 21 4.33. printer-output-features-supported ..................... 21
4.34. printer-aliases ....................................... 22 4.34. printer-aliases ....................................... 22
5. Definition of Syntaxes ..................................... 23 5. Definition of Syntaxes ..................................... 23
6. IANA Considerations ........................................ 23 6. IANA Considerations ........................................ 23
7. Internationalization Considerations ........................ 23 7. Internationalization Considerations ........................ 23
8. Security Considerations .................................... 23 8. Security Considerations .................................... 23
9. References ................................................. 23 9. References ................................................. 23
10. Acknowledgments ........................................... 24
11. Author's Addresses ........................................ 25 10. Acknowledgments ........................................... 24
11. Authors' Addresses ........................................ 25
12. Full Copyright Statement .................................. 26 12. Full Copyright Statement .................................. 26
1. Introduction 1. Introduction
The use of directory services based on the Lightweight Directory The use of directory services based on the Lightweight Directory
Access Protocol [RFC 2251] is becoming increasingly popular for Access Protocol [RFC 2251] is becoming increasingly popular for
distributed services. To ensure interoperability between vendor distributed services. To ensure interoperability between vendor
implementations it is crucial to standardize the schemas which implementations it is crucial to standardize the schemas which
describe these services. describe these services.
Under the auspices of the IETF IPP Working Group the IPP protocol is Under the auspices of the IETF IPP Working Group the IPP protocol is
being developed to bring a standards based printing solution to the being developed to bring a standards based printing solution to the
Internet. Internet.
Section 16 of [IPPMOD] describes a list of attributes which should be Section 16 of [RFC 2911] describes a list of attributes which should
included in a general directory schema describing IPP print services. be included in a general directory schema describing IPP print
The syntax for each of these attributes is described in detail in services. The syntax for each of these attributes is described in
[IPPMOD] and [SLPPRT]. This document will take these attributes and detail in [RFC 2911] and [SLPPRT]. This document will take these
map them to LDAP attributes and object classes. attributes and map them to LDAP attributes and object classes.
This document defines several object classes to provide LDAP This document defines several object classes to provide LDAP
applications with multiple options in defining printer information applications with multiple options in defining printer information
using LDAP schema. Classes are provided for defining directory using LDAP schema. Classes are provided for defining directory
entries with common printer information and for extending existing entries with common printer information and for extending existing
directory entries with SLP, IPP, and LPR specific information. directory entries with SLP, IPP, and LPR specific information.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
skipping to change at page 6, line 44 skipping to change at page 6, line 44
In this example, printerServiceAuxClass is used for extending other In this example, printerServiceAuxClass is used for extending other
structural classes defining printer information with common printer structural classes defining printer information with common printer
information defined in this document. information defined in this document.
Note that specifying the abstract object class printerAbstract is Note that specifying the abstract object class printerAbstract is
OPTIONAL when using printerService or printerServiceAuxClass to OPTIONAL when using printerService or printerServiceAuxClass to
create directory entries per [RFC 2251]. create directory entries per [RFC 2251].
Refer to section 4 for definition of attribute types referenced by Refer to section 4 for definition of attribute types referenced by
these object classes. We use names instead of OIDs in MUST and MAY these object classes. We use names instead of OIDs in MUST and MAY
for clarity. Some attribute names described in [IPPMOD] have been for clarity. Some attribute names described in [RFC 2911] have been
prefixed with 'printer-' as recommended in [SLPPRT] and [SLPLDAP]. prefixed with 'printer-' as recommended in [SLPPRT] and [RFC 2926].
For the object classes defined in this section, schema developers MAY For the object classes defined in this section, schema developers MAY
add to the list of MAY OIDs, but MUST NOT modify the list of MUST add to the list of MAY OIDs, but MUST NOT modify the list of MUST
OIDs and MUST NOT remove OIDs from the list of MAY OIDs. Schema OIDs and MUST NOT remove OIDs from the list of MAY OIDs. Schema
developers MAY derive additional classes from the abstract and developers MAY derive additional classes from the abstract and
structural classes defined in this section. Note, an object class structural classes defined in this section. Note, an object class
definition SHOULD NOT be changed without having a new name and OID definition SHOULD NOT be changed without having a new name and OID
assigned to it. assigned to it.
3.1. slpServicePrinter 3.1. slpServicePrinter
This auxiliary class defines Service Location Protocol (SLP) specific This auxiliary class defines Service Location Protocol (SLP) specific
information. It MUST be used with a structural class such as information. It MUST be used with a structural class such as
printerService. It MAY be used to create new or extend existing printerService. It MAY be used to create new or extend existing
directory entries with SLP 'service:printer' abstract service type directory entries with SLP 'service:printer' abstract service type
information as defined in [SLPPRT]. This object class is derived information as defined in [SLPPRT]. This object class is derived
from 'slpService', the parent class for all SLP services, defined in from 'slpService', the parent class for all SLP services, defined in
[SLPLDAP]. [RFC 2926].
( <id-oc>.1 ( 1.3.18.0.2.6.254
NAME 'slpServicePrinter' NAME 'slpServicePrinter'
DESC 'Service Location Protocol (SLP) information.' DESC 'Service Location Protocol (SLP) information.'
AUXILIARY AUXILIARY
SUP slpService SUP slpService
) )
3.2. printerAbstract 3.2. printerAbstract
This abstract class defines printer information. It is a base class This abstract class defines printer information. It is a base class
for deriving other printer related classes, such as, but not limited for deriving other printer related classes, such as, but not limited
to, classes defined in this document. It defines a common set of to, classes defined in this document. It defines a common set of
printer attributes that are not specific to any one type of service, printer attributes that are not specific to any one type of service,
protocol or operating system. protocol or operating system.
( <id-oc>.2 ( 1.3.18.0.2.6.258
NAME 'printerAbstract' NAME 'printerAbstract'
DESC 'Printer related information.' DESC 'Printer related information.'
ABSTRACT ABSTRACT
SUP top SUP top
MAY ( printer-name $ MAY ( printer-name $
printer-natural-language-configured $ printer-natural-language-configured $
printer-location $ printer-info $ printer-more-info $ printer-location $ printer-info $ printer-more-info $
printer-make-and-model $ printer-make-and-model $
printer-multiple-document-jobs-supported $ printer-multiple-document-jobs-supported $
printer-charset-configured $ printer-charset-supported $ printer-charset-configured $ printer-charset-supported $
skipping to change at page 8, line 28 skipping to change at page 8, line 28
other structural classes with auxiliary classes, printerService MUST other structural classes with auxiliary classes, printerService MUST
NOT be used. NOT be used.
LDAP applications SHOULD use printer-uri as the naming attribute. LDAP applications SHOULD use printer-uri as the naming attribute.
That is, when using printerService, printer-uri SHOULD be used as the That is, when using printerService, printer-uri SHOULD be used as the
attribute type of the directory entry's relative distinguished name attribute type of the directory entry's relative distinguished name
(RDN). printer-uri uniquely identifies each of the printer services (RDN). printer-uri uniquely identifies each of the printer services
for a given printer. Note that if the printer service changes for a given printer. Note that if the printer service changes
domains, printer-uri must be updated with the new domain name. domains, printer-uri must be updated with the new domain name.
( <id-oc>.3 ( 1.3.18.0.2.6.255
NAME 'printerService' NAME 'printerService'
DESC 'Printer information.' DESC 'Printer information.'
STRUCTURAL STRUCTURAL
SUP printerAbstract SUP printerAbstract
MAY ( printer-uri $ printer-xri-supported ) MAY ( printer-uri $ printer-xri-supported )
) )
3.4. printerServiceAuxClass 3.4. printerServiceAuxClass
This auxiliary class defines printer information. It is derived from This auxiliary class defines printer information. It is derived from
skipping to change at page 8, line 50 skipping to change at page 8, line 50
This class MUST be used with a structural class. This class MUST be used with a structural class.
LDAP applications SHOULD use printer-uri as the naming attribute. LDAP applications SHOULD use printer-uri as the naming attribute.
That is, when using printerServiceAuxClass, printer-uri SHOULD be That is, when using printerServiceAuxClass, printer-uri SHOULD be
used as the attribute type of the directory entry's relative used as the attribute type of the directory entry's relative
distinguished name (RDN). printer-uri uniquely identifies each of distinguished name (RDN). printer-uri uniquely identifies each of
the printer services for a given printer. Note that if the printer the printer services for a given printer. Note that if the printer
service changes domains, printer-uri must be updated with the new service changes domains, printer-uri must be updated with the new
domain name. domain name.
( <id-oc>.4 ( 1.3.18.0.2.6.257
NAME 'printerServiceAuxClass' NAME 'printerServiceAuxClass'
DESC 'Printer information.' DESC 'Printer information.'
AUXILIARY AUXILIARY
SUP printerAbstract SUP printerAbstract
MAY ( printer-uri $ printer-xri-supported ) MAY ( printer-uri $ printer-xri-supported )
) )
3.5. printerIPP 3.5. printerIPP
This auxiliary class defines Internet Printing Protocol (IPP) This auxiliary class defines Internet Printing Protocol (IPP)
information. It MUST be used with a structural class such as information. It MUST be used with a structural class such as
printerService. It is used to extend structural classes with IPP printerService. It is used to extend structural classes with IPP
specific printer information. specific printer information.
( <id-oc>.5 ( 1.3.18.0.2.6.256
NAME 'printerIPP' NAME 'printerIPP'
DESC 'Internet Printing Protocol (IPP) information.' DESC 'Internet Printing Protocol (IPP) information.'
AUXILIARY AUXILIARY
SUP top SUP top
MAY ( printer-ipp-versions-supported $ MAY ( printer-ipp-versions-supported $
printer-multiple-document-jobs-supported ) printer-multiple-document-jobs-supported )
) )
3.6. printerLPR 3.6. printerLPR
This auxiliary class defines LPR information. It MUST be used with a This auxiliary class defines LPR information. It MUST be used with a
structural class such as printerService. It is used to identify structural class such as printerService. It is used to identify
directory entries that support LPR. directory entries that support LPR.
( <id-oc>.6 ( 1.3.18.0.2.6.253
NAME 'printerLPR' NAME 'printerLPR'
DESC 'LPR information.' DESC 'LPR information.'
AUXILIARY AUXILIARY
SUP top SUP top
MUST ( printer-name ) MUST ( printer-name )
MAY ( printer-aliases) MAY ( printer-aliases)
) )
4. Definition of Attribute Types 4. Definition of Attribute Types
The following attribute types are referenced by the object classes The following attribute types are referenced by the object classes
defined in section 3. defined in section 3.
The following table is a summary of the attribute names referenced by The following table is a summary of the attribute names referenced by
this document and their corresponding names from [IPPMOD]. Some this document and their corresponding names from [RFC 2911]. Some
attribute names described in [IPPMOD] have been prefixed with attribute names described in [RFC 2911] have been prefixed with
'printer-' as recommended in [SLPLDAP], to address the flat namespace 'printer-' as recommended in [RFC 2926], to address the flat
for LDAP identifiers. namespace for LDAP identifiers.
LDAP & SLP Printer Schema IPP Model [IPPMOD] LDAP & SLP Printer Schema IPP Model [RFC 2911]
------------------------------ ------------------------------------- ------------------------------ -------------------------------------
printer-uri printer-uri
printer-xri-supported printer-xri-supported
[IPP printer-uri-supported] [IPP printer-uri-supported]
[IPP uri-authentication-supported] [IPP uri-authentication-supported]
[IPP uri-security-supported] [IPP uri-security-supported]
printer-name printer-name printer-name printer-name
printer-natural-language-configured printer-natural-language-configured
natural-language-configured natural-language-configured
printer-location printer-location printer-location printer-location
skipping to change at page 11, line 30 skipping to change at page 11, line 30
1.3.6.1.4.1.1466.115.121.1.7 Boolean 1.3.6.1.4.1.1466.115.121.1.7 Boolean
1.3.6.1.4.1.1466.115.121.1.15 Directory String (UTF-8 [RFC 2279]) 1.3.6.1.4.1.1466.115.121.1.15 Directory String (UTF-8 [RFC 2279])
1.3.6.1.4.1.1466.115.121.1.27 Integer 1.3.6.1.4.1.1466.115.121.1.27 Integer
4.1. printer-uri 4.1. printer-uri
Note, that for SLP registered printers, the LDAP printer-uri Note, that for SLP registered printers, the LDAP printer-uri
attribute should set to the value of the registered URL of the attribute should set to the value of the registered URL of the
printer. printer.
( <id-at>.1 ( 1.3.18.0.2.4.1140
NAME 'printer-uri' NAME 'printer-uri'
DESC 'The URI supported by this printer.' DESC 'The URI supported by this printer.'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
ORDERING caseIgnoreOrderingMatch ORDERING caseIgnoreOrderingMatch
SUBSTR caseIgnoreSubstringMatch SUBSTR caseIgnoreSubstringMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
SINGLE-VALUE SINGLE-VALUE
) )
4.2. printer-xri-supported 4.2. printer-xri-supported
skipping to change at page 12, line 22 skipping to change at page 12, line 22
'tls' (IETF TLS/1.0, [RFC 2246]) 'tls' (IETF TLS/1.0, [RFC 2246])
per IPP Model [3] (extensions MAY also be used). A missing 'sec' per IPP Model [3] (extensions MAY also be used). A missing 'sec'
metaparameter SHALL mean 'none'. Each metaparameter of a list member metaparameter SHALL mean 'none'. Each metaparameter of a list member
is delimited by '<'. For example: is delimited by '<'. For example:
'uri=ipp://foo.com< auth=digest< sec=tls<' 'uri=ipp://foo.com< auth=digest< sec=tls<'
'uri=lpr://bar.com< auth=none< sec=none<' 'uri=lpr://bar.com< auth=none< sec=none<'
Registrations MAY consolidate values for metaparameters, as in the Registrations MAY consolidate values for metaparameters, as in the
following example: following example:
'uri=ipp://foo.com< auth=basic,digest< sec=tls,ssl3<' 'uri=ipp://foo.com< auth=basic,digest< sec=tls,ssl3<'
( <id-at>.2 ( 1.3.18.0.2.4.1107
NAME 'printer-xri-supported' NAME 'printer-xri-supported'
DESC 'The unordered list of XRI (extended resource identifiers) DESC 'The unordered list of XRI (extended resource identifiers)
supported by this printer. Each member of the list consists of supported by this printer. Each member of the list consists of
a URI (uniform resource identifier) followed by optional a URI (uniform resource identifier) followed by optional
authentication and security metaparameters.' authentication and security metaparameters.'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
ORDERING caseIgnoreOrderingMatch ORDERING caseIgnoreOrderingMatch
SUBSTR caseIgnoreSubstringMatch SUBSTR caseIgnoreSubstringMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
) )
skipping to change at page 12, line 44 skipping to change at page 12, line 44
4.3. printer-name 4.3. printer-name
The site-specific administrative name of this printer. This value of The site-specific administrative name of this printer. This value of
this attribute SHOULD be in the language specified in this attribute SHOULD be in the language specified in
'printer-natural-language-configured' (although the printer's name 'printer-natural-language-configured' (although the printer's name
may be in any language). This name MAY be the last part of the may be in any language). This name MAY be the last part of the
printer's URI or it MAY be completely unrelated. This name MAY printer's URI or it MAY be completely unrelated. This name MAY
contain characters that are not allowed in a conventional URI (which contain characters that are not allowed in a conventional URI (which
conforms to [RFC 2396]). conforms to [RFC 2396]).
( <id-at>.3 ( 1.3.18.0.2.4.1135
NAME 'printer-name' NAME 'printer-name'
DESC 'The site-specific administrative name of this printer, more DESC 'The site-specific administrative name of this printer, more
end-user friendly than a URI.' end-user friendly than a URI.'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
ORDERING caseIgnoreOrderingMatch ORDERING caseIgnoreOrderingMatch
SUBSTR caseIgnoreSubstringMatch SUBSTR caseIgnoreSubstringMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127}
SINGLE-VALUE SINGLE-VALUE
) )
4.4. printer-natural-language-configured 4.4. printer-natural-language-configured
( <id-at>.4 ( 1.3.18.0.2.4.1119
NAME 'printer-natural-language-configured' NAME 'printer-natural-language-configured'
DESC 'The configured language in which error and status messages will DESC 'The configured language in which error and status messages will
be generated (by default) by this printer. Also, a possible be generated (by default) by this printer. Also, a possible
language for printer string attributes set by operator, system language for printer string attributes set by operator, system
administrator, or manufacturer. Also, the (declared) language administrator, or manufacturer. Also, the (declared) language
of the "printer-name", "printer-location", "printer-info", and of the "printer-name", "printer-location", "printer-info", and
"printer-make-and-model" attributes of this printer. For "printer-make-and-model" attributes of this printer. For
example: "en-us" (US English) or "fr-fr" (French in France) example: "en-us" (US English) or "fr-fr" (French in France)
Legal values of language tags conform to [RFC 1766] "Tags for Legal values of language tags conform to [RFC 1766] "Tags for
the Identification of Languages".' the Identification of Languages".'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
ORDERING caseIgnoreOrderingMatch ORDERING caseIgnoreOrderingMatch
SUBSTR caseIgnoreSubstringMatch SUBSTR caseIgnoreSubstringMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127}
SINGLE-VALUE SINGLE-VALUE
) )
4.5. printer-location 4.5. printer-location
( <id-at>.5 ( 1.3.18.0.2.4.1136
NAME 'printer-location' NAME 'printer-location'
DESC 'Identifies the location of the printer. This could include DESC 'Identifies the location of the printer. This could include
things like: "in Room 123A", "second floor of building XYZ".' things like: "in Room 123A", "second floor of building XYZ".'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
ORDERING caseIgnoreOrderingMatch ORDERING caseIgnoreOrderingMatch
SUBSTR caseIgnoreSubstringMatch SUBSTR caseIgnoreSubstringMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127}
SINGLE-VALUE SINGLE-VALUE
) )
4.6. printer-info 4.6. printer-info
( <id-at>.6 ( 1.3.18.0.2.4.1139
NAME 'printer-info' NAME 'printer-info'
DESC 'Identifies the descriptive information about this printer. DESC 'Identifies the descriptive information about this printer.
This could include things like: "This printer can be used for This could include things like: "This printer can be used for
printing color transparencies for HR presentations", or "Out printing color transparencies for HR presentations", or "Out
of courtesy for others, please print only small (1-5 page) jobs of courtesy for others, please print only small (1-5 page) jobs
at this printer", or even "This printer is going away on July at this printer", or even "This printer is going away on July
1, 1997, please find a new printer".' 1, 1997, please find a new printer".'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
ORDERING caseIgnoreOrderingMatch ORDERING caseIgnoreOrderingMatch
SUBSTR caseIgnoreSubstringMatch SUBSTR caseIgnoreSubstringMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127}
SINGLE-VALUE SINGLE-VALUE
) )
4.7. printer-more-info 4.7. printer-more-info
( <id-at>.7 ( 1.3.18.0.2.4.1134
NAME 'printer-more-info' NAME 'printer-more-info'
DESC 'A URI used to obtain more information about this specific DESC 'A URI used to obtain more information about this specific
printer. For example, this could be an HTTP type URI printer. For example, this could be an HTTP type URI
referencing an HTML page accessible to a Web Browser. The referencing an HTML page accessible to a Web Browser. The
information obtained from this URI is intended for end user information obtained from this URI is intended for end user
consumption.' consumption.'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
ORDERING caseIgnoreOrderingMatch ORDERING caseIgnoreOrderingMatch
SUBSTR caseIgnoreSubstringMatch SUBSTR caseIgnoreSubstringMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
SINGLE-VALUE SINGLE-VALUE
) )
4.8. printer-make-and-model 4.8. printer-make-and-model
( <id-at>.8 ( 1.3.18.0.2.4.1138
NAME 'printer-make-and-model' NAME 'printer-make-and-model'
DESC 'Identifies the make and model of the device. The device DESC 'Identifies the make and model of the device. The device
manufacturer may initially populate this attribute.' manufacturer may initially populate this attribute.'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
ORDERING caseIgnoreOrderingMatch ORDERING caseIgnoreOrderingMatch
SUBSTR caseIgnoreSubstringMatch SUBSTR caseIgnoreSubstringMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127}
SINGLE-VALUE SINGLE-VALUE
) )
4.9. printer-ipp-versions-supported 4.9. printer-ipp-versions-supported
( <id-at>.9 ( 1.3.18.0.2.4.1133
NAME 'printer-ipp-versions-supported' NAME 'printer-ipp-versions-supported'
DESC 'Identifies the IPP protocol version(s) that this printer DESC 'Identifies the IPP protocol version(s) that this printer
supports, including major and minor versions, i.e., the version supports, including major and minor versions, i.e., the version
numbers for which this Printer implementation meets the numbers for which this Printer implementation meets the
conformance requirements.' conformance requirements.'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
ORDERING caseIgnoreOrderingMatch ORDERING caseIgnoreOrderingMatch
SUBSTR caseIgnoreSubstringMatch SUBSTR caseIgnoreSubstringMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127}
) )
4.10. printer-multiple-document-jobs-supported 4.10. printer-multiple-document-jobs-supported
( <id-at>.10 ( 1.3.18.0.2.4.1132
NAME 'printer-multiple-document-jobs-supported' NAME 'printer-multiple-document-jobs-supported'
DESC 'Indicates whether or not the printer supports more than one DESC 'Indicates whether or not the printer supports more than one
document per job, i.e., more than one Send-Document or document per job, i.e., more than one Send-Document or
Send-Data operation with document data.' Send-Data operation with document data.'
EQUALITY booleanMatch EQUALITY booleanMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 SYNTAX 1.3.6.1.4.1.1466.115.121.1.7
SINGLE-VALUE SINGLE-VALUE
) )
4.11. printer-charset-configured 4.11. printer-charset-configured
( <id-at>.11 ( 1.3.18.0.2.4.1109
NAME 'printer-charset-configured' NAME 'printer-charset-configured'
DESC 'The configured charset in which error and status messages will DESC 'The configured charset in which error and status messages will
be generated (by default) by this printer. Also, a possible be generated (by default) by this printer. Also, a possible
charset for printer string attributes set by operator, system charset for printer string attributes set by operator, system
administrator, or manufacturer. For example: "utf-8" (ISO administrator, or manufacturer. For example: "utf-8" (ISO
10646/Unicode) or "iso-8859-1" (Latin1). Legal values are 10646/Unicode) or "iso-8859-1" (Latin1). Legal values are
defined by the IANA Registry of Coded Character Sets and the defined by the IANA Registry of Coded Character Sets and the
"(preferred MIME name)" SHALL be used as the tag. For "(preferred MIME name)" SHALL be used as the tag. For
coherence with IPP Model, charset tags in this attribute SHALL coherence with IPP Model, charset tags in this attribute SHALL
be lowercase normalized. This attribute SHOULD be static (time be lowercase normalized. This attribute SHOULD be static (time
of registration) and SHOULD NOT be dynamically refreshed of registration) and SHOULD NOT be dynamically refreshed
(subsequently).' (subsequently).'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{63} SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{63}
SINGLE-VALUE SINGLE-VALUE
) )
4.12. printer-charset-supported 4.12. printer-charset-supported
( <id-at>.12 ( 1.3.18.0.2.4.1131
NAME 'printer-charset-supported' NAME 'printer-charset-supported'
DESC 'Identifies the set of charsets supported for attribute type DESC 'Identifies the set of charsets supported for attribute type
values of type Directory String for this directory entry. For values of type Directory String for this directory entry. For
example: "utf-8" (ISO 10646/Unicode) or "iso-8859-1" (Latin1). example: "utf-8" (ISO 10646/Unicode) or "iso-8859-1" (Latin1).
Legal values are defined by the IANA Registry of Coded Legal values are defined by the IANA Registry of Coded
Character Sets and the preferred MIME name.' Character Sets and the preferred MIME name.'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{63} SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{63}
) )
4.13. printer-generated-natural-language-supported 4.13. printer-generated-natural-language-supported
( <id-at>.13 ( 1.3.18.0.2.4.1137
NAME 'printer-generated-natural-language-supported' NAME 'printer-generated-natural-language-supported'
DESC 'Identifies the natural language(s) supported for this directory DESC 'Identifies the natural language(s) supported for this directory
entry. For example: "en-us" (US English) or "fr-fr" (French in entry. For example: "en-us" (US English) or "fr-fr" (French in
France). Legal values conform to [RFC 1766], Tags for the France). Legal values conform to [RFC 1766], Tags for the
Identification of Languages.' Identification of Languages.'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
ORDERING caseIgnoreOrderingMatch ORDERING caseIgnoreOrderingMatch
SUBSTR caseIgnoreSubstringMatch SUBSTR caseIgnoreSubstringMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{63} SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{63}
) )
4.14. printer-document-format-supported 4.14. printer-document-format-supported
( <id-at>.14 ( 1.3.18.0.2.4.1130
NAME 'printer-document-format-supported' NAME 'printer-document-format-supported'
DESC 'The possible document formats in which data may be interpreted DESC 'The possible document formats in which data may be interpreted
and printed by this printer. Legal values are MIME types come and printed by this printer. Legal values are MIME types come
from the IANA Registry of Internet Media Types.' from the IANA Registry of Internet Media Types.'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127}
) )
4.15. printer-color-supported 4.15. printer-color-supported
( <id-at>.15 ( 1.3.18.0.2.4.1129
NAME 'printer-color-supported' NAME 'printer-color-supported'
DESC 'Indicates whether this printer is capable of any type of color DESC 'Indicates whether this printer is capable of any type of color
printing at all, including highlight color.' printing at all, including highlight color.'
EQUALITY booleanMatch EQUALITY booleanMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 SYNTAX 1.3.6.1.4.1.1466.115.121.1.7
SINGLE-VALUE SINGLE-VALUE
) )
4.16. printer-compression-supported 4.16. printer-compression-supported
( <id-at>.16 ( 1.3.18.0.2.4.1128
NAME 'printer-compression-supported' NAME 'printer-compression-supported'
DESC 'Compression algorithms supported by this printer. For example: DESC 'Compression algorithms supported by this printer. For example:
"deflate, gzip". Legal values include; "none", "deflate" "deflate, gzip". Legal values include; "none", "deflate"
(public domain ZIP), "gzip" (GNU ZIP), "compress" (UNIX).' (public domain ZIP), "gzip" (GNU ZIP), "compress" (UNIX).'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{255} SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{255}
) )
4.17. printer-pages-per-minute 4.17. printer-pages-per-minute
( <id-at>.17 ( 1.3.18.0.2.4.1127
NAME 'printer-pages-per-minute' NAME 'printer-pages-per-minute'
DESC 'The nominal number of pages per minute which may be output by DESC 'The nominal number of pages per minute which may be output by
this printer (e.g., a simplex or black-and-white printer). this printer (e.g., a simplex or black-and-white printer).
This attribute is informative, NOT a service guarantee. This attribute is informative, NOT a service guarantee.
Typically, it is the value used in marketing literature to Typically, it is the value used in marketing literature to
describe this printer.' describe this printer.'
EQUALITY integerMatch EQUALITY integerMatch
ORDERING integerOrderingMatch ORDERING integerOrderingMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27
SINGLE-VALUE SINGLE-VALUE
) )
4.18. printer-pages-per-minute-color 4.18. printer-pages-per-minute-color
( <id-at>.18 ( 1.3.18.0.2.4.1126
NAME 'printer-pages-per-minute-color' NAME 'printer-pages-per-minute-color'
DESC 'The nominal number of color pages per minute which may be DESC 'The nominal number of color pages per minute which may be
output by this printer (e.g., a simplex or color printer). output by this printer (e.g., a simplex or color printer).
This attribute is informative, NOT a service guarantee. This attribute is informative, NOT a service guarantee.
Typically, it is the value used in marketing literature to Typically, it is the value used in marketing literature to
describe this printer.' describe this printer.'
EQUALITY integerMatch EQUALITY integerMatch
ORDERING integerOrderingMatch ORDERING integerOrderingMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27
SINGLE-VALUE SINGLE-VALUE
) )
4.19. printer-finishings-supported 4.19. printer-finishings-supported
( <id-at>.19 ( 1.3.18.0.2.4.1125
NAME 'printer-finishings-supported' NAME 'printer-finishings-supported'
DESC 'The possible finishing operations supported by this printer. DESC 'The possible finishing operations supported by this printer.
Legal values include; "none", "staple", "punch", "cover", Legal values include; "none", "staple", "punch", "cover",
"bind", "saddle-stitch", "edge-stitch", "staple-top-left", "bind", "saddle-stitch", "edge-stitch", "staple-top-left",
"staple-bottom-left", "staple-top-right", "staple-bottom-left", "staple-top-right",
"staple-bottom-right", "edge-stitch-left", "edge-stitch-top", "staple-bottom-right", "edge-stitch-left", "edge-stitch-top",
"edge-stitch-right", "edge-stitch-bottom", "staple-dual-left", "edge-stitch-right", "edge-stitch-bottom", "staple-dual-left",
"staple-dual-top", "staple-dual-right", "staple-dual-bottom".' "staple-dual-top", "staple-dual-right", "staple-dual-bottom".'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
SUBSTR caseIgnoreSubstringMatch SUBSTR caseIgnoreSubstringMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{255} SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{255}
) )
4.20. printer-number-up-supported 4.20. printer-number-up-supported
( <id-at>.20 ( 1.3.18.0.2.4.1124
NAME 'printer-number-up-supported' NAME 'printer-number-up-supported'
DESC 'The possible numbers of print-stream pages to impose upon a DESC 'The possible numbers of print-stream pages to impose upon a
single side of an instance of a selected medium. Legal values single side of an instance of a selected medium. Legal values
include; 1, 2, and 4. Implementations may support other include; 1, 2, and 4. Implementations may support other
values.' values.'
EQUALITY integerMatch EQUALITY integerMatch
ORDERING integerOrderingMatch ORDERING integerOrderingMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27
) )
4.21. printer-sides-supported 4.21. printer-sides-supported
( <id-at>.21 ( 1.3.18.0.2.4.1123
NAME 'printer-sides-supported' NAME 'printer-sides-supported'
DESC 'The number of impression sides (one or two) and the two-sided DESC 'The number of impression sides (one or two) and the two-sided
impression rotations supported by this printer. Legal values impression rotations supported by this printer. Legal values
include; "one-sided", "two-sided-long-edge", include; "one-sided", "two-sided-long-edge",
"two-sided-short-edge".' "two-sided-short-edge".'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127}
) )
4.22. printer-media-supported 4.22. printer-media-supported
( <id-at>.22 ( 1.3.18.0.2.4.1122
NAME 'printer-media-supported' NAME 'printer-media-supported'
DESC 'The standard names/types/sizes (and optional color suffixes) of DESC 'The standard names/types/sizes (and optional color suffixes) of
the media supported by this printer. For example: "iso-a4", the media supported by this printer. For example: "iso-a4",
"envelope", or "na-letter-white". Legal values conform to ISO "envelope", or "na-letter-white". Legal values conform to ISO
10175, Document Printing Application (DPA), and any IANA 10175, Document Printing Application (DPA), and any IANA
registered extensions.' registered extensions.'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{255} SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{255}
) )
4.23. printer-media-local-supported 4.23. printer-media-local-supported
( <id-at>.23 ( 1.3.18.0.2.4.1117
NAME 'printer-media-local-supported' NAME 'printer-media-local-supported'
DESC 'Site-specific names of media supported by this printer, in the DESC 'Site-specific names of media supported by this printer, in the
language in "printer-natural-language-configured". language in "printer-natural-language-configured".
For example: "purchasing-form" (site-specific name) as opposed For example: "purchasing-form" (site-specific name) as opposed
to (in "printer-media-supported"): "na-letter" (standard to (in "printer-media-supported"): "na-letter" (standard
keyword from ISO 10175).' keyword from ISO 10175).'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
SUBSTR caseIgnoreSubstringMatch SUBSTR caseIgnoreSubstringMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{255} SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{255}
) )
4.24. printer-resolution-supported 4.24. printer-resolution-supported
( <id-at>.24 ( 1.3.18.0.2.4.1121
NAME 'printer-resolution-supported' NAME 'printer-resolution-supported'
DESC 'List of resolutions supported for printing documents by this DESC 'List of resolutions supported for printing documents by this
printer. Each resolution value is a string with 3 fields: printer. Each resolution value is a string with 3 fields:
1) Cross feed direction resolution (positive integer), 2) Feed 1) Cross feed direction resolution (positive integer), 2) Feed
direction resolution (positive integer), 3) Resolution unit. direction resolution (positive integer), 3) Resolution unit.
Legal values are "dpi" (dots per inch) and "dpcm" (dots per Legal values are "dpi" (dots per inch) and "dpcm" (dots per
centimeter). Each resolution field is delimited by ">". For centimeter). Each resolution field is delimited by ">". For
example: "300> 300> dpi>".' example: "300> 300> dpi>".'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
SUBSTR caseIgnoreSubstringMatch SUBSTR caseIgnoreSubstringMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{255} SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{255}
) )
4.25. printer-print-quality-supported 4.25. printer-print-quality-supported
( <id-at>.25 ( 1.3.18.0.2.4.1120
NAME 'printer-print-quality-supported' NAME 'printer-print-quality-supported'
DESC 'List of print qualities supported for printing documents on DESC 'List of print qualities supported for printing documents on
this printer. For example: "draft, normal". Legal values this printer. For example: "draft, normal". Legal values
include; "unknown", "draft", "normal", "high".' include; "unknown", "draft", "normal", "high".'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127}
) )
4.26. printer-job-priority-supported 4.26. printer-job-priority-supported
( <id-at>.26 ( 1.3.18.0.2.4.1110
NAME 'printer-job-priority-supported' NAME 'printer-job-priority-supported'
DESC 'Indicates the number of job priority levels supported. An IPP DESC 'Indicates the number of job priority levels supported. An IPP
conformant printer which supports job priority must always conformant printer which supports job priority must always
support a full range of priorities from "1" to "100" (to ensure support a full range of priorities from "1" to "100" (to ensure
consistent behavior), therefore this attribute describes the consistent behavior), therefore this attribute describes the
"granularity". Legal values of this attribute are from "1" to "granularity". Legal values of this attribute are from "1" to
"100".' "100".'
EQUALITY integerMatch EQUALITY integerMatch
ORDERING integerOrderingMatch ORDERING integerOrderingMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27
SINGLE-VALUE SINGLE-VALUE
) )
4.27. printer-copies-supported 4.27. printer-copies-supported
( <id-at>.27 ( 1.3.18.0.2.4.1118
NAME 'printer-copies-supported' NAME 'printer-copies-supported'
DESC 'The maximum number of copies of a document that may be printed DESC 'The maximum number of copies of a document that may be printed
as a single job. A value of "0" indicates no maximum limit. A as a single job. A value of "0" indicates no maximum limit. A
value of "-1" indicates unknown.' value of "-1" indicates unknown.'
EQUALITY integerMatch EQUALITY integerMatch
ORDERING integerOrderingMatch ORDERING integerOrderingMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27
SINGLE-VALUE SINGLE-VALUE
) )
4.28. printer-job-k-octets-supported 4.28. printer-job-k-octets-supported
( <id-at>.28 ( 1.3.18.0.2.4.1111
NAME 'printer-job-k-octets-supported' NAME 'printer-job-k-octets-supported'
DESC 'The maximum size in kilobytes (1,024 octets actually) incoming DESC 'The maximum size in kilobytes (1,024 octets actually) incoming
print job that this printer will accept. A value of "0" print job that this printer will accept. A value of "0"
indicates no maximum limit. A value of "-1" indicates indicates no maximum limit. A value of "-1" indicates
unknown.' unknown.'
EQUALITY integerMatch EQUALITY integerMatch
ORDERING integerOrderingMatch ORDERING integerOrderingMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27
SINGLE-VALUE SINGLE-VALUE
) )
4.29. printer-current-operator 4.29. printer-current-operator
( <id-at>.29 ( 1.3.18.0.2.4.1112
NAME 'printer-current-operator' NAME 'printer-current-operator'
DESC 'The name of the current human operator responsible for DESC 'The name of the current human operator responsible for
operating this printer. It is suggested that this string operating this printer. It is suggested that this string
include information that would enable other humans to reach the include information that would enable other humans to reach the
operator, such as a phone number.' operator, such as a phone number.'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
ORDERING caseIgnoreOrderingMatch ORDERING caseIgnoreOrderingMatch
SUBSTR caseIgnoreSubstringMatch SUBSTR caseIgnoreSubstringMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127}
SINGLE-VALUE SINGLE-VALUE
) )
4.30. printer-service-person 4.30. printer-service-person
( <id-at>.30 ( 1.3.18.0.2.4.1113
NAME 'printer-service-person' NAME 'printer-service-person'
DESC 'The name of the current human service person responsible for DESC 'The name of the current human service person responsible for
servicing this printer. It is suggested that this string servicing this printer. It is suggested that this string
include information that would enable other humans to reach the include information that would enable other humans to reach the
service person, such as a phone number.' service person, such as a phone number.'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
ORDERING caseIgnoreOrderingMatch ORDERING caseIgnoreOrderingMatch
SUBSTR caseIgnoreSubstringMatch SUBSTR caseIgnoreSubstringMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127}
SINGLE-VALUE SINGLE-VALUE
) )
4.31. printer-delivery-orientation-supported 4.31. printer-delivery-orientation-supported
( <id-at>.31 ( 1.3.18.0.2.4.1114
NAME 'printer-delivery-orientation-supported' NAME 'printer-delivery-orientation-supported'
DESC 'The possible delivery orientations of pages as they are printed DESC 'The possible delivery orientations of pages as they are printed
and ejected from this printer. Legal values include; and ejected from this printer. Legal values include;
"unknown", "face-up", and "face-down".' "unknown", "face-up", and "face-down".'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127}
) )
4.32. printer-stacking-order-supported 4.32. printer-stacking-order-supported
( <id-at>.32 ( 1.3.18.0.2.4.1115
NAME 'printer-stacking-order-supported' NAME 'printer-stacking-order-supported'
DESC 'The possible stacking order of pages as they are printed and DESC 'The possible stacking order of pages as they are printed and
ejected from this printer. Legal values include; "unknown", ejected from this printer. Legal values include; "unknown",
"first-to-last", "last-to-first".' "first-to-last", "last-to-first".'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127}
) )
4.33. printer-output-features-supported 4.33. printer-output-features-supported
( <id-at>.33 ( 1.3.18.0.2.4.1116
NAME 'printer-output-features-supported' NAME 'printer-output-features-supported'
DESC 'The possible output features supported by this printer. Legal DESC 'The possible output features supported by this printer. Legal
values include; "unknown", "bursting", "decollating", values include; "unknown", "bursting", "decollating",
"page-collating", "offset-stacking".' "page-collating", "offset-stacking".'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127}
) )
4.34. printer-aliases 4.34. printer-aliases
( <id-at>.34 ( 1.3.18.0.2.4.1108
NAME 'printer-aliases' NAME 'printer-aliases'
DESC 'Site-specific administrative names of this printer in addition DESC 'Site-specific administrative names of this printer in addition
the printer name specified for printer-name.' the printer name specified for printer-name.'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
ORDERING caseIgnoreOrderingMatch ORDERING caseIgnoreOrderingMatch
SUBSTR caseIgnoreSubstringMatch SUBSTR caseIgnoreSubstringMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127} SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{127}
) )
5. Definition of Syntaxes 5. Definition of Syntaxes
skipping to change at page 23, line 31 skipping to change at page 23, line 31
Therefore, all objects of the printerService class conform to "IETF Therefore, all objects of the printerService class conform to "IETF
Policy on Character Sets and Languages" [RFC 2277]. Policy on Character Sets and Languages" [RFC 2277].
8. Security Considerations 8. Security Considerations
As with any LDAP schema, it is important to protect specific entries As with any LDAP schema, it is important to protect specific entries
and attributes with the appropriate access control. It is and attributes with the appropriate access control. It is
particularly important that only administrators can modify entries particularly important that only administrators can modify entries
defined in this schema. For additional considerations of deploying defined in this schema. For additional considerations of deploying
printers in an IPP environment the reader is referred to section 8 of printers in an IPP environment the reader is referred to section 8 of
[IPPMOD]. [RFC 2911].
By advertising the security methods for each supported printer URL By advertising the security methods for each supported printer URL
the printer may expose information useful to attackers. Suitable the printer may expose information useful to attackers. Suitable
security methods SHOULD be used to authenticate any service security methods SHOULD be used to authenticate any service
advertisements. advertisements.
Obtaining a reference to an object and storing it in the directory Obtaining a reference to an object and storing it in the directory
may make a handle to the object available to a wider audience. This may make a handle to the object available to a wider audience. This
may have security implications. may have security implications.
9. References 9. References
[IPPMOD] deBry, Hastings, Herriot, Isaacson, Powell. Internet
Printing Protocol/1.1: Model and Semantics,
<draft-ietf-ipp-model-v11-07.txt>, May 2000 (adopted by IESG as
Proposed Standard in June 2000).
[SLPPRT] St. Pierre, Isaacson, McDonald. Definition Printer Abstract [SLPPRT] St. Pierre, Isaacson, McDonald. Definition Printer Abstract
Service Type v2.0, <draft-ietf-svrloc-printer-schema-06.txt>, March Service Type v2.0, <draft-ietf-svrloc-printer-schema-06.txt>, March
2000 (appoved and archived in the IANA SLP Template Registry: 2000 (appoved and archived in the IANA SLP Template Registry:
ftp://isi.edu/in-notes/iana/assignments/svrloc-templates/ ftp://isi.edu/in-notes/iana/assignments/svrloc-templates/
in the file 'printer.2.0.en') in the file 'printer.2.0.en')
[SLPLDAP] Kempf, Moats, St. Pierre. Conversion of LDAP Schemas to
and from SLP Templates,
<draft-ietf-svrloc-template-conversion-07.txt>, (work in progress),
June 2000.
[RFC 1179] McLaughlin. Line Printer Daemon Protocol, RFC 1179, [RFC 1179] McLaughlin. Line Printer Daemon Protocol, RFC 1179,
August 1990. August 1990.
[RFC 1766] Alvestrand. Tags for the Identification of Languages, RFC [RFC 1766] Alvestrand. Tags for the Identification of Languages, RFC
1766, March 1995. 1766, March 1995.
[RFC 2119] Bradner. Key words for use in RFCs to Indicate [RFC 2119] Bradner. Key words for use in RFCs to Indicate
Requirement Levels, RFC 2119, March 1997. Requirement Levels, RFC 2119, March 1997.
[RFC 2246] Dierks, Allen. TLS Protocol Version 1.0, RFC 2246, [RFC 2246] Dierks, Allen. TLS Protocol Version 1.0, RFC 2246,
skipping to change at page 24, line 47 skipping to change at page 24, line 39
[RFC 2279] Yergeau. UTF-8, a Transformation Format of ISO 10646, RFC [RFC 2279] Yergeau. UTF-8, a Transformation Format of ISO 10646, RFC
2279, January 1998. 2279, January 1998.
[RFC 2307] Howard. An Approach for Using LDAP as a Network [RFC 2307] Howard. An Approach for Using LDAP as a Network
Information Service, RFC 2307, March 1998. Information Service, RFC 2307, March 1998.
[RFC 2396] Berners-Lee, Fielding, Masinter. URI Generic Syntax, RFC [RFC 2396] Berners-Lee, Fielding, Masinter. URI Generic Syntax, RFC
2396, August 1998. 2396, August 1998.
[RFC 2911] deBry, Hastings, Herriot, Isaacson, Powell. Internet
Printing Protocol/1.1: Model and Semantics, RFC 2911, September 2000.
[RFC 2926] Kempf, Moats, St. Pierre. Conversion of LDAP Schemas to
and from SLP Templates, RFC 2926, September 2000.
10. Acknowledgments 10. Acknowledgments
This document is a submission to the IPP Working group. This document is a submission to the IPP Working group.
Thanks to Kimberly Reger (IBM), Robert Moore (IBM) and Lee Rafalow Thanks to Kimberly Reger (IBM), Robert Moore (IBM) and Lee Rafalow
(IBM) for their review comments and help in preparing this document. (IBM) for their review comments and help in preparing this document.
11. Author's Addresses 11. Authors' Addresses
Principal Editor: Principal Editor:
Pat Fleming Pat Fleming
IBM IBM
Highway 52 N. Highway 52 N.
Rochester, MN 55901 Rochester, MN 55901
USA USA
Phone: 507-253-7583 Phone: +1 507-253-7583
EMail: flemingp@us.ibm.com EMail: flemingp@us.ibm.com
Ken Jones Ken Jones
Sun Microsystems Inc. eStarCom
17 Network Circle 400 S McCaslin Blvd Suite 211
Menlo Park, CA 94025 Louisville, CO 80027
USA USA
Phone: +1 650 786 4164 Phone: +1 720-890-7507
EMail: kenjones@eng.sun.com EMail: kenjones@estarcom.com
Harry Lewis Harry Lewis
IBM IBM
6300 Diagonal Hwy 6300 Diagonal Hwy
Boulder, CO 80301 Boulder, CO 80301
USA USA
Phone: 303-924-5337 Phone: +1 303-924-5337
EMail: harryl@us.ibm.com EMail: harryl@us.ibm.com
Ira McDonald Ira McDonald
High North Inc High North Inc
221 Ridge Ave 221 Ridge Ave
Grand Marais, MI 49839 Grand Marais, MI 49839
USA USA
Phone: 906-494-2434 (or 2697) Phone: +1 906-494-2434
Email: imcdonald@sharplabs.com Email: imcdonald@sharplabs.com
Email: imcdonal@sdsp.mc.xerox.com Email: imcdonald@crt.xerox.com
12. Full Copyright Statement 12. Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/