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

Re: LDAP Subentry and naming

To: Ed Reed <eer@OnCallDBA.COM>
Subject: Re: LDAP Subentry and naming
From: mcs@netscape.com (Mark C Smith)
Date: Thu, 30 Mar 2000 11:16:56 -0500
Cc: ietf-ldup@imc.org, ietf-ldapext@netscape.com
Organization: iPlanet E-Commerce Solutions
References: <s8e2a40b.091@mail.oncalldba.com>
Resent-date: Thu, 30 Mar 2000 08:15:54 -0800 (PST)
Resent-from: ietf-ldapext@netscape.com
Resent-message-id: <hzTb6.A.6x.u2344@glacier>
Resent-sender: ietf-ldapext-request@netscape.com

On the choice of a naming attribute for ldapSubEntry objects, I think
the safest choice is to define a new attribute type and say that people
MAY use it for naming.  I would call it "ldapSubEntryName" and still
leave it as an optional ("MAY") type in the objectclass definition in
case someone wants to use a different attribute for naming.  So... I am
basically endorsing option 1 of the three you proposed.

-- 
Mark Smith
Directory Product Development / iPlanet E-Commerce Solutions
My words are my own, not my employer's.            Got LDAP?

Prev by Date: LDAP Schema
Next by Date: RE: LDAP Subentry and naming
Index(es):
- Chronological
- Thread