Re: substring matching rules

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

At 11:33 AM 2/8/00 -0800, Kurt D. Zeilenga wrote:
>RFC 2252, 8.3 says:
>   ( 2.5.13.4 NAME 'caseIgnoreSubstringsMatch'
>    SYNTAX 1.3.6.1.4.1.1466.115.121.1.58 )
>   

Interesting enough, the inetOrgPerson draft says:

13.3.3.  Additional matching rules from X.520

    ( 2.5.13.5 NAME 'caseExactMatch'
      SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
    
    ( 2.5.13.7 NAME 'caseExactSubstringsMatch'
      SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )

I don't have a copy of X.520 to confirm correctness.  But
appear so.  When used in a substrings filter, the asserted
substrings are each of directoryString syntax, not each a
substringsAssertion syntax.

The caseIgnoreSubstringsMatch implies that in a substrings
filter, each of the asserted substrings are each of
substringsAssertion syntax.  This is incorrect.  Each should
be a directoryString.

I believe two matching rules, one for substrings filters
and one for extended matching using substrings assertions,
are needed for every match algorithm.   That is:

  ( <OID>.1 NAME 'mySubstringsMatch'
	DESC 'for use with substring filters'
	SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
  ( <OID>.2 NAME 'mySubstringsExtendedMatch'
	DESC 'for use with extended match filters'
	SYNTAX 1.3.6.1.4.1.1466.115.121.1.58 )

(where <OID> is replaced with some valid OID).