Suffix Naming Conventions - Red Hat DIRECTORY SERVER 7.1 - DEPLOYMENT Deployment Manual

Table of Contents

Advertisement

By default, the standard Directory Server deployment contains multiple suffixes,
one for storing data and the others for data needed by internal directory operations
(such as configuration information and your directory schema). For more
information on these standard directory suffixes, see the Red Hat Directory Server
Administrator's Guide.

Suffix Naming Conventions

All entries in your directory should be located below a common base entry, the
root suffix. In naming the root directory suffix, consider the following
recommendations for what the name should be:
Globally unique.
Static, so it rarely changes, if ever.
Short, so that entries beneath it are easier to read on screen.
Easy for a person to type and remember.
In a single enterprise environment, choose a directory suffix that aligns with a DNS
name or Internet domain name of your enterprise. For example, if your enterprise
owns the domain name of
.
dc=example,dc=com
The
dc (domainComponent)
domain name into its component parts.
Normally, you can use any attribute that you like to name your root suffix.
However, for a hosting organization, we recommend that the root suffix contain
only the following attributes:
c (countryName)
name, as defined by ISO.
l (localityName)
where the entry is located or which is associated with the entry.
— Identifies the state or province where the entry resides.
st
o (organizationName)
the entry belongs.
The presence of these attributes allows for interoperability with subscriber
applications. For example, a hosting organization might use these attributes to
create the following root suffix for one of its clients,
o=example_a,st=Washington,c=US
, then you should use a directory suffix of
example.com
attribute represents your suffix by breaking your
— Contains the two-digit code representing the country
— Identifies the county, city, or other geographical area
— Identifies the name of the organization to which
Designing Your Directory Tree
:
example_a
Chapter 4
Designing the Directory Tree
63

Advertisement

Table of Contents
loading

This manual is also suitable for:

Directory server 7.1

Table of Contents