On Aug 10, 2007, at 1:56 PM, Alex Karasulu wrote:
That's quite useful but not quite definitive :-). I guess the first thing is to check if triplesec trunk has update the oids...looks like "no".
I don't think it has so yes you are right. It is using a Safehaus based OID branch.
So should triplesec (lets assume we can merge our efforts) get
188.8.131.52.4.1.18060.0.4.X.0 ApacheDS LDAP Schema syntaxes
184.108.40.206.4.1.18060.0.4.X.1 ApacheDS LDAP Schema matchingRules
220.127.116.11.4.1.18060.0.4.X.2 ApacheDS LDAP Schema attributeTypes
18.104.22.168.4.1.18060.0.4.X.3 ApacheDS LDAP Schema objectClasses
22.214.171.124.4.1.18060.0.4.X.4 ApacheDS LDAP Schema dITStructureRules
126.96.36.199.4.1.18060.0.4.X.5 ApacheDS LDAP Schema nameForms
where X == 6 for the different types?
188.8.131.52.4.1.18060.0.4.6 is the branch you are creating for Triplesec? If you take another
look at the document we already allocated 184.108.40.206.4.1.18060.0.1 as the Tsec base. You
can then assign various kinds of schema elements to OIDs off this base. Here's what I
| 220.127.116.11.4.1.18060.0.1.0 || Tsec LDAP Schema syntaxes |
| 18.104.22.168.4.1.18060.0.1.1 || Tsec LDAP Schema matchingRules |
| 22.214.171.124.4.1.18060.0.1.2 || Tsec LDAP Schema attributeTypes |
| 126.96.36.199.4.1.18060.0.1.3 || Tsec LDAP Schema objectClasses |
| 188.8.131.52.4.1.18060.0.1.4 || Tsec LDAP Schema dITStructureRules |
| 184.108.40.206.4.1.18060.0.1.5 || Tsec LDAP Schema nameForms|
I'm happy to use these but.... right below where the page suggests 220.127.116.11.4.1.18060.0.1 as the tsec base it says "um, that's not a good idea, even better...." and says 18.104.22.168.4.1.18060.0.1 should be for ApacheDS LDAP Extended Operations
I followed what I thought the second suggestion was. I'm happy with either scheme or yet a third one.... let me know. I think it might be a good idea for this page to have clearer advice :-)