Hi folks, Thursday (24 February 2000)
I spoke with Ken Jones (see below) at length on the phone
this afternoon about this LDAP Schema named 'ippPrinter'.
Ken followed the IPP/1.1 Generic Directory Schema exactly,
except that all IPP Recommended (SLP Required) attributes
were reduced to LDAP May (optional) - except 'printer-name'
which is LDAP Must (required) - see page 3, section 2.1
of Ken's I-D for the rationale.
Also, the IPP attribute names have NOT been prefixed
with 'printer-' for safety in the flat LDAP namespace -
recommended in 'Conversion of LDAP Schemas to/from SLP
Templates', <draft-ietf-svrloc-template-conversion-05.txt>.
Also, the Printer MIB derived attributes in the SLP template
have not been included (because Ken wrote straight from the
IPP/1.1 Model and not by translation from the SLP template).
Ken did adopt the use of '>' for ordered lists from the SLP
template. So our representations are very close.
Please copy Ken Jones (see headers on this note) on any
comments.
PLEASE make comments while you can, folks.
Cheers,
- Ira McDonald (consulting architect at Sharp Labs America)
High North Inc
-----Original Message-----
From: Kenneth Jones [mailto:Ken.Jones at eng.sun.com]
Sent: Thursday, February 24, 2000 2:45 PM
To: ipp at pwg.org
Subject: IPP> Informational RFC to be:
draft-sun-ldap-print-schema-00.txt
Ira McDonald asked that I forward this internet draft
to ipp for review.
Ken Jones
Sun Microsystems
------------- Begin Forwarded Message -------------
To: iesg at ietf.org
Subject: Informational RFC to be: draft-sun-ldap-print-schema-00.txt
Cc: rfc-ed. at ISI.EDU, Ken.Jones at eng.sun.com
IESG,
This RFC-to-be was submitted to the RFC Editor to be published as
Informational: draft-sun-ldap-print-schema-00.txt
Four week timeout is initiated (21 March 2000).
An LDAP Directory Schema Solution For Printers
This document describes an LDAP directory schema for print services.
The intention is to build upon the work done by the Internet Printing
Protocol (IPP) group and illustrate how to extend that solution with an
additional class to support existing Sun Microsystems printing
implementations.
Sincerely,
Sandy Ginoza - USC/ISI
Request for Comments Documents
Voice: (310) 822-1511 x89369
Fax: (310) 823-6714
EMAIL: RFC-ED at ISI.EDU
------------- End Forwarded Message -------------