On Thu, Dec 28, 2006 at 06:31:56PM +0100, Emmanuel Lecharny wrote: > >> What about doing a conversion like : A-> 10+ 1, B-> 10 + 2, ... Z->10 + > >26, > >> 0 -> 0, 1 -> 1, ...etc leading to OIDs like that : > >> GUID = azerty12345 > >> OID = 11.36.15.28.30.35.1.2.3.4.5 > >> > >> Just a suggestion ... > > > >Good point, very simple indeed. I could even stick to ASCII and > >zero-terminate the "string". That way it would be "human readable" for > >fluent ASCII speakers. > > you mean, OID= 65.90.69.82.84.89.49.50.51.52.53 for arzerty12345 ?
Yes. > Even better than what I suggested. Not necessary to zero terminate the > OID... Well, the (optional) zero would allow the hierarchy to be extended below the encoded GUID. I even need that because this way I can assign each open-EIS module a unique OID. My LDAP server would get an OID like this (in decoded form): ...private-number.0.c4u_ldapserver.0.c4u_classic_email the next module could get it's own OID space: ...private-number.0.c4u_something_else.0.custom-use Hm. Supposed, anyone would need to parse back the OIDs. Otherwise, the zero-termination is not neccessary, that's right. Bye, Tino. -- www.quantenfeuerwerk.de www.spiritualdesign-chemnitz.de www.lebensraum11.de
