-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 12/07/2012 10:51 AM, Victor Sudakov wrote:
Cl?ment OUDOT wrote:
2012/12/7 Victor Sudakov vas@mpeks.tomsk.su:
>>> the problem can be that Outlook use SSSVLV controls >>> on attributes without ordering rules in OpenLDAP. >>> Unfortunately, the 'name' attribute has no ordering >>> rules, so you can't sort results on name (this >>> includes, cn, sn, gn attributes, because they >>> inherit from name). We do not have this limitation >>> on AD (but it breaks LDAP standard).
Mark,
Could you be more specific which LDAP standard it breaks? Is there an explicit prohibition for the 'name' attribute to have ordering rules? In the RFCs somewhere?
Yes, but why do you think it is a restrictive definition and no more optional properties can be *added* (without removing the mandatory ones, of course)?
My best guess is that because this thinking leads to the very problems ("Embrace, Extend, Extinguish") that have plagued some notable implementations of certain standards. They have been harmful to interoperability for quite some time already.
- -- Ondrej Kuznik
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding.