Previous section.

DCE 1.1: Directory Services
Copyright © 1997 The Open Group

Object Identifiers for CDS Attributes

The Open Group Directory Services (XDS) interface offers client application programmers the ability to create and maintain names in either CDS or GDS. Programmers also can create new CDS attribute names or GDS attribute type labels. In the DCE Directory Service, every CDS attribute name and GDS attribute type label has a corresponding unique number called an object identifier.

Origin of Object Identifiers

The purpose of object identifiers is to ensure uniqueness among the attribute types that many different applications generate and use. Object identifiers are typically obtained from a hierarchy of allocation authorities, the highest being the International Organization for Standardization (ISO) and the International Telegraph and Telephone Consultative Committee (CCITT). Individual application developers do not usually have to contact ISO or CCITT directly to obtain unique numbers. Application developers are more likely to request object identifiers from a person within their company who is in charge of allocating them. The company authority would in turn contact a higher authority to obtain a unique company prefix.

The hierarchy of allocation authorities is indicated by dots that separate portions of an object identifier. Each string of numbers delineated by dots represents a level of the allocation hierarchy, going left to right from the highest authority down. For example, the object identifier consists of the following levels:


Identified organisation

Open Software Foundation

Distributed Computing Environment

Remote Procedure Call

RPC Object UUIDs

CDS Attributes Table

The following table lists the currently registered object identifiers for CDS attributes:

# The derivation of the stem of these object ids is:
#       {iso(1) identified-org(3) osf(22) dce(1) cds(3)}
#     OID       LABEL                   SYNTAX
#   CDS_Members             VT_GroupMember   CDS_GroupRevoke         VT_Timeout   CDS_CTS                 VT_Timestamp   CDS_UTS                 VT_Timestamp   CDS_Class               VT_byte (ASCII encoding, ISO 8859-1)   CDS_ClassVersion        VT_Version   CDS_ObjectUUID          VT_uuid   CDS_Replicas            VT_ReplicaPointer   CDS_AllUpTo             VT_Timestamp   CDS_Convergence         VT_small   CDS_InCHName            VT_small   CDS_ParentPointer       VT_ParentPointer   CDS_DirectoryVersion    VT_Version   CDS_UpgradeTo           VT_Version   CDS_LinkTarget          VT_FullName   CDS_LinkTimeout         VT_Timeout   CDS_Towers              VT_byte   CDS_CHName              VT_FullName   CDS_CHLastAddress       VT_byte   CDS_CHState             VT_small   CDS_CHDirectories       VT_CHDirectory   CDS_ReplicaState        VT_small   CDS_ReplicaType         VT_small   CDS_LastSkulk           VT_Timestamp   CDS_LastUpdate          VT_Timestamp   CDS_RingPointer         VT_uuid   CDS_Epoch               VT_uuid   CDS_ReplicaVersion      VT_Version   CDS_NSCellname          VT_char   CDS_GDAPointers         VT_gdaPointer   CDS_CellAliases         VT_GroupMember   CDS_ParentCellPointers  VT_ReplicaPointer    RPC_ClassVersion        VT_byte    RPC_ObjectUUIDs         VT_byte    RPC_Group               VT_byte (ASCII encoding, ISO 8859-1)    RPC_Profile             VT_byte (ASCII encoding, ISO 8859-1)    RPC_Codesets            VT_byte    SEC_RepUUID             VT_byte

The first column contains the object identifier (OID), the second column contains a label (the name to which the identifier is mapped), and the third column indicates the data type (defined in CDS Protocol Encodings ).

Please note that the html version of this specification may contain formatting aberrations. The definitive version is available as an electronic publication on CD-ROM from The Open Group.

Contents Next section Index