Then again, we could just sidestep all of this schema-extension hassle and just define a suite of new syntaxes:It might be better for the schema to defined like:
( ATTRIBUTE-OID NAME 'orderedValue' EQUALITY caseIgnoreMatch SYNTAX ORDERED-VALUES-SYNTAX-OID X-ORDERED 'SIBLINGS' X-ORDERED-SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
So that to an unaware client, the syntax is something they are not familiar with. For an aware client, the ORDERED-VALUES-SYNTAX-OID is some encoding of something like: orderedValue ::= SEQUENCE { position INTEGER OPTIONAL, value OCTET STRING }
where value is of the X-ORDERED-SYNTAX syntax.
orderedInteger orderedDirectoryString orderedOctetString orderedDistinguishedName
and so on.
-- -- 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