IPP> Re: Root OID for IPP Printer Schema

IPP> Re: Root OID for IPP Printer Schema

IPP> Re: Root OID for IPP Printer Schema

McDonald, Ira imcdonald at sharplabs.com
Wed Apr 26 11:57:55 EDT 2000


Lots of confusion here...

James - we already *have* coordinated with Ken Jones (Sun) about
his original LDAP printer schema - Ken is a co-author of the
SUBSEQUENT IPP WG blessed LDAP printer schema - one of the 
objections raised at IETF 47 to this later LDAP printer schema
is that the Sun-specific object class (that Ken Jones contributed)
must be removed from an IETF 'standards track' vendor neutral
LDAP printer schema - we are now doing so.

All - the principal author of the current vendor neutral LDAP
printer schema is Pat Fleming (IBM AS/400 team in Rochester, MN)
who maintains the database of LDAP schema and attributes for all
IBM products (with the help of others, of course) and is quite
knowledgeable about LDAP - both in theory and in actual practice.

Pat is working on an updated draft - this draft will *remove* the
use of the 'borrowed' Sun OID arcs (taken from Ken Jones' original
Internet Draft) and leave them TBD (as is common in working drafts
of IETF 'standards track' LDAP schema).

The coauthors of the LDAP printer schema are:

Pat Fleming (editor, IBM - for LDAP usage and class structure)
Harry Lewis (IBM - for IPP WG coherence)
Ken Jones (Sun - for Sun-specific issues)
Ira McDonald (High North - for SLP 'printer' template coherence)

We'll keep you posted.  A new draft should be out very soon.

- Ira McDonald, consulting architect at Xerox and Sharp
  High North Inc

-----Original Message-----
From: Ron Bergman [mailto:rbergma at hitachi-hkis.com]
Sent: Tuesday, April 25, 2000 5:45 PM
To: James Kempf
Cc: cmanros at cp10.es.xerox.com; ludovic.poitou at france.sun.com;
bgreenblatt at directory-applications.com; harryl at us.ibm.com;
mark.wahl at innosoft.com; ietf-ldapext at netscape.com; ipp at pwg.org
Subject: Re: IPP> Re: Root OID for IPP Printer Schema

I favor doing what is easiest, and that is keeping the OIDs as they
are.  In the end what difference does it make where the number
was assigned.  This may not be the "pure" solution, but it is just
a number that some application has to interpret.

We tend to get into very long discussions over issues that do
not really have any long term consequences.  I suggest that
whoever (Harry and Ira?) is responsible for editing this document
make a decision and the rest of us just live with it.

    Ron Bergman
    Hitachi Koki Imaging Solutions

James Kempf wrote:

> I think I understand now what some of the confusion around the OIDs taken
> from the SLP template conversion draft might be.
> I'm looking at an Internet draft, draft-sun-ldap-print-schema-00.txt,
> done by Ken Jones of Sun which appears to be a Sun-specific LDAP schema
> printers, dated this Feburary. This draft has *ABSOLUTELY NOTHING* to do
> draft-ietf-svrloc-template-conversion-05.txt, which is an official
> document of the SLP working group, on track for an informational RFC. As
> pointed out, the fact that the OIDs were reserved means that they *WILL
NOT* be
> used for anything else, and that they explicitly belong to the SLP working
> group to use in the RFC. Sun won't be using them or deriving anything from
> for any internal purpose.
> If people are still uncomfortable with having Sun allocated OIDs in
> the schema, I have a request pending at IANA to get a special OID
> for the draft. I will not follow up on the request unless I hear
> some strong voices to the contrary.
> I'd also suggest that someone from the IPP group follow up with Ken
> and see whether he might not be interested in using the standardized
> schema (I'll try on my end as well).
>                 jak

More information about the Ipp mailing list