IPP Mail Archive: RE: IPP> Re: Root OID for IPP Printer Sche

RE: IPP> Re: Root OID for IPP Printer Schema

From: McDonald, Ira (imcdonald@sharplabs.com)
Date: Sat Apr 22 2000 - 20:52:09 EDT

  • Next message: henrik.holst@i-data.com: "Re: IPP> IPP over other transports"

    Hi Jay,

    Good question - it turns out there are existing tools
    and scenarios where a system administrator on a customer
    site will populate LDAP directory objects in an environment
    that either: a) doesn't use SLP at all; or b) doesn't have
    any coordination/shadowing of SLP registrations to LDAP
    directory entries.

    As I mentioned in my note to James Kempf, one example is
    where an LDAP directory has DMTF CIM printer objects and
    there's a desire to augment them with other attributes
    that come from the IPP community for printers.

    When SLP templates are translated directly to one-to-one
    LDAP schemas, they always have some SLP-centric base
    attributes that are both useless to the system admin
    and generally unknown (if they weren't auto-shadowed
    by an SLP Directory Agent).

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

    -----Original Message-----
    From: Jay Martin [mailto:jkm@underscore.com]
    Sent: Friday, April 21, 2000 3:09 PM
    To: McDonald, Ira
    Cc: ipp@pwg.org
    Subject: Re: IPP> Re: Root OID for IPP Printer Schema

    Hi Ira,

    > We referred to your translation spec a good deal, BUT,
    > during development of the LDAP schema, folks from IBM,
    > Sharp, and Xerox indicated that they wanted an LDAP
    > printer schema that was independent of SLP (and shorn
    > of the SLP base attributes).

    Just curious, but why did these folks desire a schema
    independent of SLP? I thought you guys were really into
    SLP and all.


    This archive was generated by hypermail 2b29 : Sat Apr 22 2000 - 20:59:38 EDT