The use of human-readable OIDs originates in X.500, but for some
mystifying reason was dropped from the LDAP specifications. The syntax
you see here is not the same as X.500; it is a customization I added to
OpenLDAP because I got tired of checking for typos when developing my
own schemas. It is documented in the slapd.conf(5) manpage. Note that
this usage is only a convenience for input parsing; internally the full
numeric OID is stored and that's what you'll see when you query the
Subschema subentry. (Because to do otherwise would violate the braindead
LDAP specification.)
From: jay alvarez <[EMAIL PROTECTED]>
Date: Wed, 3 Aug 2005 20:48:10 -0700 (PDT)
Good day,
I'm trying to create our own schema and I encountered
a schema example from Wake Forest University which has
these lines near the top:
objectidentifier wfu 1.3.6.1.4.1.19861
objectidentifier wfuProductionAttr wfu:2
objectidentifier wfuProductionObj wfu:3
One of his attributetypes looks like this:
attributetype ( wfuProductionAttr:2 NAME
'wfuIpDHCPRange'
DESC 'DHCP ranges passed to
dhcpd.conf'
EQUALITY caseIgnoreIA5Match
SYNTAX
1.3.6.1.4.1.1466.115.121.1.26{128} )
That is, instead of writing the numeric oid
representation of attributes, he writes it in human
readable form.
Is this trick documented in rfc 2252? I'm currently
reading it right now but I can't seem to locate the
exact details regarding this trick. Any idea?
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc
OpenLDAP Core Team http://www.openldap.org/project/
---
You are currently subscribed to [email protected] as: [EMAIL PROTECTED]
To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the
SUBJECT of the message.
