HP-UX Directory Server 8.1 deployment guide

Figure 4-5 Directory tree for example isp

Beneath the root suffix entry o=example, c=US, the tree is split into three branches. The ISP

branch contains customer data and internal information for Example ISP. The Internet branch

is the domain tree. The groups branch contains information about the administrative groups.

Consider the following when choosing attributes for the branch points:

• Be consistent.

Some LDAP client applications may be confused if the distinguished name (DN) format is

inconsistent across the directory tree. That is, if l is subordinate to ou in one part of the

directory tree, then make sure l is subordinate to ou in all other parts of the directory service.

• Try to use only the traditional attributes (shown in “Identifying branch points”).

Using traditional attributes increases the likelihood of retaining compatibility with third-party

LDAP client applications. Using the traditional attributes also means that they are known

to the default directory schema, which makes it easier to build entries for the branch DN.

Table 4-1 Traditional DN branch point attributes

DefinitionAttribute name

An element of the domain name, such as dc=example; this is refrequently specified

in pairs, or even longer, depending on the domain, such as dc=example,dc=com or

dc=mtv,dc=example,dc=com.

A country name.

An organization name. This attribute is typically used to represent a large divisional

branching such as a corporate division, academic discipline (the humanities, the

sciences), subsidiary, or other major branching within the enterprise, as in “Suffix

naming conventions”.

An organizational unit. This attribute is typically used to represent a smaller divisional

branching of the enterprise than an organization. Organizational units are generally

subordinate to the preceding organization.

A state or province name.

A locality, such as a city, country, office, or facility name.

l or locality

A domain component, as in “Suffix naming conventions”.

4.2 Designing the directory tree 43