Private Enterprise Numbers and OIDs within the university

What is a Private Enterprise Number OID? An Object Identifier (OID) is needed for defining your own SNMP or LDAP objects. An OID contais a Network Management Private Enterprise Code as prefix.
This prefix starts with: iso.org.dod.internet.private.enterprise (1.3.6.1.4.1). Enterprises can apply at the IANA for an own number following this prefix for free. The IANA also provides the list of Enterprise Numbers already in use. (further information about OIDs.)
It is the IANA's policy to assign only one Private Enterprise Number per university to be used by all divisions, departments, and projects therein.
The Institute of Telematics was assigned number 87:
87 Institute of Telematics, University of Karlsruhe
OIDs within the university can be requested by email to ldap<nospam>@tm.uka.de (please delete <nospam> ). Please name a contact person and an email address within your request.
Internal remark: the current table in the SVN-repository Institut/OID-Registry/OID-Registry-Data.txt should be kept up-to-date and also the following list.

So far we got the following assignments:

University of Karlsruhe has official OID 1.3.6.1.4.1.87
OID     Assignment
1.3.6.1.4.1.87   Organization's OID (University of Karlsruhe)
1.3.6.1.4.1.87.1 Reserved (maybe University administration)
1.3.6.1.4.1.87.2 RZ - Rechenzentrum (Computing Center)
                 2005-09-06, C: Ralf Wigand, ralf.wigand at rz.uni-karlsruhe.de
1.3.6.1.4.1.87.3 Institute of Telematics (tm.uka.de)
                 2003-10-15, C: LDAP Admin, ldap at tm.uka.de
1.3.6.1.4.1.87.4 ATIS (Fakultaet fuer Informatik, atis.uka.de)
1.3.6.1.4.1.87.5 ZeMM (Fakultaet fuer Informatik)
1.3.6.1.4.1.87.6 ECON (Institut fuer Volkswirtschaftslehre, Fakultaet fuer Wirtschaftswissenschaften)
                 2004-04-29, C: Lars Wessels, wessels at kit.edu
        Suggested further sub structure
1.3.6.1.4.1.87.*.1     SNMP Elements
1.3.6.1.4.1.87.*.2     LDAP Elements
1.3.6.1.4.1.87.*.2.1   AttributeTypes
1.3.6.1.4.1.87.*.2.1.1 myAttribute
1.3.6.1.4.1.87.*.2.2   ObjectClasses
1.3.6.1.4.1.87.*.2.2.1 myObjectClass
        Structure within tm.uka.de
1.3.6.1.4.1.87.3.1   public (e.g., public LDAP directory information)
1.3.6.1.4.1.87.3.2   praktikum
1.3.6.1.4.1.87.3.3   flexinet
1.3.6.1.4.1.87.3.4   ZeuS (for MIB in sensor nodes, requested by Jochen Dinger 2008-10-31)

Examples:
#1.3.6.1.4.1.87.3.2.2   praktikum LDAP
#1.3.6.1.4.1.87.3.2.2.1   praktikum LDAP Attribute Types
attributetype ( 1.3.6.1.4.1.87.3.2.2.1.1 NAME 'fCert' SYNTAX 1.3.6.1.4.1.1466.115.121.1.5 )
attributetype ( 1.3.6.1.4.1.87.3.2.2.1.2 NAME 'rCert' SYNTAX 1.3.6.1.4.1.1466.115.121.1.5 )

#1.3.6.1.4.1.87.3.2.2.2   praktikum LDAP Object Classes
objectclass ( 1.3.6.1.4.1.87.3.2.2.2.1
        NAME 'certificateUser'
        DESC 'Zertifikatsinhaber'
        SUP top AUXILIARY
        MUST ( objectClass $ fCert $ rCert ) )