H2: Schema Specification
-The {{EX:objectclass}} and {{attributeTypes}} configuration file
+The {{EX:objectclass}} and {{EX:attributeTypes}} configuration file
directives can be used to define schema rules on entries in the
directory.
H3: Object Identifiers
-Each schema element is identified by a globally unique Object
-Identifier (OID). OIDs are also used to identify other objects.
-They are commonly found in protocols described by ASN.1. In
+Each schema element is identified by a globally unique
+{{TERM[expand]OID}} ({{TERM:OID}}). OIDs are also used to identify
+other objects.
+They are commonly found in protocols described by {{TERM:ASN.1}}. In
particular, they are heavy used by Simple Network Management
Protocol (SNMP). As OIDs are hierarchical, your organization
can obtain one OID and branch in as needed. For example,
!endblock
You are, of course, free to design a hierarchy suitable to your
-organizational needs under your organization's OID.
+organizational needs under your organization's OID. No matter
+what hierarchy you choose, you should maintain a registry of
+assignments you make. This can be a simple flat file or a
+something more sophisticated such as the OpenLDAP OID Registry
+{{URL:http://www.openldap.org/faq/index.cgi?file=197}}.
+
+For more information about Object Identifers (and a listing
+service) see {{URL:http://www.alvestrand.no/harald/objectid/}}.
.{{Under no circumstances should you use a fictious OID!}}
may request an OID to be assigned under this arch. Just fill
out the form at {{URL: http://www.iana.org/cgi-bin/enterprise.pl}}
and your official OID will be sent to you usually within a few days.
+Your base OID will be something like {EX:1.3.6.1.4.1.X}} were {{EX:X}}
+is an integer.
+
+Note: Don't let the "MIB/SNMP" statement confuse you. OIDs
+obtained using this form may be used for any purpose including
+identifying LDAP schema elements.
+
H3: AttributeType Specification