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

Re: UUID external format

Kurt Zeilenga wrote:

On Aug 14, 2009, at 9:18 AM, Emmanuel Lecharny wrote:

Hi guys,

a short question about the way OpenLDAP (last version) exposes the entryUUID during replication. UUID is supposed to be binary :

RFC 4530 :

*2.1 UUID Syntax*

  A Universally Unique Identifier (UUID) [RFC4122
  <http://www.apps.ietf.org/rfc/rfc4122.html>] is a 16-octet (128-
  bit) value that identifies an object. The ASN.1 [X.680] type UUID is
  defined to represent UUIDs as follows:

         UUID ::= OCTET STRING (SIZE(16))
-- constrained to an UUID [RFC4122 <http://www.apps.ietf.org/rfc/rfc4122.html>]

RFC 4530 then says:

In LDAP, UUID values are encoded using the [ASCII] character string representation described in [RFC4122]. For example, "597ae2f6-16a6-1027-98f4-d28b5365dc14".

That is, the LDAP encoding of the UUID type is the [ASCII] character string representation.
Ok, got it.

(Much like the LDAP encoding of an INTEGER typer is a character string representation.)
Well, UUID are not meant to be Human Readable, unless you have to register for a M$ product ;)

But this is about transferring attribute/assertion values of the UUID syntax, such as values of the entryUUID attribute.
Ok. I was confusing cookie UUID and entryUUID value. Cookies are transfered as byte[16], when entryUUID are considered as String.

Thanks for the clarification !

cordialement, regards,
Emmanuel Lécharny