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

Re: Mandatory Operational Attributes

To: Jim Sermersheim <JIMSE@novell.com>
Subject: Re: Mandatory Operational Attributes
From: Mark Wahl <M.Wahl@INNOSOFT.COM>
Date: Mon, 21 Jun 1999 16:29:48 -0500
Cc: ietf-ldapext@netscape.com
In-reply-to: "Your message of Mon, 21 Jun 1999 15:10:27 MDT." <s76e55e9.030@prv-mail20.provo.novell.com>
Resent-date: Mon, 21 Jun 1999 14:30:32 -0700 (PDT)
Resent-from: ietf-ldapext@netscape.com
Resent-message-id: <"UU8dyB.A.55E.p7qb3"@glacier>
Resent-sender: ietf-ldapext-request@netscape.com

There is a subtle distinction here.  Servers MUST follow the rules in 2252 
section 5.1.  Entries may have certain attributes, as described in 3.2.1.  
I did not want to put a MUST condition on an _entry_ as access control 
restrictions could prevent some of those attributes from being visible, and 
when the entry has never been modified the modifyTimestamp and modifiersName
are not there.  This might read better if 3.2.1 said "Entries can contain"
rather than "Entries may contain".  I'll keep this in mind for the next 
revision of LDAPv3.

Mark Wahl, Directory Product Architect
Innosoft International, Inc.

References:
- Mandatory Operational Attributes
  - From: Jim Sermersheim <JIMSE@novell.com>

Prev by Date: Re: LDAP C API: LDAP_OPT_DESC
Next by Date: Re: LDAP C API: Data Types and Legacy Implementations
Index(es):
- Chronological
- Thread