PS> FW: Help with review of draft-fleming-ldap-printer-schema-02.txt

PS> FW: Help with review of draft-fleming-ldap-printer-schema-02.txt

McDonald, Ira imcdonald at sharplabs.com
Mon Aug 4 15:27:25 EDT 2003


Hi folks,

I personally think we should award SOMETHING to Ted Hardie for
being the most responsive IETF Area Director I've ever heard of.
See below.

Cheers,
- Ira McDonald, co-editor of LDAP Printer schema
  High North Inc


-----Original Message-----
From: hardie at qualcomm.com [mailto:hardie at qualcomm.com]
Sent: Monday, August 04, 2003 2:46 PM
To: McDonald, Ira; 'Pat Fleming'; 'Harry Lewis'; 'Kurt at OpenLDAP.org'
Subject: RE: Help with review of
draft-fleming-ldap-printer-schema-02.txt


I got the note, and I've updated the tracker and sent a request to 
the Secretariat
for a last call.  That should be a four week call (September 1 or 2). 
Thanks again
for your help on moving this forward,
				regards,
					Ted Hardie

At 11:24 AM -0700 8/4/03, McDonald, Ira wrote:
>Hi Ted,
>
>Wow!  Thanks for your instant reply.
>
>I just sent a note to the RFC Editor and copied you and Kurt
>ASAP, so soon you will be able to schedule an IETF last call.
>
>Cheers,
>- Ira McDonald
>   High North Inc
>
>
>-----Original Message-----
>From: hardie at qualcomm.com [mailto:hardie at qualcomm.com]
>Sent: Monday, August 04, 2003 1:59 PM
>To: McDonald, Ira; 'Pat Fleming'; 'Harry Lewis'; 'Kurt at OpenLDAP.org'
>Subject: Re: Help with review of
>draft-fleming-ldap-printer-schema-02.txt
>
>
>Hi,
>	I would also like help moving this forward.  As a first
>step, would you be willing for us to last call the document?  This
>is not required for an informational document, but I believe
>that in this case the combination of technologies (and the time
>it has been on the plate) would make that prudent.  If you
>are, please let the RFC Editor know that this will be moving
>from "Independent via RFC Editor" to "Independent, sponsored
>by AD"; I'll then mark the change in the tracker and issue a
>four week last call.  Assuming no issues come up, we should
>be able to get it on the ballot after the last call.
>		thanks,
>			Ted Hardie
>
>
>At 10:44 AM -0700 8/4/03, McDonald, Ira wrote:
>>Hi Ted and Kurt,
>>
>>Pat Fleming and I revised this LDAP Printer schema document
>>in response to comments from Kurt and others in June 2002.
>>FYI - below is the release notice Pat Fleming and I sent when
>>we posted draft-02 last year.
>>
>>Patrik Faltstrom has never replied to any of our subsequent
>>notes.
>>
>>I found out in the IETF I-D Tracker that Ted is now our shepherd
>>and the docment remains in 'Expert Review' (since February 2002).
>>
>>Printer industry folks active in the IETF and the IEEE/ISTO
>>PWG (Printer Working Group) would very much like to get this
>>Informational RFC published.  Two IEEE/ISTO PWGs protocols
>>now under development recommend support of this LDAP Printer
>>schema for service advertising.
>>
>>Any help moving this document forward would be greatly
>>appreciated.
>>
>>Cheers,
>>- Ira McDonald, co-editor of LDAP Printer schema
>>    High North Inc
>>    (consultant at Sharp Labs, Easy Software, and elsewhere)
>>    imcdonald at sharplabs.com
>>
>>--------------------------------------------------------------
>>
>>
>>Copies: IPP WG <ipp at pwg.org>
>>          SLP Discussion List <srvloc-discuss at lists.sourceforge.net>
>>          Pat Fleming <flemingp at us.ibm.com>
>>          Ken Jones <kjones at bytemobile.com>
>>          Harry Lewis <harryl at us.ibm.com>
>>          Ira McDonald <imcdonald at sharplabs.com>
>>
>>Hi folks,                                          Sunday (30 June 2002)
>>
>>I've just sent a final version of 'LDAP Schema for Printer Services' to
>>the Internet-Drafts editor and posted a copy on the PWG server in the
>>directory 'ftp://ftp.pwg.org/pub/pwg/ipp/new_LDAP/' in the file:
>>
>>      <draft-fleming-ldap-printer-schema-02.txt> (June 2002)
>>
>>There have been a number of minor revisions, based on IESG 'last call'
>>comments.  The document includes a change history appendix (to be
>>deleted before RFC publication - see below).
>>
>>The technical content is entirely unchanged from the previous version.
>>
>>As soon as this I-D is available in the IETF repository, we will request
>>that it be published as an Informational RFC.
>>
>>Cheers,
>>- Ira McDonald (co-editor of LDAP printer schema)
>>    High North Inc
>>    imcdonald at sharplabs.com
>>
>>------------------------------------------------------------------------
>>
>>Copies: Internet Drafts Editor <internet-drafts at ietf.org>
>>          Pat Fleming <flemingp at us.ibm.com>
>>          Ira McDonald <imcdonald at sharplabs.com>
>  >
>>I-D Editor,                                        Sunday (30 June 2002)
>>
>>Please place this document in the Internet-Drafts repository named:
>>
>>      <draft-fleming-ldap-printer-schema-02.txt> (June 2002)
>>
>>It replaces the previous:
>>
>>      <draft-fleming-ldap-printer-schema-01.txt> (February 2002)
>>
>>There have been a number of minor revisions, based on IESG 'last call'
>>comments.  The document includes a change history appendix (to be
>>deleted before RFC publication).
>>
>>The technical content is entirely unchanged from the previous version.
>>
>>Abstract
>>
>>     This document defines a schema, object classes and attributes, for
>>     printers and printer services, for use with directories that support
>>     Lightweight Directory Access Protocol v3 (LDAP-TS).  This document is
>>     based on the printer attributes listed in Appendix E of Internet
>>     Printing Protocol/1.1 (IPP) (RFC 2911).  A few additional printer
>>     attributes are based on definitions in the Printer MIB (RFC 1759).
>>
>>Thanks very much,
>>- Ira McDonald (co-editor of LDAP printer schema)
>>    High North Inc
>>    imcdonald at sharplabs.com
>>
>>------------------------------------------------------------------------
>>
>>[Excerpt from Change History]
>>
>>     30 June 2002 - draft-fleming-ldap-printer-schema-02.txt
>>     - Final edits after IESG 'last call';
>>     - Revised title page and section 12 'Acknowledgments' to acknowledge
>>       Ken Jones and Harry Lewis as major contributors (rather than as
>>       current editors), per new RFC Editor policies;
>>     - Rewrote and simplified Abstract and section 1 Introduction, per
>>       comments from Kurt Zeilenga;
>>     - Added section 1.1 'Rationale for using DirectoryString syntax', per
>>       comments from Kurt Zeilenga;
>>     - Added section 1.2 'Rationale for using caseIgnoreMatch', per
>>       comments from Kurt Zeilenga;
>>     - Added section 1.3 'Rationale for using caseIgnoreSubstringsMatch',
>>       per comments from Kurt Zeilenga;
>>     - Renamed section 2 to 'Terminology and Conventions' and added schema
>>       definition format reference, per comments from Kurt Zeilenga;
>>     - Revised section 3 and section 4 to remove (erroneous) guidance on
>>       adding new attributes to existing classes and discussion of RDN for
>>       auxiliary classes, per comments from Kurt Zeilenga and Ryan Moats;
>>     - Revised section 4 'Definition of Attribute Types' to remove
>>       (erroneous) guidance on support of matching rules, per comments
>>       from Kurt Zeilenga;
>>     - Revised section 4 'Definition of Attribute Types' to remove
>>       normative/lengthy descriptions from the DESC clauses and place them
>>       _below_ each formal attribute definition, per comments from Kurt
>>       Zeilenga;
>>     - Revised section 4 'Definition of Attribute Types', removing all
>>       ORDERING clauses using 'caseIgnoreOrderingMatch', per comments from
>>       Kurt Zeilenga;
>>     - Revised sections 4.x printer-uri, printer-xri-supported, and
>>       printer-more-info, to provide guidance on application handling of
>>       malformed URI and reference new sections 1.1, 1.2, and 1.3, per
>>       comments from Kurt Zeilenga;
>>     - Revised section 6 'Definition of Matching Rules' to remove
>>       (erroneous) guidance on support of matching rules, per comments
>>       from Kurt Zeilenga;
>>     - Revised section 7 'IANA Considerations' to include completed
>>       templates for IANA registration of new object classes and attribute
>>       types, defined in this document;
>>     - Revised section 9 'Security Considerations' to reference RFC 2829
>>       (for authentication methods) and RFC 2830 (for TLS confidentiality
>>       and integrity), per comments from Kurt Zeilenga;
>>     - Revised (former) section 10 'References', to separate normative and
>>       informative references, per comments from Kurt Zeilenga;
>>     - Corrected author contact info.



More information about the Ps mailing list