Skip to content
Switch branches/tags
Go to file
Cannot retrieve contributors at this time

DebOps OID Registry

This is the authoritative source of the information regarding the DebOps OID Registry that describes the hierarchy of the Object Identifiers managed in DebOps.


In order to extend specific network protocols like SNMP or LDAP, an organization needs to have its own Private Enterprise Number registered at Internet Assigned Numbers Authority (IANA) to avoid collisions with other organizations present in the Internet.

enterprise.DebOps /

DebOps is registered in the Private Enterprise Numbers registry as: or

The technical contact for DebOps organization is Maciej Delmanowski.

The DebOps namespace is split into child namespaces depending on their purpose:

OID Namespace Description
42 DebOpsLDAP Object definitions for LDAP databases (LDAP schemas)

The DebOps namespace is defined in the :ref:`debops.schema <slapd__ref_debops_schema>`. All other LDAP schemas created in the DebOps project depend on this schema to be present in the LDAP directory.

enterprise.DebOps.DebOpsLDAP /

The Object identifiers for LDAP objects managed by DebOps are defined in the 42 namespace.

OID LDAP schema Ansible role
1 :ref:`posixgroupid.schema <slapd__ref_posixgroupid>` :ref:`debops.slapd`
2 :ref:`mailservice.schema <slapd__ref_mailservice>` :ref:`debops.slapd`
3 :ref:`nextuidgid.schema <slapd__ref_nextuidgid_schema>` :ref:`debops.slapd`
4 :ref:`orgstructure.schema <slapd__ref_orgstructure_schema>` :ref:`debops.slapd`