Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (herse.apache.org: domain of akarasulu@gmail.com designates
 66.249.82.227 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:organization:user-agent:mime-version:to:subject:content-type:sender;
        b=Lv5hp0OZ7PpXfM3yLOWcaM8RS07uWg4bhlu1lpOC4EfZK5mXjHWodHbwD81ID60B24jyuAsmQrr7BVQDjN7LrAk1CEuINMmxWAYu/YoGWcCK13pVibAPd68ZL0Cu5BnClK+N/QKiaEhb4i2SSl4co/klvv77vw1HbXWc2yXmCi8=
Message-ID: <4572F9B5.50301@apache.org>
Date: Sun, 03 Dec 2006 11:22:13 -0500
From: Alex Karasulu <akarasulu@apache.org>
Reply-To: akarasulu@apache.org
Organization: Apache Software Foundation
User-Agent: Thunderbird 1.5.0.8 (X11/20061115)
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: [ApacheDS] [Schema] New schema OID assignment scheme
Content-Type: multipart/mixed;
 boundary="------------010601030605060104070409"
Sender: Alex Karasulu <akarasulu@gmail.com>

This is a multi-part message in MIME format.
--------------010601030605060104070409
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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


--------------010601030605060104070409
Content-Type: text/x-vcard; charset=utf-8;
 name="akarasulu.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="akarasulu.vcf"

begin:vcard
fn:Alex Karasulu
n:Karasulu;Alex
org:Apache Software Foundation;Apache Directory
adr:;;1005 N. Marsh Wind Way;Ponte Vedra ;FL;32082;USA
email;internet:akarasulu@apache.org
title:Member, V.P.
tel;work:(904) 791-2766
tel;fax:(904) 808-4789
tel;home:(904) 808-4789
tel;cell:(904) 315-4901
note;quoted-printable:AIM: alexokarasulu=0D=0A=
	MSN: aok123@bellsouth.net=0D=0A=
	Yahoo!: alexkarasulu=0D=0A=
	IRC: aok=0D=0A=
	PGP ID: 1024D/4E1370F8 BBCC E8D8 8756 2D51 C3D4 014A 3662 F96F 4E13 70F8=0D=0A=
	
x-mozilla-html:FALSE
url:http://people.apache.org/~akarasulu
version:2.1
end:vcard


--------------010601030605060104070409--