martin: doc/architecture server.sgml,1.17,1.18
cvs at intevation.de
cvs at intevation.de
Tue Apr 20 20:26:46 CEST 2004
Author: martin
Update of /kolabrepository/doc/architecture
In directory doto:/tmp/cvs-serv2737
Modified Files:
server.sgml
Log Message:
Martin K.: Added section explaining an OID
Index: server.sgml
===================================================================
RCS file: /kolabrepository/doc/architecture/server.sgml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -d -r1.17 -r1.18
--- server.sgml 20 Apr 2004 06:33:16 -0000 1.17
+++ server.sgml 20 Apr 2004 18:26:43 -0000 1.18
@@ -1070,6 +1070,18 @@
</programlisting>
</para>
</sect2>
+<sect2><title>LDAP OID Numbers</title>
+<para>
+An OID number is a hierarchical identifier with periods separating each level. Each attribute and each objectclass must have a unique OID number. In order to allow easy consolidation
+of an Kolab LDAP server with other LDAP servers we require a globaly unique OID number. The Kolab Project obtained the base OID <filename>1.3.6.1.4.1.19414</filename> from IANA to which we append values creating our own unique OID numbers.
+</para>
+<para>
+If the OID does not start with <filename>1.3.6.1.4.1.19414</filename> the attribute or objectclass is a copy from some other vendor. You can research who owns an OID from the Alvestrand Data <filename>http://www.alvestrand.no/objectid/top.html</filename> web site OID lookup service
+</para>
+<para>
+The suffixes used for the Kolab project are arbritary unique without any internal semantics and get administered via the Kolab cvs server.
+</para>
+</sect2>
<sect2><title>LDAP Access Control Lists</title>
<para>Access to individual attributes or objects is controlled via static
More information about the commits
mailing list