[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Component Matching Performance




Hi,


Sang s Lim wrote:

Directory
- 100,000 entry DIT
- Each entry is a person entry with one userCertificate attribute
- Operations: Random searches on tbsCertificate.serialNumber (serialNumber in userCertificate)
- Indexing: tbsCertificate.serialNumber






I haven't used OpenLDAP or explored its Component Matching capabilities yet, so I'm going to take the content of the operation mentioned above literally.
The mention of 'tbsCertificate' is both surprising and confusing... The userCertificate attribute within LDAP and X.500 does not have a syntax of Certificate as defined within RFC3280; it has a syntax of Certificate as defined with X.509. This is stated in both RFC2252 and Kurt's individual submission of "LDAP X.509 Certificate Schema" (draft-zeilenga-ldap-x509-00.txt).
Even though these definitions may be syntactically equivalent, an LDAP/X.500 userCertificate does not have a tbsCertificate component.


It is my opinion that the component tbsCertificate should not be used within an LDAP search for the userCertificate attribute and in doing so should result in zero entries being returned.


Regards, Andrew Sciberras eB2Bcom

Sang Seok Lim

IBM T.J Watson Research Center
Enterprise Linux Group
slim@xxxxxxxxxx