[ldapext] objectIdentifierMatch

[Howard Chu <hyc@highlandsun.com>]

RFC4512 and RFC4517  allow OIDs to be either numeric or short-name 
descriptors, but the objectIdentifierMatch and 
objectIdentifierFirstComponentMatch matching rules have no way to 
determine in what context a descriptor resides. That makes it pretty 
much impossible to validate these descriptors in arbitrary attributes.

One possible solution would be to specify the namespace in a schema 
extension:

attributetype ( 1.1.1.1.1.1.1.1.1 
               NAME 'myAttr' 
               DESC 'The attribute to use'
               EQUALITY objectIdentifierMatch 
               SYNTAX 1.3.6.1.4.1.1466.115.121.1.38
               SINGLE-VALUE
		X-OID-NAME 'attribute' )

How are others handling this issue?

--
 -- Howard Chu
 Chief Architect, Symas Corp.  http://www.symas.com
 Director, Highland Sun        http://highlandsun.com/hyc
 OpenLDAP Core Team            http://www.openldap.org/project/


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext