[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Extending the schema: What about OIDs?

I can't think of anything that would break if you do not use your own OIDs. It's generally good practice to use your own oids because for instance if the core schema developers decide to use the OIDs you have used to define attributes in the future then when you decide to upgrade you might have to reassign OIDs to your attributes. On the other hand if you have your own OID all you need to is just add your schema file.

-Umesh

Venkataraman, Jeeva wrote:

Hi,
Thanks for your reply.
But I am trying to understand what would affect not defining your own ids..?
Where would it be un-usable?
(Like would it to be unable across organizations of same attributes?

Please explain.
Thanks,

Jeeva Venkataraman
Software Engineer, MediaOcean.
In pursuit of real freedom we have yet to gain much more than we have won.
We have not begun to gain freedom from error, the freedom that comes from
the right reason. We have not begun to gain freedom from hate, the freedom
that is born of love. Thats the true meaning of our wars.
- FORTUNE mag Feb 1951 Issue.
-----Original Message-----
From: Umesha Balasubramaniam [mailto:umeshajb@goshen.edu] Sent: Tuesday, March 12, 2002 3:03 PM
To: Venkataraman, Jeeva; openldap-software@OpenLDAP.org
Subject: Re: Extending the schema: What about OIDs?

If you come up with any attributes or objectclasses in practice you should use your own OID. Even if you are extending an existing schema and even if it works.
-Umesh

Venkataraman, Jeeva wrote:

Adam,
As we are using the core schema and extending it few more attributes, do we
need to get OID specifically for these additional attributes? Is that what
you are saying?
My understanding is that we need to get an OID if the schema is totally new
and independent of core schema. Correct me if I am wrong.

Thanks,

Jeeva Venkataraman
Software Engineer, MediaOcean.
In pursuit of real freedom we have yet to gain much more than we have won.
We have not begun to gain freedom from error, the freedom that comes from
the right reason. We have not begun to gain freedom from hate, the freedom
that is born of love. Thats the true meaning of our wars.
- FORTUNE mag Feb 1951 Issue.

-----Original Message-----
From: Adam Williams6 [mailto:awilliam@whitemice.org] Sent: Tuesday, March 12, 2002 1:22 PM
To: Venkataraman, Jeeva
Cc: openldap-software@OpenLDAP.org
Subject: Re: Extending the schema: What about OIDs?

We have created a local schema file which defines the attributes and

object

classes that are specific to us.
Our slapd.conf includes core.schema and our local schema file.
Everything works well this way.
Having read about OIDs, I have clarification on defining the ids for the

all

the entries.
The OIDs for all the attributes/object classes continue to be the same in
the core.schema.

They are defined by the same authority.  The OID should remain the same.

In the local schema we have just added new ids, ids just extending from
similar ones from core schema.
( for instance, defined a 'myattribute' with a id 1.4.1) This works well on our local server. 

As well it should.

What is the need to obtain a fully registered OID?

Go to IANA's web site.

Even if we obtain a OID, 

"IF"!  If you define schema you need your *OWN* OID.

then do we need to change the core schema as well?
Or do we need to change only the local schema attributes?

No, do not adjust existing schema, those are the OIDs of that schema, defined by people with authority to use that OID.

I have a section on OIDs in my LDAP presentation - ftp://kalamazoolinux.org/pub/pdf/ldapv3.pdf