[Date Prev][Date Next]
Re: UUID external format
Emmanuel Lecharny wrote:
> 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
> When the UUID is transfered in the Syncrepl cookies, it's as a String,
> not as a byte (with a format like xxx-yyyy-zzzz, kindof). Is there any
> reason not to transfer the UUID as a byte ?
Unfortunately you snipped the following text right after what you've cited:
In LDAP, UUID values are encoded using the [ASCII] character string
representation described in [RFC4122]. For example,
So for this particular syntax RFC 4530 defines a LDAP string representation.
That's what's transferred over the wire.