[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: Case Ignore Ordering matching rule for IA5 String sysntax ?

Hi !

  OK ... we will check that approach.

   Do you know if it was something forgotten in the RFC4517 ?... it
really odd (to me) that PrintableString (that is a subset of IA5String) 
and DirectoryString (that is a superset) are allowed syntaxis for
"caseIgnoreOrderingMatch" ... but IA5String is not allowed to use it
(maybe I am missunderstanding/mixing things ....???)

Thanks a lot

BR / Antonio

-----Original Message-----
From: masarati@aero.polimi.it [mailto:masarati@aero.polimi.it] 
Sent: jueves, 25 de junio de 2009 21:25
To: Antonio Alonso
Cc: openldap-technical@openldap.org
Subject: Re: Case Ignore Ordering matching rule for IA5 String sysntax ?

> Hi !
>    We are trying to define (in our own ldap schema) an IA5String 
> attribute type that is required to be managed (from our ldap clients) 
> as "case insensitive"
>    "greaterOrEqual" and "lessOrEqual" filters are required to be 
> managed over this attribute, so we wanted to assigne (in its attribute

> type definition) an ORDERING matching requesting "case insensitive" 
> behaviour
>    According to RFC4517 (http://tools.ietf.org/html/rfc4517) there is 
> NO any ordering Matching Rule for IA5String syntax AND case 
> insensitive support.
> We
> tried with the "caseIgnoreOrderingMatch" .. but slapd returns and 
> error (at schema
> loading) as attribute type syntax (IA5String) is not allowed for this 
> "ordering match rule"


>    We checked that defining the attribute as "PrintableString"  works 
> (as "caseIgnoreOrderingMatch"
> is a valid matching rule for that sysntax according to RFC4517) ... 
> but we are really interested in IA5String syntax ....
>    Does openLDAP server technolgy provide a "case insensitive ordering

> match" method for IA5String syntax ?

No.  It doesn't because there's no standard track definition for it. 
However, there's nothing preventing OpenLDAP software from supporting
this non-standard track feature.  Adding custom matching rules is
relatively "trivial".