[SOLVED] LDAP & Standards: Extensible match functionality and "Matching Rule" names consistent across vendors?

LDAP & Standards: Extensible match functionality and "Matching Rule" names consistent across vendors?

This article discusses and gives examples of LDAP query syntax http://ff1959.wordpress.com/2011/09/21/mastering-ldap-search-filters/

It shows how the 'filter' portion of the query can give a matching rule. E.g, A filter can specify "exact match" as follows:

(uid:caseExactMatch:=User.0)

Where ":caseExactMatch:" identifies the name of the "matching rule" which the LDAP server will use to filter the results. (e.g. the LDAP server has a matching rule called "caseExactMatch" )

From the article: The above filter will match "User.0" but not "user.0".

My question

I see that RFC 4515 defines the syntax. Do major LDAP vendors support this standard, i.e. 'will it work' regardless of implementation (i.e. including OpenLDAP, Microsoft's Active Directory and SunONE directory server)?
Do LDAP vendors support the 'matching rule' names' listed in RFC 4517 (e.g. caseExactMatch, caseIgnoreMatch, keywordMatch, numericStringMatch, etc )

Reference

RFC 4515 defines LDAP filters

RFC 4517 defines LDAP matching rules

thanks

Solution

extensible match filters are supported by Sun DSEE, UnboundID Directory Server, OpenDS, and OpenLDAP for sure - generally it should be supported by LDAP-compliant servers. Don't know about other, non-compliant servers.