Re: Changing schema OID values in cn=config

To: Howard Chu <hyc@symas.com>
Subject: Re: Changing schema OID values in cn=config
From: Michael StrÃder <michael@stroeder.com>
Date: Fri, 17 Feb 2012 10:37:30 +0100
Cc: openldap-technical@openldap.org
In-reply-to: <4F3E1488.10904@symas.com>
References: <4ED3C067.4010608@eurobjects.com> <4F3AD045.2080403@eurobjects.com> <4F3E05FE.2070501@eurobjects.com> <4F3E0AB0.5010303@symas.com> <4F3E0DEF.4010603@eurobjects.com> <4F3E1488.10904@symas.com>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120208 Firefox/10.0.1 SeaMonkey/2.7.1

Howard Chu wrote:

Admins should know that OIDs are meant to be constants; you should have
very good reasons for changing them, otherwise you should never change
them.

Another reason why the current experimental .666 OID policy is non-sense andshould be revisited...


Ciao, Michael.

References:
- Re: Changing schema OID values in cn=config
  - From: Nick Milas <nick@eurobjects.com>
- Re: Changing schema OID values in cn=config
  - From: Nick Milas <nick@eurobjects.com>
- Re: Changing schema OID values in cn=config
  - From: Howard Chu <hyc@symas.com>
- Re: Changing schema OID values in cn=config
  - From: Nick Milas <nick@eurobjects.com>
- Re: Changing schema OID values in cn=config
  - From: Howard Chu <hyc@symas.com>