Re: Diff files for Schema.pod and Examples.pod

[Clif H. <cl...@di...>]

> 
> On Mon, 19 Jun 2000 13:52:31 CDT, Clif Harden wrote:
> > + After a successful bind you are ready to retrieve the schema 
> > + information.  You do this by initializing a schema object.
> > + 
> > +  $schema = $ldap->schema();
> > + 
> > +  In this case the default schema commonName (cn) is being 
> > +  used to retrieve the schema.
> 
> That description is wrong. schema() will retrieve the schema held by 
> the server using information present in the server's root DSE. See RFC 
> 2251 section 3.4
> 
> > + or
> > + 
> > +  $schema = $ldap->schema($cn);
> > + 
> > +  In this case an alternative schema commonName (cn) is being
> > +  used to retrieve the schema.
> 
> That's wrong for similar reasons. The argument is actually the DN of a 
> subentry or entry that contains the schema.
> 
> X.500 servers will for instance, have subschema stored in subentries 
> below the points which they are mastering, eg <cn=subschema-subentry,o=Y
> oyodyne,c=US>, *not* directly below the root.
> 
> > + The default LDAP schema name is cn=schema.  However this 
> > + may not always be the case, Microsoft Exchange systems are known
> > + to build a schema commonName (cn) that is based on domain and 
> > + server name.
> 
> There is no default schema name in the standards. However, Net::LDAP 
> will guess at a DN of <cn=schema> if it cannot find the 
> subschemaSubentry attribute in the root DSE.
> 
> Looks good otherwise!
> 
> Chris
> 
> 


What I was refering to on the default schema name is that LDAP.pm
has a default schema name of "cn=schema" if it does not find a root 
DSE, not that the LDAP/x.500 standards have a default schema.

Bad choice of words on my part.

Regards,

Clif Harden           INTERNET:  c-h...@ti...