RE: Please review: LDAPv3 Data Model Definitions

["Ramsay, Ron" <Ron.Ramsay@ca.com>]

Kurt,

AttributeType
- I would have thought syntax were optional if a supertype were given.
- I was disappointed to find a requirement that servers use textual names
where known in view of the ambiguity of names not specified in standards
track RFCs.

Attribute Usage
- I find these definitions unhelpful. I cannot work out the difference
between directoryOperation and distributedOperation. I can't see how
dSAOperation is related to the operation of distribution. For example, I
would regard all attributes of the Root DSE as dSAOperation attributes but
none relate to distribution. Other operational attributes would be expected
to have the same value at all replicas unless otherwise specified. But I
don't know what such a specification would look like. Is one of these
definitions simply a place holder in case distribution requires an attribute
with a different behaviour. Examples would be welcome.

Attribute Value
- takes a value OCTET STRING if the ;binary option is specified?? What about
jpegPhoto and audio?

Distinguished Name
- Only attribute types can be used. But if I perform a modifyDN with
deleteOldRDN, how can I find this value to delete? Or is this implementation
dependent?

Entry
- X501 requires every entry to contain an objectClass attribute. Does LDAP?
- Is it necessary that an entry contain a modifyTimestamp? That is, when an
entry is created, should modifyTimestamp appear? I would have thought it
would appear on the first modification of the object.

Filter Item
- The present match evaluates to TRUE where there is an attribute or
subtype... I thought debate over inclusion of subtypes was still raging?
- Surely shoeSize>=12 would also evaluate to undefined if shoeSize WERE
recognised but the entry did not contain a shoeSize attribute? Similarly for
Matching Rule Assertion.

Object Class
- An object class doesn't have fields. These should be moved to the object
class description.

Referral
- I was surprised to find continuation reference here.

Structural Object Class of the Entry
- What is: "exactly one most subordinate structural object class?"

Subschema Entry
- Why is "top" mandatory? Does it perform any function?

Subentry
- I don't believe this is defined in X.501. I believe LDAP has there own
definition for it.

Subordinate Reference
- May also be returned in continuation references.

Ron.

-----Original Message-----
From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
Sent: Tuesday, 7 November 2000 5:40
To: ietf-ldapbis@OpenLDAP.org
Subject: Please review: LDAPv3 Data Model Definitions


I draw your attention to the following I-D:
  LDAPv3 Data Model Definitions
  draft-wahl-ldapv3-defns-00.txt

This I-D proposes a technical specification to update and/or
replace sections of RFC 2251 and RFC 2252.  I request you
review this I-D as a strawman proposal for LDAPbis work items.

Your comments are solicited.