Re: which naming attribute, couple of more questions ...

["Kurt D. Zeilenga" <Kurt@OpenLDAP.org>]

At 03:48 PM 10/11/00 -0700, sanjay jain wrote:
>Please clarify few more things for me.  Thanks.
>Which of the following are MUST for LDAP V3 ?

In my opinion, vendors have a good deal of freedom
when implementing LDAPv3.  I do, however, advocate that
vendors implement not only all the MUSTs, but most of
the SHOULDs, and many of the MAYs.

>   - support for multiple AVAs in an RDN

optional.  A server can return unwillingToPerform or
other suitable resultCode if it is unwilling to accept
multiple AVAs in an RDN as the target or base DN of an
operation.  However, as a value of user attribute or
in a filter, it should accept it for any attribute of
DN syntax it publishes support for.

I know of a few implementations which do not support
multi-valued RDNs.

>   - server should be able to recognize an attribute by its OID
>   or any of its textual names in the protocol (In DNs, attribute names
>   in update operations, in required attr list and in filters etc..)

Off hand, I'd say 'optional'.  As previously noted, there is
plenty of play in the specification.

I know of many implementations which do not support OID/NAME
equivalences in all protocol elements.

>   - support for renaming (moddn) of a non-leaf node

Optional.  A server can return unwillingToPerform or
other suitable resultCode if it is unwilling to perform
the requested operation.

I know of many implementations which do not support
renaming of subtrees.