RE: [ldapext] I-D ACTION:draft-zeilenga-ldap-uuid-00.txt

["Steven Legg" <steven.legg@adacel.com.au>]

Steven Legg wrote:
> Kurt D. Zeilenga wrote:
> > >Doesn't matter. Matching rules operate on the abstract value,
> > >not any particular encoding of the abstract value.
> > 
> > While true, the OID of the matching rule identifies both
> > the abstract type AND the LDAP string encoding to use.
> 
> ... for the assertion value. Yes, okay, fair point.

More an observation than a suggestion for change: if the equality
matching rule for the entryUUID attribute was allComponentsMatch
and the LDAP-specific encoding for the UUID syntax was the GSER
encoding then the UUIDs would appear as hexadecimal digit character
strings in LDAP, in both the attribute values and assertion values,
and they would be matched in the same way as octetStringMatch.
I assume that the ISO 11578 string representation isn't anything
special and that all you care about is that the UUIDs normally appear
as displayable characters rather than raw octets.

There isn't an allComponentsOrderingMatch though.

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