[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: BCP for use of o, ou and cn attribute types

To: Jason Lixfeld <jason+lists.openldap@lixfeld.ca>
Subject: Re: BCP for use of o, ou and cn attribute types
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Date: Mon, 03 May 2004 21:25:55 -0700
Cc: openLDAP-software@OpenLDAP.org
In-reply-to: <946A39B2-9D7E-11D8-86BB-000A95989E4A@lixfeld.ca>
References: <946A39B2-9D7E-11D8-86BB-000A95989E4A@lixfeld.ca>

As your question is not specific to OpenLDAP Software, it's
off topic here.  Please direct general LDAP questions to a
general LDAP forum such as <ldap@umich.edu>.

Kurt

At 08:53 PM 5/3/2004, Jason Lixfeld wrote:
>Is there a best common practice for when and where to use these attributes?  RFC2256 describes the 'o' attribute as "This attribute contains the name of an organization".  Is "organization" in their description supposed to be taken ambiguously, such that organization can be a system specific organization called "uid", or does "organization" actually mean XYZ Company Inc. by their definition?
>
>Similar questions for organizationalUnit and commonName.  Both descriptions seem somewhat ambiguously defined.  Is this the case and one is free to use each one as you see fit based on whatever criteria the like, or is each attribute tailored to a specific task as a best practice?

References:
- BCP for use of o, ou and cn attribute types
  - From: Jason Lixfeld <jason+lists.openldap@lixfeld.ca>

Prev by Date: BCP for use of o, ou and cn attribute types
Next by Date: Re: Slurpd timer question
Index(es):
- Chronological
- Thread