draft-ietf-ipp-ldap-printer-schema-00.txt   draft-ietf-ipp-ldap-printer-schema-01.txt 
Internet Printing Protocol Working Group Pat Fleming Internet Printing Protocol Working Group Pat Fleming
INTERNET DRAFT IBM INTERNET DRAFT IBM
Expires 8 September 2000 Ken Jones Expires 27 October 2000 Ken Jones
Sun Microsystems Sun Microsystems
Harry Lewis Harry Lewis
IBM IBM
Ira McDonald Ira McDonald
High North High North Inc
8 March 2000 27 April 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-00.txt> <draft-ietf-ipp-ldap-printer-schema-01.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.
skipping to change at page 1, line 49 skipping to change at page 1, line 49
This document defines a common printer schema for use with LDAP This document defines a common printer schema for use with LDAP
directories (a directory service supporting the Lightweight Directory directories (a directory service supporting the Lightweight Directory
Access Protocol (LDAP)). Using this common printer schema enables Access Protocol (LDAP)). Using this common printer schema enables
client applications to use LDAP to search for printers using client applications to use LDAP to search for printers using
application or user specified search criteria. Searches are defined application or user specified search criteria. Searches are defined
based on the entry's type and attributes independent of the LDAP based on the entry's type and attributes independent of the LDAP
directory being used. directory being used.
This document describes the LDAP schema, object classes and This document describes the LDAP schema, object classes and
attributes, for SLP printer templates. This document uses the attributes, for printers and printer services. This document uses
printer attributes defined in Appendix E. of [IPPMOD], the the printer attributes defined in Appendix E. of [IPPMOD], 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 [SLPLDAP] 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 ............................................... 4 1. Introduction ............................................... 4
2. Terminology ................................................ 4 2. Terminology ................................................ 4
3. Definition of Object Classes ............................... 5 3. Definition of Object Classes ............................... 5
3.1. slpServicePrinter ...................................... 6 3.1. slpServicePrinter ...................................... 6
3.2. servicePrinter ......................................... 6 3.2. printerAbstract ........................................ 6
3.3. printerService ......................................... 7 3.3. printerService ......................................... 7
3.4. printerServiceAuxClass ................................. 7 3.4. printerServiceAuxClass ................................. 7
3.5. printerIPP ............................................. 7 3.5. printerIPP ............................................. 8
3.6. printerLPR ............................................. 8 3.6. printerLPR ............................................. 8
3.7. sunPrinter ............................................. 8
4. Definition of Attribute Types .............................. 9 4. Definition of Attribute Types .............................. 9
4.1. printer-uri ............................................ 10 4.1. printer-uri ............................................ 10
4.2. printer-xri-supported .................................. 10 4.2. printer-xri-supported .................................. 10
4.3. printer-name ........................................... 11 4.3. printer-name ........................................... 11
4.4. printer-natural-language-configured .................... 12 4.4. printer-natural-language-configured .................... 12
4.5. printer-location ....................................... 12 4.5. printer-location ....................................... 12
4.6. printer-info ........................................... 12 4.6. printer-info ........................................... 12
4.7. printer-more-info ...................................... 13 4.7. printer-more-info ...................................... 13
4.8. printer-make-and-model ................................. 13 4.8. printer-make-and-model ................................. 13
4.9. printer-ipp-versions-supported ......................... 13 4.9. printer-ipp-versions-supported ......................... 13
skipping to change at page 2, line 39 skipping to change at page 2, line 38
4.13. printer-generated-natural-language-supported .......... 15 4.13. printer-generated-natural-language-supported .......... 15
4.14. printer-document-format-supported ..................... 15 4.14. printer-document-format-supported ..................... 15
4.15. printer-color-supported ............................... 15 4.15. printer-color-supported ............................... 15
4.16. printer-compression-supported ......................... 15 4.16. printer-compression-supported ......................... 15
4.17. printer-pages-per-minute .............................. 16 4.17. printer-pages-per-minute .............................. 16
4.18. printer-pages-per-minute-color ........................ 16 4.18. printer-pages-per-minute-color ........................ 16
4.19. printer-finishings-supported .......................... 16 4.19. printer-finishings-supported .......................... 16
4.20. printer-number-up-supported ........................... 17 4.20. printer-number-up-supported ........................... 17
4.21. printer-sides-supported ............................... 17 4.21. printer-sides-supported ............................... 17
4.22. printer-media-supported ............................... 17 4.22. printer-media-supported ............................... 17
4.23. printer-media-local-supported ......................... 18 4.23. printer-media-local-supported ......................... 17
4.24. printer-resolution-supported .......................... 18 4.24. printer-resolution-supported .......................... 18
4.25. printer-print-quality-supported ....................... 18 4.25. printer-print-quality-supported ....................... 18
4.26. printer-job-priority-supported ........................ 19 4.26. printer-job-priority-supported ........................ 18
4.27. printer-copies-supported .............................. 19 4.27. printer-copies-supported .............................. 19
4.28. printer-job-k-octets-supported ........................ 19 4.28. printer-job-k-octets-supported ........................ 19
4.29. printer-current-operator .............................. 20 4.29. printer-current-operator .............................. 19
4.30. printer-service-person ................................ 20 4.30. printer-service-person ................................ 20
4.31. printer-delivery-orientation-supported ................ 20 4.31. printer-delivery-orientation-supported ................ 20
4.32. printer-stacking-order-supported ...................... 21 4.32. printer-stacking-order-supported ...................... 20
4.33. printer-output-features-supported ..................... 21 4.33. printer-output-features-supported ..................... 20
4.34. sun-printer-bsdaddr ................................... 21 5. Definition of Syntaxes ..................................... 22
4.35. sun-printer-kvp ....................................... 21 6. IANA Considerations ........................................ 22
5. Definition of Syntaxes ..................................... 23 7. Internationalization Considerations ........................ 22
6. IANA Considerations ........................................ 23 8. Security Considerations .................................... 22
7. Internationalization Considerations ........................ 23 9. References ................................................. 22
8. Security Considerations .................................... 23 10. Acknowledgments ........................................... 23
11. Author's Addresses ........................................ 24
9. References ................................................. 23 12. Full Copyright Statement .................................. 25
10. Acknowledgments ........................................... 24
11. Author's Addresses ........................................ 25
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
skipping to change at page 4, line 29 skipping to change at page 4, line 29
The syntax for each of these attributes is described in detail in The syntax for each of these attributes is described in detail in
[IPPMOD] and [SLPPRT]. This document will take these attributes and [IPPMOD] and [SLPPRT]. This document will take these attributes and
map them to LDAP attributes and object classes. 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.
An additional object class, sunPrinter, is defined to illustrate how
Sun Microsystems will support its current installed base. These
systems currently use a "nameservice" to obtain information about
printers. The nameservice may be, at its simplest, a collection of
files in the local filesystem which are opened and searched. Other
nameservices include the Network Information Name Service (NIS) and
the next version of this product (NIS+). Printer information which
is now being kept in these nameservices will be available in LDAP
through the use of this Sun specific object class. This extends
current support for [RFC 2307]. The reader is encouraged to refer to
this RFC for more information regarding LDAP as a nameservice.
Extensions for similar mapping of nameservices to LDAP are
anticipated on various other operating system platforms.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC 2119]. document are to be interpreted as described in [RFC 2119].
3. Definition of Object Classes 3. Definition of Object Classes
We define the following LDAP object classes for use with both generic We define the following LDAP object classes for use with both generic
printer related information and services specific to SLP, IPP, LPR printer related information and services specific to SLP, IPP, and
and Sun Microsystems. LPR.
slpServicePrinter - auxiliary class for SLP registered printers slpServicePrinter - auxiliary class for SLP registered printers
servicePrinter - abstract class for all printer classes printerAbstract - abstract class for all printer classes
printerService - structural class for printers printerService - structural class for printers
printerServiceAuxClass - auxiliary class for printers printerServiceAuxClass - auxiliary class for printers
printerIPP - auxiliary class for IPP printers printerIPP - auxiliary class for IPP printers
printerLPR - auxiliary class for LPR printers printerLPR - auxiliary class for LPR printers
sunPrinter - auxiliary class for Sun Microsystems printers
The following are some examples of how applications MAY choose to use The following are some examples of how applications MAY choose to use
these classes when creating directory entries: these classes when creating directory entries:
1) Use printerService for directory entries containing common printer 1) Use printerService for directory entries containing common printer
information. information.
2) Use both printerService and slpServicePrinter for directory 2) Use both printerService and slpServicePrinter for directory
entries containing common printer information for SLP registered entries containing common printer information for SLP registered
printers. printers.
skipping to change at page 5, line 39 skipping to change at page 5, line 38
3) Use printerService, printerLPR and printerIPP for directory 3) Use printerService, printerLPR and printerIPP for directory
entries containing common printer information for printers that entries containing common printer information for printers that
support both LPR and IPP. support both LPR and IPP.
4) Use printerServiceAuxClass and object classes not defined by this 4) Use printerServiceAuxClass and object classes not defined by this
document for directory entries containing common printer information. document for directory entries containing common printer information.
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 the use of the abstract object class servicePrinter 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 [IPPMOD] have been
prefixed with 'printer-' as recommended in [SLPPRT] and [SLPLDAP]. prefixed with 'printer-' as recommended in [SLPPRT] and [SLPLDAP].
For the object classes defined in this section, schema developers MAY For the object classes defined in this section, schema developers MAY
modify 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. Schema developers MAY derive additional classes from the OIDs and MUST NOT remove OIDs from the list of MAY OIDs. Schema
abstract and structural classes defined in this section. Note, an developers MAY derive additional classes from the abstract and
object class definition SHOULD NOT be changed without having a new structural classes defined in this section. Note, an object class
name and OID assigned to it. definition SHOULD NOT be changed without having a new name and OID
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]. [SLPLDAP].
( 1.3.6.1.4.1.42.2.27.5.2.8 ( <id-oc>.8
NAME 'slpServicePrinter' NAME 'slpServicePrinter'
DESC 'Service Location Protocol (SLP) information.' DESC 'Service Location Protocol (SLP) information.'
SUP slpService SUP slpService
AUXILIARY AUXILIARY
) )
3.2. servicePrinter 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.
( 1.3.6.1.4.1.42.2.27.5.2.9 ( <id-oc>.9
NAME 'servicePrinter' NAME 'printerAbstract'
DESC 'Printer related information.' DESC 'Printer related information.'
ABSTRACT ABSTRACT
SUP top SUP top
MUST ( printer-uri $ printer-xri-supported $ printer-name ) MAY ( printer-name $
MAY ( 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 $
printer-generated-natural-language-supported $ printer-generated-natural-language-supported $
printer-document-format-supported $ printer-color-supported $ printer-document-format-supported $ printer-color-supported $
printer-compression-supported $ printer-pages-per-minute $ printer-compression-supported $ printer-pages-per-minute $
printer-pages-per-minute-color $ printer-pages-per-minute-color $
printer-finishings-supported $ printer-number-up-supported $ printer-finishings-supported $ printer-number-up-supported $
printer-sides-supported $ printer-media-supported $ printer-sides-supported $ printer-media-supported $
skipping to change at page 7, line 13 skipping to change at page 7, line 13
printer-job-k-octets-supported $ printer-current-operator $ printer-job-k-octets-supported $ printer-current-operator $
printer-service-person $ printer-service-person $
printer-delivery-orientation-supported $ printer-delivery-orientation-supported $
printer-stacking-order-supported $ printer-stacking-order-supported $
printer-output-features-supported ) printer-output-features-supported )
) )
3.3. printerService 3.3. printerService
This structural class defines printer information. It is derived This structural class defines printer information. It is derived
from class servicePrinter and thus inherits common printer from class printerAbstract and thus inherits common printer
attributes. This class can be used with or without auxiliary classes attributes. This class can be used with or without auxiliary classes
to define printer information. Auxiliary classes can be used to to define printer information. Auxiliary classes can be used to
extend the common printer information with protocol, service or extend the common printer information with protocol, service or
operating system specific information. Note that when extending operating system specific information. Note that when extending
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 MUST 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). (RDN). printer-uri uniquely identifies each of the printer services
for a given printer. Note that if the printer service changes
domains, printer-uri must be updated with the new domain name.
( 1.3.6.1.4.1.42.2.27.5.2.10 ( <id-oc>.10
NAME 'printerService' NAME 'printerService'
DESC 'Printer information.' DESC 'Printer information.'
SUP servicePrinter SUP printerAbstract
MAY ( printer-uri $ printer-xri-supported )
STRUCTURAL STRUCTURAL
) )
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
class servicePrinter and thus inherits common printer attributes. class printerAbstract and thus inherits common printer attributes.
This class MUST be used with a structural class, such as This class MUST be used with a structural class.
printerService.
( 1.3.6.1.4.1.42.2.27.5.2.11 LDAP applications SHOULD use printer-uri as the naming attribute.
That is, when using printerService, printer-uri SHOULD be used as the
attribute type of the directory entry's relative distinguished name
(RDN). printer-uri uniquely identifies each of the printer services
for a given printer. Note that if the printer service changes
domains, printer-uri must be updated with the new domain name.
( <id-oc>.11
NAME 'printerServiceAuxClass' NAME 'printerServiceAuxClass'
DESC 'Printer information.' DESC 'Printer information.'
SUP servicePrinter SUP printerAbstract
MAY ( printer-uri $ printer-xri-supported )
AUXILIARY AUXILIARY
) )
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.
( 1.3.6.1.4.1.42.2.27.5.2.12 ( <id-oc>.12
NAME 'printerIPP' NAME 'printerIPP'
DESC 'Internet Printing Protocol (IPP) information.' DESC 'Internet Printing Protocol (IPP) information.'
SUP top SUP top
AUXILIARY AUXILIARY
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 extend structural class such as printerService. It is used to identify
structural classes with LPR specific printer information. directory entries that support LPR.
( 1.3.6.1.4.1.42.2.27.5.2.13 ( <id-oc>.13
NAME 'printerLPR' NAME 'printerLPR'
DESC 'LPR information.' DESC 'LPR information.'
SUP top SUP top
AUXILIARY AUXILIARY
) )
3.7. sunPrinter
Current Sun Microsystems print implementations use the Line Printer
Daemon (LPD) Protocol described in [RFC 1179] to communicate between
print clients and servers. In addition to this print clients make
use of nameservices to obtain information about the printer. It is
desirable to extend the current print client nameservice support to
include LDAP while keeping existing functionality. This is done by
defining a Sun specific object class. The "sunPrinter" object
contains two attributes. The sun-printer-bsdaddr attribute
identifies the server host name associated with a print queue and
whether or not Solaris specific extensions to the LPD protocol should
be generated. The second attribute sun-printer-kvp contains a set of
key values pairs. These values may have meaning to the print
subsystem or they may be user defined.
( 1.3.6.1.4.1.42.2.27.5.2.14
NAME 'sunPrinter'
DESC 'Sun printer information'
SUP top
AUXILIARY
MAY ( sun-printer-bsdaddr $ sun-printer-kvp )
)
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 [IPPMOD]. Some
attribute names described in [IPPMOD] have been prefixed with attribute names described in [IPPMOD] have been prefixed with
'printer-' as recommended in [SLPLDAP], to address the flat namespace 'printer-' as recommended in [SLPLDAP], to address the flat namespace
for LDAP identifiers. for LDAP identifiers.
skipping to change at page 10, line 8 skipping to change at page 10, line 8
printer-resolution-supported printer-resolution-supported printer-resolution-supported printer-resolution-supported
printer-print-quality-supported print-quality-supported printer-print-quality-supported print-quality-supported
printer-job-priority-supported job-priority-supported printer-job-priority-supported job-priority-supported
printer-copies-supported copies-supported printer-copies-supported copies-supported
printer-job-k-octets-supported job-k-octets-supported printer-job-k-octets-supported job-k-octets-supported
printer-current-operator printer-current-operator
printer-service-person printer-service-person
printer-delivery-orientation-supported printer-delivery-orientation-supported
printer-stacking-order-supported printer-stacking-order-supported
printer-output-features-supported printer-output-features-supported
sun-printer-bsdaddr
sun-print-kvp
In the following definitions, we use matching rule names instead of In the following definitions, we use matching rule names instead of
OIDs for clarity. Note that if the printer information is not known, OIDs for clarity. Note that if the printer information is not known,
the attribute value is not set (for optional attributes). In the the attribute value is not set (for optional attributes). In the
following definitions, referenced matching rules are defined in following definitions, referenced matching rules are defined in
section 8 of [RFC 2252]. section 8 of [RFC 2252].
The following definitions reference syntax OIDs as defined in [RFC The following definitions reference syntax OIDs as defined in [RFC
2252], which are summarized below: 2252], which are summarized below:
Syntax OID Syntax Description Syntax OID Syntax Description
skipping to change at page 10, line 31 skipping to change at page 10, line 29
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.
( 1.3.6.1.4.1.42.2.27.5.1.30 ( <id-at>.1
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 11, line 24 skipping to change at page 11, line 21
'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<'
( 1.3.6.1.4.1.42.2.27.5.1.31 ( <id-at>.2
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 11, line 46 skipping to change at page 11, line 43
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]).
( 1.3.6.1.4.1.42.2.27.5.1.32 ( <id-at>.3
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
( 1.3.6.1.4.1.42.2.27.5.1.33 ( <id-at>.4
NAME 'printer-generated-natural-language-configured' NAME 'printer-generated-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
( 1.3.6.1.4.1.42.2.27.5.1.34 ( <id-at>.5
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
( 1.3.6.1.4.1.42.2.27.5.1.35 ( <id-at>.6
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
( 1.3.6.1.4.1.42.2.27.5.1.36 ( <id-at>.7
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 caseExactMatch EQUALITY caseIgnoreMatch
ORDERING caseExactOrderingMatch ORDERING caseIgnoreOrderingMatch
SUBSTR caseExactSubstringMatch 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
( 1.3.6.1.4.1.42.2.27.5.1.37 ( <id-at>.8
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
( 1.3.6.1.4.1.42.2.27.5.1.38 ( <id-at>.9
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
( 1.3.6.1.4.1.42.2.27.5.1.39 ( <id-at>.10
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
( 1.3.6.1.4.1.42.2.27.5.1.40 ( <id-at>.11
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
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}
SINGLE-VALUE SINGLE-VALUE
) )
4.12. printer-charset-supported 4.12. printer-charset-supported
( 1.3.6.1.4.1.42.2.27.5.1.41 ( <id-at>.12
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
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.13. printer-generated-natural-language-supported 4.13. printer-generated-natural-language-supported
( 1.3.6.1.4.1.42.2.27.5.1.42 ( <id-at>.13
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
( 1.3.6.1.4.1.42.2.27.5.1.43 ( <id-at>.14
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
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.15. printer-color-supported 4.15. printer-color-supported
( 1.3.6.1.4.1.42.2.27.5.1.44 ( <id-at>.15
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
( 1.3.6.1.4.1.42.2.27.5.1.45 ( <id-at>.16
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
ORDERING caseIgnoreOrderingMatch
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.17. printer-pages-per-minute 4.17. printer-pages-per-minute
( 1.3.6.1.4.1.42.2.27.5.1.46 ( <id-at>.17
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
( 1.3.6.1.4.1.42.2.27.5.1.47 ( <id-at>.18
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
( 1.3.6.1.4.1.42.2.27.5.1.48 ( <id-at>.19
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
ORDERING caseIgnoreOrderingMatch
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
( 1.3.6.1.4.1.42.2.27.5.1.49 ( <id-at>.20
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
( 1.3.6.1.4.1.42.2.27.5.1.50 ( <id-at>.21
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
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.22. printer-media-supported 4.22. printer-media-supported
( 1.3.6.1.4.1.42.2.27.5.1.51 ( <id-at>.22
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
ORDERING caseIgnoreOrderingMatch
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.23. printer-media-local-supported 4.23. printer-media-local-supported
( 1.3.6.1.4.1.42.2.27.5.1.52 ( <id-at>.23
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-generated-natural-language-configured". language in "printer-generated-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
ORDERING caseIgnoreOrderingMatch
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
( 1.3.6.1.4.1.42.2.27.5.1.53 ( <id-at>.24
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
ORDERING caseIgnoreOrderingMatch
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
( 1.3.6.1.4.1.42.2.27.5.1.54 ( <id-at>.25
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
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.26. printer-job-priority-supported 4.26. printer-job-priority-supported
( 1.3.6.1.4.1.42.2.27.5.1.55 ( <id-at>.26
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
( 1.3.6.1.4.1.42.2.27.5.1.56 ( <id-at>.27
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
( 1.3.6.1.4.1.42.2.27.5.1.57 ( <id-at>.28
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
( 1.3.6.1.4.1.42.2.27.5.1.58 ( <id-at>.29
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
( 1.3.6.1.4.1.42.2.27.5.1.59 ( <id-at>.30
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
( 1.3.6.1.4.1.42.2.27.5.1.60 ( <id-at>.31
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
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.32. printer-stacking-order-supported 4.32. printer-stacking-order-supported
( 1.3.6.1.4.1.42.2.27.5.1.61 ( <id-at>.32
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
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.33. printer-output-features-supported 4.33. printer-output-features-supported
( 1.3.6.1.4.1.42.2.27.5.1.62 ( <id-at>.33
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
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.34. sun-printer-bsdaddr
( 1.3.6.1.4.1.42.2.27.5.1.63
NAME 'sun-printer-bsdaddr'
DESC 'Sets the server, print queue destination name and whether the
client generates protocol extensions. "Solaris" specifies a
Solaris print server extension. The value is represented by
the following value: server "," destination ", Solaris".'
EQUALITY caseIgnoreIA5Match
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
SINGLE-VALUE
)
4.35. sun-printer-kvp
( 1.3.6.1.4.1.42.2.27.5.1.64
NAME 'sun-print-kvp'
DESC 'This attribute contains a set of key value pairs which may have
meaning to the print subsystem or may be user defined. Each
value is represented by the following: key "=" value.'
EQUALITY caseIgnoreIA5Match
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
)
5. Definition of Syntaxes 5. Definition of Syntaxes
No new syntaxes are defined by this document. No new syntaxes are defined by this document.
6. IANA Considerations 6. IANA Considerations
There are no IANA registration considerations defined by this There are no IANA registration considerations defined by this
document. document.
7. Internationalization Considerations 7. Internationalization Considerations
skipping to change at page 25, line 5 skipping to change at page 23, line 50
[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.
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
(IBM) for their review comments and help in preparing this document.
11. Author's Addresses 11. Author's Addresses
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: 507-253-7583
EMail: flemingp@us.ibm.com EMail: flemingp@us.ibm.com
skipping to change at page 25, line 32 skipping to change at page 24, line 32
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: 303-924-5337
EMail: harryl@us.ibm.com EMail: harryl@us.ibm.com
Ira McDonald Ira McDonald
High North 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: 906-494-2434 (or 2697)
Email: imcdonald@sharplabs.com Email: imcdonald@sharplabs.com
Email: imcdonal@sdsp.mc.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/