< draft-ietf-ipp-ldap-printer-schema-04.txt   draft-ietf-ipp-ldap-printer-schema-05.txt >
Internet Printing Protocol Working Group Pat Fleming Internet Printing Protocol Working Group Pat Fleming
INTERNET DRAFT IBM INTERNET DRAFT IBM
Expires 20 June 2001 Ken Jones <draft-ietf-ipp-ldap-printer-schema-05.txt> Ken Jones
eStarCom [Target Category: Informational] eStarCom
[Target Category: Standards Track] Harry Lewis Expires 28 February 2002 Harry Lewis
IBM IBM
Ira McDonald Ira McDonald
High North Inc High North Inc
20 December 2000 28 August 2001
Internet Printing Protocol (IPP): Internet Printing Protocol (IPP):
LDAP Schema for Printer Services LDAP Schema for Printer Services
<draft-ietf-ipp-ldap-printer-schema-04.txt>
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2001). 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."
To view the list of Internet-Draft Shadow Directories, see To view the list of Internet-Draft Shadow Directories, see
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 provides information for the Internet community. It
Group, chartered by the IETF. Comments should be sent to the does not specify an Internet standard of any kind. This document
ipp@pwg.org mailing list and the principal editor defines an LDAP schema, object classes and attributes, for printers
flemingp@us.ibm.com. and printer services, for use with directories that support
Lightweight Directory Access Protocol (LDAPv3) [RFC2251]. This
This document defines a common printer schema for use with directory document is based on the printer attributes listed in Appendix E of
services that support the Lightweight Directory Access Protocol Internet Printing Protocol (IPP/1.1) [RFC2911], the Service Location
(LDAP) [RFC 2251]. Using this common printer schema enables client Protocol (SLPv2) [RFC2608] 'service:printer:' template defined in
applications to use LDAP to search for printers using application or [SLPPRT], and the mapping between SLP service advertisements and LDAP
user specified search criteria. Searches are defined based on the descriptions of services defined in [RFC2926]. Send comments to the
entry's type and attributes independent of the LDAP directory being IPP WG <ipp@pwg.org> and the editor <flemingp@us.ibm.com>.
used.
This document describes the LDAP schema, object classes and
attributes, for printers and printer services. This document uses
the printer attributes defined in Appendix E of [RFC 2911], the
'printer:' service template defined in [SLPPRT], and the mapping
between SLP service advertisements and LDAP descriptions of services
defined in [RFC 2926] to define an LDAP printer schema.
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
this document MAY be used in part or whole.
Table of Contents Table of Contents
1. Introduction ............................................... 5 1. Introduction ............................................... 4
2. Terminology ................................................ 5 2. Terminology ................................................ 4
3. Definition of Object Classes ............................... 6 3. Definition of Object Classes ............................... 5
3.1. slpServicePrinter ...................................... 7 3.1. slpServicePrinter ...................................... 6
3.2. printerAbstract ........................................ 7 3.2. printerAbstract ........................................ 6
3.3. printerService ......................................... 8 3.3. printerService ......................................... 7
3.4. printerServiceAuxClass ................................. 8 3.4. printerServiceAuxClass ................................. 7
3.5. printerIPP ............................................. 9 3.5. printerIPP ............................................. 8
3.6. printerLPR ............................................. 9 3.6. printerLPR ............................................. 8
4. Definition of Attribute Types .............................. 10 4. Definition of Attribute Types .............................. 9
4.1. printer-uri ............................................ 11 4.1. printer-uri ............................................ 10
4.2. printer-xri-supported .................................. 11 4.2. printer-xri-supported .................................. 11
4.3. printer-name ........................................... 12 4.3. printer-name ........................................... 11
4.4. printer-natural-language-configured .................... 13 4.4. printer-natural-language-configured .................... 12
4.5. printer-location ....................................... 13 4.5. printer-location ....................................... 12
4.6. printer-info ........................................... 13 4.6. printer-info ........................................... 13
4.7. printer-more-info ...................................... 14 4.7. printer-more-info ...................................... 13
4.8. printer-make-and-model ................................. 14 4.8. printer-make-and-model ................................. 13
4.9. printer-ipp-versions-supported ......................... 14 4.9. printer-ipp-versions-supported ......................... 14
4.10. printer-multiple-document-jobs-supported .............. 15 4.10. printer-multiple-document-jobs-supported .............. 14
4.11. printer-charset-configured ............................ 15 4.11. printer-charset-configured ............................ 14
4.12. printer-charset-supported ............................. 15 4.12. printer-charset-supported ............................. 15
4.13. printer-generated-natural-language-supported .......... 16 4.13. printer-generated-natural-language-supported .......... 15
4.14. printer-document-format-supported ..................... 16 4.14. printer-document-format-supported ..................... 15
4.15. printer-color-supported ............................... 16 4.15. printer-color-supported ............................... 15
4.16. printer-compression-supported ......................... 16 4.16. printer-compression-supported ......................... 16
4.17. printer-pages-per-minute .............................. 17 4.17. printer-pages-per-minute .............................. 16
4.18. printer-pages-per-minute-color ........................ 17 4.18. printer-pages-per-minute-color ........................ 16
4.19. printer-finishings-supported .......................... 17 4.19. printer-finishings-supported .......................... 17
4.20. printer-number-up-supported ........................... 18 4.20. printer-number-up-supported ........................... 17
4.21. printer-sides-supported ............................... 18 4.21. printer-sides-supported ............................... 17
4.22. printer-media-supported ............................... 18 4.22. printer-media-supported ............................... 17
4.23. printer-media-local-supported ......................... 18 4.23. printer-media-local-supported ......................... 18
4.24. printer-resolution-supported .......................... 19 4.24. printer-resolution-supported .......................... 18
4.25. printer-print-quality-supported ....................... 19 4.25. printer-print-quality-supported ....................... 18
4.26. printer-job-priority-supported ........................ 19 4.26. printer-job-priority-supported ........................ 19
4.27. printer-copies-supported .............................. 20 4.27. printer-copies-supported .............................. 19
4.28. printer-job-k-octets-supported ........................ 20 4.28. printer-job-k-octets-supported ........................ 19
4.29. printer-current-operator .............................. 20 4.29. printer-current-operator .............................. 20
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 ................ 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 ..................... 21
4.34. printer-aliases ....................................... 22 4.34. printer-aliases ....................................... 21
5. Definition of Syntaxes ..................................... 23 5. Definition of Syntaxes ..................................... 22
6. IANA Considerations ........................................ 23 6. Definition of Matching Rules ............................... 22
7. Internationalization Considerations ........................ 23 7. IANA Considerations ........................................ 23
8. Security Considerations .................................... 23 8. Internationalization Considerations ........................ 23
9. References ................................................. 23 9. Security Considerations .................................... 23
10. Acknowledgments ........................................... 24 10. References ................................................ 23
11. Authors' Addresses ........................................ 25 11. Acknowledgments ........................................... 24
12. Full Copyright Statement .................................. 26 12. Authors' Addresses ........................................ 25
13. Full Copyright Statement .................................. 26
1. Introduction 1. Introduction
The use of directory services based on the Lightweight Directory This document provides information for the Internet community. It
Access Protocol [RFC 2251] is becoming increasingly popular for does not specify an Internet standard of any kind. This document
distributed services. To ensure interoperability between vendor defines an LDAP schema, object classes and attributes, for printers
implementations it is crucial to standardize the schemas which and printer services, for use with directories that support
describe these services. Lightweight Directory Access Protocol (LDAPv3) [RFC2251]. This
document is based on the printer attributes listed in Appendix E of
Under the auspices of the IETF IPP Working Group the IPP protocol is Internet Printing Protocol (IPP/1.1) [RFC2911], the Service Location
being developed to bring a standards based printing solution to the Protocol (SLPv2) [RFC2608] 'service:printer:' template defined in
Internet. [SLPPRT], and the mapping between SLP service advertisements and LDAP
descriptions of services defined in [RFC2926]. Send comments to the
IPP WG <ipp@pwg.org> and the editor <flemingp@us.ibm.com>.
Section 16 of [RFC 2911] describes a list of attributes which should Appendix E of IPP/1.1 [RFC2911] specifies a list of printer
be included in a general directory schema describing IPP print attributes which should be included in a general directory schema
services. The syntax for each of these attributes is described in describing IPP print services. The syntax for each of these
detail in [RFC 2911] and [SLPPRT]. This document will take these attributes is described in detail in [RFC2911] and [SLPPRT]. This
attributes and map them to LDAP attributes and object classes. document takes these attributes and maps 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 flexible 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 SLPv2 [RFC2608], IPP/1.1 [RFC2911], and LPR
[RFC1179] specific information.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", This document provides information for the Internet community. It
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this does not specify an Internet standard of any kind.
document are to be interpreted as described in [RFC 2119].
For systems which choose to support this LDAP printer schema, the key
words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in sections 3 and
4 of this document are to be interpreted as described in [RFC2119].
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, and printer related information and services specific to SLPv2 [RFC2608],
LPR. IPP/1.1 [RFC2911], and LPR [RFC1179].
slpServicePrinter - auxiliary class for SLP registered printers slpServicePrinter - auxiliary class for SLP registered printers
printerAbstract - 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
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:
skipping to change at page 6, line 40 skipping to change at page 5, line 40
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 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 [RFC2251].
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 [RFC 2911] have been for clarity. Some attribute names described in [RFC2911] have been
prefixed with 'printer-' as recommended in [SLPPRT] and [RFC 2926]. prefixed with 'printer-' as recommended in [SLPPRT] and [RFC2926].
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 (SLPv2)
information. It MUST be used with a structural class such as [RFC2608] specific information. It MUST be used with a structural
printerService. It MAY be used to create new or extend existing class such as printerService. It MAY be used to create new or extend
directory entries with SLP 'service:printer' abstract service type existing directory entries with SLP 'service:printer' abstract
information as defined in [SLPPRT]. This object class is derived service type information as defined in [SLPPRT]. This object class
from 'slpService', the parent class for all SLP services, defined in is derived from 'slpService', the parent class for all SLP services,
[RFC 2926]. defined in [RFC2926].
( 1.3.18.0.2.6.254 ( 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
skipping to change at page 8, line 26 skipping to change at page 7, line 26
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 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.
( 1.3.18.0.2.6.255 ( 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
class printerAbstract and thus inherits common printer attributes. class printerAbstract and thus inherits common printer attributes.
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.
( 1.3.18.0.2.6.257 ( 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/1.1)
information. It MUST be used with a structural class such as [RFC2911] information. It MUST be used with a structural class such
printerService. It is used to extend structural classes with IPP as printerService. It is used to extend structural classes with IPP
specific printer information. specific printer information.
( 1.3.18.0.2.6.256 ( 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 [RFC1179] information. It MUST be
structural class such as printerService. It is used to identify used with a structural class such as printerService. It is used to
directory entries that support LPR. identify directory entries that support LPR.
( 1.3.18.0.2.6.253 ( 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 attribute types reference syntax OIDs defined in
this document and their corresponding names from [RFC 2911]. Some Section 6 of [RFC2252] (see Section 5 'Definition of Syntaxes'
attribute names described in [RFC 2911] have been prefixed with below).
'printer-' as recommended in [RFC 2926], to address the flat
namespace for LDAP identifiers.
LDAP & SLP Printer Schema IPP Model [RFC 2911] The following attribute types reference matching rule names (instead
of OIDs) for clarity (see Section 6 below). Note that if the printer
information is not known, the attribute value is not set (for
optional attributes). In the following definitions, referenced
matching rules are defined in Section 8 of [RFC2252] and/or Section 6
of [X.520]. (see Section 6 'Definition of Matching Rules' below).
Note: Some implementations of LDAP servers do not support some or
all of the [X.520] matching rules in the EQUALITY, ORDERING, or
SUBSTR clauses of attribute definitions. Administrators may wish to:
1) Omit the EQUALITY clause (or at least the 'booleanMatch', which is
not defined in [RFC2252]);
2) Omit the ORDERING clause (or at least the 'integerOrderingMatch',
which is not defined in [RFC2252]);
3) Omit the SUBSTR clause.
The following table is a summary of the attribute names defined by
this document and their corresponding names from [RFC2911]. Some
attribute names described in [RFC2911] have been prefixed with
'printer-' as recommended in [RFC2926], to address the flat namespace
for LDAP identifiers.
LDAP & SLP Printer Schema IPP Model [RFC2911]
------------------------------ ------------------------------------- ------------------------------ -------------------------------------
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 10 skipping to change at page 10, line 33
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
printer-aliases printer-aliases
In the following definitions, we use matching rule names instead of
OIDs for clarity. Note that if the printer information is not known,
the attribute value is not set (for optional attributes). In the
following definitions, referenced matching rules are defined in
section 8 of [RFC 2252].
The following definitions reference syntax OIDs as defined in [RFC
2252], which are summarized below:
Syntax OID Syntax Description
----------------------------- ------------------
1.3.6.1.4.1.1466.115.121.1.7 Boolean
1.3.6.1.4.1.1466.115.121.1.15 Directory String (UTF-8 [RFC 2279])
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 MUST set to the value of the registered URL of the printer.
printer.
( 1.3.18.0.2.4.1140 ( 1.3.18.0.2.4.1140
NAME 'printer-uri' NAME 'printer-uri'
DESC 'The URI supported by this printer.' DESC 'A URI supported by this printer.
This URI SHOULD be used as a relative distinguished name (RDN).
If printer-xri-supported is implemented, then this URI value
MUST be listed in a member value of printer-xri-supported.'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
ORDERING caseIgnoreOrderingMatch ORDERING caseIgnoreOrderingMatch
SUBSTR caseIgnoreSubstringMatch SUBSTR caseIgnoreSubstringsMatch
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
A list of XRI (extended resource identifiers) supported by this A list of XRI (extended resource identifiers) supported by this
printer. Each value of this list consists of a URI (uniform resource printer. Each value of this list consists of a URI (uniform resource
identifier) followed by optional authentication and security identifier) followed by optional authentication and security
metaparameters. The keywords for URI and their metaparameters are: metaparameters. The keywords for URI and their metaparameters are:
'uri' == IPP 'printer-uri-supported' value 'uri' == IPP 'printer-uri-supported' value
'auth' == IPP 'uri-authentication-supported' value 'auth' == IPP 'uri-authentication-supported' value
'sec' == IPP 'uri-security-supported' value 'sec' == IPP 'uri-security-supported' value
Legal values of the 'auth' metaparameter include Legal values of the 'auth' metaparameter include
'none' (no authentication for this URI) 'none' (no authentication for this URI)
'requesting-user-name' (from operation request) 'requesting-user-name' (from operation request)
'basic' (HTTP/1.1 Basic [RFC 2617]) 'basic' (HTTP/1.1 Basic [RFC2617])
'digest' (HTTP/1.1 Basic, [RFC 2617]) 'digest' (HTTP/1.1 Basic, [RFC2617])
'certificate' (from certificate) 'certificate' (from certificate)
per IPP Model [3] (extensions MAY also be used). A missing 'auth' per IPP Model [3] (extensions MAY also be used). A missing 'auth'
metaparameter SHALL mean 'none'. Legal values of the 'sec' metaparameter SHALL mean 'none'. Legal values of the 'sec'
metaparameter include metaparameter include
'none' (no security for this URI) 'none' (no security for this URI)
'ssl3' (Netscape SSL3) 'ssl3' (Netscape SSL3)
'tls' (IETF TLS/1.0, [RFC 2246]) 'tls' (IETF TLS/1.0, [RFC2246])
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.18.0.2.4.1107 ( 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 caseIgnoreSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
) )
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 [RFC2396]).
( 1.3.18.0.2.4.1135 ( 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 caseIgnoreSubstringsMatch
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.18.0.2.4.1119 ( 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 [RFC3066] "Tags for
the Identification of Languages".' the Identification of Languages".'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
ORDERING caseIgnoreOrderingMatch ORDERING caseIgnoreOrderingMatch
SUBSTR caseIgnoreSubstringMatch SUBSTR caseIgnoreSubstringsMatch
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.18.0.2.4.1136 ( 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 caseIgnoreSubstringsMatch
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.18.0.2.4.1139 ( 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 caseIgnoreSubstringsMatch
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.18.0.2.4.1134 ( 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 caseIgnoreSubstringsMatch
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.18.0.2.4.1138 ( 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 caseIgnoreSubstringsMatch
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.18.0.2.4.1133 ( 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 caseIgnoreSubstringsMatch
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.18.0.2.4.1132 ( 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.'
skipping to change at page 16, line 11 skipping to change at page 15, line 24
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
( 1.3.18.0.2.4.1137 ( 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 [RFC3066], Tags for the
Identification of Languages.' Identification of Languages.'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
ORDERING caseIgnoreOrderingMatch ORDERING caseIgnoreOrderingMatch
SUBSTR caseIgnoreSubstringMatch SUBSTR caseIgnoreSubstringsMatch
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.18.0.2.4.1130 ( 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.'
skipping to change at page 17, line 47 skipping to change at page 17, line 17
( 1.3.18.0.2.4.1125 ( 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 caseIgnoreSubstringsMatch
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.18.0.2.4.1124 ( 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
skipping to change at page 19, line 6 skipping to change at page 18, line 22
4.23. printer-media-local-supported 4.23. printer-media-local-supported
( 1.3.18.0.2.4.1117 ( 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 caseIgnoreSubstringsMatch
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.18.0.2.4.1121 ( 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 caseIgnoreSubstringsMatch
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.18.0.2.4.1120 ( 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".'
skipping to change at page 20, line 42 skipping to change at page 20, line 15
4.29. printer-current-operator 4.29. printer-current-operator
( 1.3.18.0.2.4.1112 ( 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 caseIgnoreSubstringsMatch
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.18.0.2.4.1113 ( 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 caseIgnoreSubstringsMatch
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.18.0.2.4.1114 ( 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;
skipping to change at page 22, line 13 skipping to change at page 21, line 29
) )
4.34. printer-aliases 4.34. printer-aliases
( 1.3.18.0.2.4.1108 ( 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 caseIgnoreSubstringsMatch
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
No new syntaxes are defined by this document. No new attribute syntaxes are defined by this document.
6. IANA Considerations The attribute types defined in Section 4 above reference syntax OIDs
defined in Section 6 of [RFC2252], which are summarized below:
Syntax OID Syntax Description
------------------------------ ------------------
1.3.6.1.4.1.1466.115.121.1.7 Boolean
1.3.6.1.4.1.1466.115.121.1.15 Directory String (UTF-8 [RFC2279])
1.3.6.1.4.1.1466.115.121.1.27 Integer
6. Definition of Matching Rules
No new matching rules are defined by this document.
The attribute types defined in Section 4 above reference matching
rules defined in Section 8 of [RFC2252] and/or Section 6 of [X.520],
which are summarized below:
Matching Rule OID Matching Rule Name Usage
------------------------------ ------------------ -----
2.5.13.13* booleanMatch EQUALITY
2.5.13.2 caseIgnoreMatch EQUALITY
2.5.13.14 integerMatch EQUALITY
2.5.13.3 caseIgnoreOrderingMatch ORDERING
2.5.13.15* integerOrderingMatch ORDERING
2.5.13.4 caseIgnoreSubstringsMatch SUBSTR
* - Defined in ITU-T X.520:1996 [X.520] but not listed in [RFC2252]
Note: Some implementations of LDAP servers do not support some or
all of the [X.520] matching rules in the EQUALITY, ORDERING, or
SUBSTR clauses of attribute definitions. Administrators may wish to:
1) Omit the EQUALITY clause (or at least the 'booleanMatch', which is
not defined in [RFC2252]);
2) Omit the ORDERING clause (or at least the 'integerOrderingMatch',
which is not defined in [RFC2252]);
3) Omit the SUBSTR clause.
7. 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 8. Internationalization Considerations
All text string attribute values in objects of the printerService All text string attribute values in objects of the printerService
class MUST be encoded in UTF-8 [RFC 2279] characters, as required by class MUST be encoded in UTF-8 [RFC2279] characters, as required by
the syntax 'Directory String' [RFC 2252]. Also, a language tag for the syntax 'Directory String' [RFC2252]. Also, a language tag
all of the text string attributes in objects of the printerService [RFC3066] for all of the text string attributes in objects of the
class SHOULD be supplied in 'printer-natural-language-configured'. printerService class SHOULD be supplied in
Therefore, all objects of the printerService class conform to "IETF 'printer-natural-language-configured'. Therefore, all objects of the
Policy on Character Sets and Languages" [RFC 2277]. printerService class conform to the "IETF Policy on Character Sets
and Languages" [RFC2277].
8. Security Considerations 9. 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 LDAP printer schema. For additional considerations
printers in an IPP environment the reader is referred to section 8 of of deploying printers in an IPP environment, the reader is referred
[RFC 2911]. to Section 8 of [RFC2911].
By advertising the security methods for each supported printer URL
the printer may expose information useful to attackers. Suitable
security methods SHOULD be used to authenticate any service
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 10. References
[SLPPRT] St. Pierre, Isaacson, McDonald. Definition Printer Abstract
Service Type v2.0, <draft-ietf-svrloc-printer-schema-06.txt>, March
2000 (appoved and archived in the IANA SLP Template Registry:
[SLPPRT] St. Pierre, Isaacson, McDonald. Definition of the Printer
Abstract Service Type v2.0, <durable URL below>, May 2000.
Reviewed and approved by IETF SLP Designated Expert, according to
Section 5 'IANA Considerations' in [RFC2609].
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'
[RFC 1179] McLaughlin. Line Printer Daemon Protocol, RFC 1179,
August 1990.
[RFC 1766] Alvestrand. Tags for the Identification of Languages, RFC [RFC1179] McLaughlin. Line Printer Daemon Protocol, RFC 1179, August
1766, March 1995. 1990.
[RFC 2119] Bradner. Key words for use in RFCs to Indicate [RFC2119] Bradner. Key words for use in RFCs to Indicate Requirement
Requirement Levels, RFC 2119, March 1997. Levels, RFC 2119, March 1997.
[RFC 2246] Dierks, Allen. TLS Protocol Version 1.0, RFC 2246, [RFC2246] Dierks, Allen. TLS Protocol Version 1.0, RFC 2246, January
January 1999. 1999.
[RFC 2251] Wahl, Howes, Kille. Lightweight Directory Access Protocol [RFC2251] Wahl, Howes, Kille. Lightweight Directory Access Protocol
(v3), RFC 2251, December 1997. (v3), RFC 2251, December 1997.
[RFC 2252] Wahl, Coulbeck, Howes, Kille. Lightweight Directory [RFC2252] Wahl, Coulbeck, Howes, Kille. Lightweight Directory Access
Access Protocol (v3): Attribute Syntax Definitions, RFC 2252, Protocol (v3): Attribute Syntax Definitions, RFC 2252, December 1997.
December 1997.
[RFC 2277] Alvestrand. IETF Policy on Character Sets and Languages, [RFC2277] Alvestrand. IETF Policy on Character Sets and Languages,
RFC 2277, January 1998. RFC 2277, January 1998.
[RFC 2279] Yergeau. UTF-8, a Transformation Format of ISO 10646, RFC [RFC2279] 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 [RFC2396] Berners-Lee, Fielding, Masinter. URI Generic Syntax, RFC
Information Service, RFC 2307, March 1998.
[RFC 2396] Berners-Lee, Fielding, Masinter. URI Generic Syntax, RFC
2396, August 1998. 2396, August 1998.
[RFC 2911] deBry, Hastings, Herriot, Isaacson, Powell. Internet [RFC2608] Guttman, Perkins, Veizades, Day. Service Location Protocol
v2, RFC 2608, June 1999.
[RFC2609] Guttman, Perkins, Kempf. Service Templates and Service:
Schemes, RFC 2609, June 1999.
[RFC2617] Franks, Hallam-Baker, Hostetler, Lawrence, Leach, Luotonen,
Stewart. HTTP Authentication: Basic and Digest Access
Authentication, RFC 2617, June 1999.
[RFC2911] deBry, Hastings, Herriot, Isaacson, Powell. Internet
Printing Protocol/1.1: Model and Semantics, RFC 2911, September 2000. Printing Protocol/1.1: Model and Semantics, RFC 2911, September 2000.
[RFC 2926] Kempf, Moats, St. Pierre. Conversion of LDAP Schemas to [RFC2926] Kempf, Moats, St. Pierre. Conversion of LDAP Schemas to
and from SLP Templates, RFC 2926, September 2000. and from SLP Templates, RFC 2926, September 2000.
10. Acknowledgments [RFC3066] Alvestrand. Tags for the Identification of Languages, RFC
3066, January 2001.
This document is a submission to the IPP Working group. [X.520] The Directory: Selected Attribute Types. ITU-T
Recommendation X.520 and ISO/IEC 9594-6, 1993.
Thanks to Kimberly Reger (IBM), Robert Moore (IBM) and Lee Rafalow 11. Acknowledgments
(IBM) for their review comments and help in preparing this document.
11. Authors' Addresses Thanks to the members of the IPP Working group, Kimberly Reger (IBM),
Robert Moore (IBM) and Lee Rafalow (IBM), and Kurt Zeilenga
(OpenLDAP) for their review comments and help in preparing this
document.
12. 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: +1 507-253-7583 Phone: +1 507-253-7583
EMail: flemingp@us.ibm.com EMail: flemingp@us.ibm.com
skipping to change at page 25, line 38 skipping to change at page 25, line 38
USA USA
Phone: +1 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: +1 906-494-2434 Phone: +1 906-494-2434
Email: imcdonald@sharplabs.com
Email: imcdonald@crt.xerox.com Email: imcdonald@crt.xerox.com
12. Full Copyright Statement 13. Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2001). 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
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
 End of changes. 85 change blocks. 
213 lines changed or deleted 265 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/