directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny" <elecha...@gmail.com>
Subject Re: [ApacheDS] [Schema] New schema OID assignment scheme
Date Sun, 03 Dec 2006 16:26:39 GMT
As we need to modify the whole schema to fix a typo
(1.2.6.1.4.1.18060instead of
1.3.6.1.4.1.18060) ..., this seems to be the best moment to modify these
numbers :)

Emmanuel

On 12/3/06, Alex Karasulu <akarasulu@apache.org> wrote:
>
> Hi all,
>
> I was just talking to Emmanuel on IRC and he had a good idea regarding
> OID assignments.  Right now we have the following OID assignment scheme:
>
> 1.3.6.1.4.1.18060 is the Apache Enterprise IANA number.
>
> 1.3.6.1.4.1.18060.1 is the base for Top Level Projects.
>
> 1.3.6.1.4.1.18060.2 is reserved for the Apache infrastructure team.
>
>
> So Apache Directory is assigned the following base:
>
> 1.3.6.1.4.1.18060.1.1
>
> Internal to the Directory TLP we are then slitting this to assign a base
> to products.  ApacheDS has the following OID base:
>
> 1.3.6.1.4.1.18060.1.1.1
>
> (Should really have been 1.3.6.1.4.1.18060.1.1.0 but we can fix this)
>
> We partitioned this so we can represent schema entities using the
> following bases:
>
> 1.3.6.1.4.1.18060.1.1.1.1 for syntaxes
> 1.3.6.1.4.1.18060.1.1.1.2 for matchingRules
> 1.3.6.1.4.1.18060.1.1.1.3 for attributeTypes
> 1.3.6.1.4.1.18060.1.1.1.4 for objectClasses
> 1.3.6.1.4.1.18060.1.1.1.5 for dITContentRules
> 1.3.6.1.4.1.18060.1.1.1.6 for dITStructureRules
> 1.3.6.1.4.1.18060.1.1.1.7 for matchingRuleUses
> 1.3.6.1.4.1.18060.1.1.1.8 for nameForms
>
> This is all dandy but we often run into problems assigning schema
> elements new OIDs within their own class of identifiers.  Basically if I
> have to add a new attributeType for the apache.schema file I have to
> search both the apachedns.schema and the apache.schema to make sure
> there are no conflicts.
>
> This is a bit of a PITA.  It would be nice to make sure that scheme
> ranges for different schemes are unique so assignments can be isolated
> to individual schema files without problems.
>
> So to do this it might be a good idea to create a separate OID base for
> each ApacheDS specific schema.  So for example we might have the
> following as base schema OID's:
>
> 1.3.6.1.4.1.18060.1.1.0.0 -> apachemeta.schema
> 1.3.6.1.4.1.18060.1.1.0.1 -> apache.schema (core apache)
> 1.3.6.1.4.1.18060.1.1.0.2 -> apachedns.schema
>
> and so on ...
>
> Within each of these schema files we can then divide the OIDs with new
> bases for syntaxes, matching rules, etc ...
>
> Alex
>
>
>
>
>


-- 
Cordialement,
Emmanuel L├ęcharny

Mime
View raw message